[GitHub] [zookeeper] Hinterwaeldlers opened a new pull request, #1922: document the need for local sessions within the readonly mode

2022-09-12 Thread GitBox
Hinterwaeldlers opened a new pull request, #1922: URL: https://github.com/apache/zookeeper/pull/1922 Starting with commit https://github.com/apache/zookeeper/commit/c47ef905e077184bc5b7f555a3e2dfeb6dc046e1 the readonly mode requires local sessions to be activated. This commit appends

[GitHub] [zookeeper] Hinterwaeldlers opened a new pull request, #1921: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in read

2022-09-12 Thread GitBox
Hinterwaeldlers opened a new pull request, #1921: URL: https://github.com/apache/zookeeper/pull/1921 https://github.com/apache/zookeeper/pull/1390 for the 3.7 branch -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [zookeeper] eolivelli commented on pull request #1922: document the need for local sessions within the readonly mode

2022-09-12 Thread GitBox
eolivelli commented on PR #1922: URL: https://github.com/apache/zookeeper/pull/1922#issuecomment-1243829676 what happens if you do not enable them ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

[GitHub] [zookeeper] Hinterwaeldlers closed pull request #1920: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in readonly mo

2022-09-12 Thread GitBox
Hinterwaeldlers closed pull request #1920: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in readonly mode URL: https://github.com/apache/zookeeper/pull/1920 -- This is an automated message from the Apache Git

[GitHub] [zookeeper] Hinterwaeldlers opened a new pull request, #1920: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in read

2022-09-12 Thread GitBox
Hinterwaeldlers opened a new pull request, #1920: URL: https://github.com/apache/zookeeper/pull/1920 Contains the fix from https://github.com/apache/zookeeper/pull/1390 to the 3.7 branch -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [zookeeper] Hinterwaeldlers closed pull request #1390: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in readonly mo

2022-09-12 Thread GitBox
Hinterwaeldlers closed pull request #1390: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in readonly mode URL: https://github.com/apache/zookeeper/pull/1390 -- This is an automated message from the Apache Git

[GitHub] [zookeeper] Hinterwaeldlers opened a new pull request, #1390: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in read

2022-09-12 Thread GitBox
Hinterwaeldlers opened a new pull request, #1390: URL: https://github.com/apache/zookeeper/pull/1390 Use common zxid between all ZooKeeperServers used within a server instance -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [zookeeper] Hinterwaeldlers commented on pull request #1390: ZOOKEEPER-3526: data inconsistency due to mistaken TRUNC caused by maxCommittedLog is much less than minCommittedLog when in reado

2022-09-12 Thread GitBox
Hinterwaeldlers commented on PR #1390: URL: https://github.com/apache/zookeeper/pull/1390#issuecomment-1243668793 After I've done a couple of tests and code reading, it seems having the zxid set to the valid value seems still a good thing -> Test + Code adapted accordingly -- This is