Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_forward_expiration is flaky #315

Open
lzydmxy opened this issue Jun 18, 2024 · 0 comments
Open

test_forward_expiration is flaky #315

lzydmxy opened this issue Jun 18, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@lzydmxy
Copy link
Contributor

lzydmxy commented Jun 18, 2024

RaftKeeper version

v2.0.4

Description

We isolated the network between node 3 and nodes (1, 2). If node 3 is the leader, the test will fail.

        node1_zk = node1.get_fake_zk(session_timeout=15)
        node2_zk = node2.get_fake_zk()
        node3_zk = node3.get_fake_zk()

        node1_zk.sync("/")  # Make node1 and node3 establish a forward connection

        with PartitionManager() as pm:
            pm.partition_instances(node3, node2)
            pm.partition_instances(node3, node1)
            time.sleep(3)
            begin = datetime.now()
            with pytest.raises(OperationTimeoutError):
                node1_zk.sync("/")
            end = datetime.now()

We make an

How to reproduce

@lzydmxy lzydmxy added the bug Something isn't working label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant