You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a case where some nodes in zookeeper cluster were pulled along with their DNS names, so some DNS names declared in zookeeper configuration becomes invalid. This seems to cause the clickhouse tables in some nodes to be readonly.
Our clickhouse version is 1.1.54388
What we see in the logs is that nodes failed to handle DNS errors
<Error> some_tables (ReplicatedMergeTreeRestartingThread): void DB::ReplicatedMergeTreeRestartingThread::run(): Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = No address found: node1.zookeeper, e.what() = No address found
....
<Error> executeQuery: Code: 242, e.displayText() = DB::Exception: Table is in readonly mode, Stack trace:
....
<Error> ConfigReloader: Error loading config from `/etc/clickhouse-server/config.xml': Poco::Exception. Code: 1000, e.code() = 0, e.displayText() = Exception: Failed to preprocess config '/etc/clickhouse-server/config.xml': No address found: node1.zookeeper, e.what() = Exception
We do have multiple zookeeper servers declared in config.xml. Any idea why it bailed after failing to query only 1 name ?
The text was updated successfully, but these errors were encountered:
We had a case where some nodes in zookeeper cluster were pulled along with their DNS names, so some DNS names declared in zookeeper configuration becomes invalid. This seems to cause the clickhouse tables in some nodes to be readonly.
Our clickhouse version is 1.1.54388
What we see in the logs is that nodes failed to handle DNS errors
We do have multiple zookeeper servers declared in config.xml. Any idea why it bailed after failing to query only 1 name ?
The text was updated successfully, but these errors were encountered: