changing node X startup state to critical

Hi Pietro,

Vertica's durability and crash-recovery depend on K-safety.  If a node has committed data in the WOS and that node crashes, the only way to get the data back is to retrieve it from another node.  This is a fundamental limitation of running Vertica without K-safety (and therefore of Vertica as a single-node database); also a limitation that we find that people often forget, and re-discover only after a node has crashed.

The MC is targeted at displaying issues that likely matter to production services.  We allow single-node Vertica instances because they are great for development purposes.  But I would not personally recommend running a production service on a single-node database.  (Use three small machines instead.  We have a whitepaper somewhere about running Vertica on a cluster of many HP Moonshot blades, for example; tiny cheap Intel Atom-based machines.)

I don't know whether there's a way to disable the warning.  Others may be able to comment there.

Adam

Hi Adam,
thank you for your reply.
Just to be clear, do you confirm that this messages could be displayed just for warning and they could be not directly related to any issues?
My only node haven't crashed yet, but I often see this message

furthermore, I have other development environment with single-node clusters but MC does not display this message in those cases. I can't figure out why.

Hi Pietro,

Many Vertica users would consider "the current configuration will cause you to lose data if the system crashes" as an issue.  (And a serious issue, too.)

The error doesn't indicate that your system is more likely to crash, if that's your concern.  Just that the cost is greater if it does.

Adam