The Vertica Forum recently got a makeover! Let us know what you think by filling out this short, anonymous survey.

Management Console is showing a node as UNKNOWN, but the node is actually UP.

We are using MC (Management Console) to view the database, and one of the databases in the cluster is appearing as if it is in an Unknown state. The database is actually UP in the cluster. We need to make sure that the MC is properly reading the node state.

Comments

  • From the nodes in the cluster, adjust the agent settings. On all nodes running the agent: We recommend adjusting the cache size of the agent from 50 to 200. To do this, follow these steps: As root, shut down the agent on each node using the command: /etc/init.d/vertica_agent stop. Backup the file /opt/vertica/agent/config.py using the command cp /opt/vertica/agent/config.py /opt/vertica/agent/config.py.orig. Modify the file /opt/vertica/agent/config.py and change cache_size = 50 to cache_size = 200. As root, start the agent on each node using the command /etc/init.d/vertica_agent start On the machine running the MC (Management Console): Adjust the cache size used by the MC to write data to the embedded Vertica database from 100 to 200. To do this, follow these steps:
    • As root, shut down the MC using the command /etc/init.d/vertica-consoled stop .
    • Backup the following file /opt/vertica/bin/mctl using the command cp /opt/vertica/bin/mctl /opt/vertica/bin/mctl.orig
    • Modify the file /opt/vertica/bin/mctl and add -Dvertica.commit_size=200 to the java start lines.
    • For example, find the line: $JAVA_HOME/bin/java -Dvertica.home=$VERTICA_HOME -Djava.library.path=$VERTICA_HOME/lib -Dderby.system.home=/opt/vertica/mcdb/derby -Xmx2048m -Xms1024m -XX:MaxPermSize=256m -jar $VERTICA_HOME/lib/webui.war & Change that line to: $JAVA_HOME/bin/java -Dvertica.home=$VERTICA_HOME -Dvertica.commit_size=200 -Djava.library.path=$VERTICA_HOME/lib -Dderby.system.home=/opt/vertica/mcdb/derby -Xmx2048m -Xms1024m -XX:MaxPermS
    • Restart the MC and after it has restarted, remove the database from the MC front end and then add it back. It should now properly show the node information.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.