[FLINK-26223] Making ZK-related logs available in tests

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.6, 1.14.3, 1.15.0
• Fix Version/s: 1.14.5, 1.15.0, 1.13.7
• Component/s: Runtime / Coordination
• Labels: pull-request-available test-stability
• Assignee: Matthias Pohl
• Reporter: Matthias Pohl
• Created: 17/Feb/22 13:13
• Updated: 11/Mar/22 09:33
• Resolved: 02/Mar/22 15:28

Description

Recently, we had a few incidents where it appears that ZooKeeper wasn't behaving as expected. It might help to have to the ZooKeeper logs available in these cases.

We have multiple options:

• Introduce an extension to change the ZK log level for specific tests
• Lower the ZK log level again and make the logs being written to the standard log files
• Lower the ZK log level again and move the ZK logs into a dedicated file to avoid spoiling the Flink logs

Issue Links

• relates to: FLINK-25981 ZooKeeperMultipleComponentLeaderElectionDriverTest.testLeaderElectionWithMultipleDrivers failed
• relates to: FLINK-26121 ZooKeeperLeaderRetrievalConnectionHandlingTest.testNewLeaderAfterReconnectTriggersListenerNotification failed on azure
• relates to: FLINK-26120 ZooKeeperCheckpointIDCounterITCase.testConcurrentGetAndIncrement failed on azure
• links to: GitHub Pull Request #18846
• links to: GitHub Pull Request #18946