![]() ![]() 13:19:06,252 - WARN - Unable to read additional data from client sessionid 0x0, likely client has closed socket ![]() 13:19:05,965 - INFO - Closed socket connection for client /10.40.0.0:49986 (no session established for client) 13:19:05,965 - WARN - Unable to read additional data from client sessionid 0x0, likely client has closed socket 13:18:56,252 - INFO - Closed socket connection for client /10.40.0.0:49978 (no session established for client) 13:18:56,252 - WARN - Unable to read additional data from client sessionid 0x0, likely client has closed socket 13:18:55,965 - INFO - Closed socket connection for client /10.40.0.0:49976 (no session established for client) 13:18:55,965 - WARN - Unable to read additional data from client sessionid 0x0, likely client has closed socket These options could be exposed for values.yaml.Įnable a sidecar to clean them up using java -cp zookeeper.jar:lib/slf4j-api-1.6.1.jar:lib/slf4j-log4j12-1.6.1.jar:lib/log4j-1.2.15.jar:conf .PurgeTxnLog -n (With the correct jar versions for this deploy.)Īdditional information you deem important (e.g. Zookeeper 3.4.0 and later (of which this chart uses) can support the autopurge.* parameters. Clients will have their connections drop and the cluster may lose quorum. Zookeeeper will throw exceptions as it will not be able to write any more logs or snapshots. Zookeeper node fails with full disk mounted at /bitnami/zookeeper.Disk usage increases as logs are not purged.
0 Comments
Leave a Reply. |