Say we know one node is temporarily dysfunctional and it won't go up no matter what. Yet when we do admintools -t start_db, it keeps on waiting for that node forever so we just Ctrl+C it. Is there a better way of instructing the cluster to run without that one node for the time being?
Question
What is the proper way to starting an incomplete cluster?
+2
+2Consider the following thread.
https://forum.vertica.com/discussion/241043/cannot-replace-a-permanently-down-node-update-vertica-fails-with-host-is-unreachable
In any case it is advised to open a support case.
+2@mosheg said:
Consider the following thread.
https://forum.vertica.com/discussion/241043/cannot-replace-a-permanently-down-node-update-vertica-fails-with-host-is-unreachable
In any case it is advised to open a support case.
Thanks, but that case is about a permanently down node that needs to be removed from the cluster. In my case a node is temporarily down and I just want to use the reduced cluster for a week. It actually works my way, I am just a bit concerned about it constantly trying to connect the down node and me having to use CTRL+C in admintools to get out of the waiting situation. I was wondering if I could tell the cluster to leave the down node be until further notice but to not decommission it.
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
