apache/pulsar

Flaky-test: AdminApiTransactionMultiBrokerTest.setup

Open

#16,929 创建于 2022年8月3日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Java (13,697 star) (3,485 fork)batch import
Stalearea/testhelp wantedtype/flaky-tests

描述

https://github.com/apache/pulsar/runs/7647562319?check_suite_focus=true

Error:  Tests run: 2, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 100.773 s <<< FAILURE! - in org.apache.pulsar.broker.admin.v3.AdminApiTransactionMultiBrokerTest
  Error:  setup(org.apache.pulsar.broker.admin.v3.AdminApiTransactionMultiBrokerTest)  Time elapsed: 98.777 s  <<< FAILURE!
  org.apache.pulsar.client.api.PulsarClientException: org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException: org.apache.pulsar.client.api.PulsarClientException$LookupException: {"errorMsg":"org.apache.pulsar.broker.PulsarServerException: Failed to acquire ownership for namespace bundle pulsar/system/0x00000000_0xffffffff","reqId":4590687001839393428, "remote":"localhost/127.0.0.1:46635", "local":"/127.0.0.1:55664"}
  	at org.apache.pulsar.client.impl.PulsarClientImpl.<init>(PulsarClientImpl.java:225)
  	at org.apache.pulsar.client.impl.PulsarClientImpl.<init>(PulsarClientImpl.java:154)
  	at org.apache.pulsar.client.impl.ClientBuilderImpl.build(ClientBuilderImpl.java:63)
  	at org.apache.pulsar.broker.transaction.TransactionTestBase.setUpBase(TransactionTestBase.java:146)
  	at org.apache.pulsar.broker.admin.v3.AdminApiTransactionMultiBrokerTest.setup(AdminApiTransactionMultiBrokerTest.java:41)

贡献者指南

技术栈
java
领域
backendtesting
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
JavaApache Pulsar fundamentalsFlaky test debugging
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Investigate the flaky test 'AdminApiTransactionMultiBrokerTest.setup' in files AdminApiTransactionMultiBrokerTest.java and TransactionTestBase.java. The error occurs during setup when acquiring ownership for a namespace bundle. Reproduce the test multiple times to identify race conditions or timing issues. Look for recent changes to the transaction coordinator or multi broker test environment. Consider adding debug logging or retries.