You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/02/07 04:32:37 UTC
[GitHub] [pulsar] devinbost opened a new issue #6258: (Flaky-Test) Possible
Race Condition - Namespace already exists
devinbost opened a new issue #6258: (Flaky-Test) Possible Race Condition - Namespace already exists
URL: https://github.com/apache/pulsar/issues/6258
I've actually experienced intermittent (random) issues in production that have given the message "Namespace already exists," but we never captured broker logs when this has happened.
This is an intermittent error that appears to be a race condition or concurrency issue, rather than an issue with just the test:
```
[ERROR] Tests run: 20, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 345.803 s <<< FAILURE! - in org.apache.pulsar.broker.service.ReplicatorTest
464[ERROR] testReplicatedCluster(org.apache.pulsar.broker.service.ReplicatorTest) Time elapsed: 0.023 s <<< FAILURE!
465org.apache.pulsar.client.admin.PulsarAdminException$ConflictException: Namespace already exists
```
This may reflect intermittent issues that are happening in production.
The logs can be seen here: https://github.com/apache/pulsar/pull/6202/checks?check_run_id=431093396
I've also attached the logs.
[logs_14078.zip](https://github.com/apache/pulsar/files/4168962/logs_14078.zip)
----------------------------------------------------------------
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 to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] sijie commented on issue #6258: [Pulsar-Broker] consistent
test failure - Namespace already exists or ManagedLedgerException: Not
enough non-faulty bookies available
Posted by GitBox <gi...@apache.org>.
sijie commented on issue #6258: [Pulsar-Broker] consistent test failure - Namespace already exists or ManagedLedgerException: Not enough non-faulty bookies available
URL: https://github.com/apache/pulsar/issues/6258#issuecomment-583677302
Namespace already exists usually because tests are re-run. So you might consider improving the test with randomized names.
----------------------------------------------------------------
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 to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] devinbost commented on issue #6258: [Pulsar-Broker]
consistent test failure - Namespace already exists or
ManagedLedgerException: Not enough non-faulty bookies available
Posted by GitBox <gi...@apache.org>.
devinbost commented on issue #6258: [Pulsar-Broker] consistent test failure - Namespace already exists or ManagedLedgerException: Not enough non-faulty bookies available
URL: https://github.com/apache/pulsar/issues/6258#issuecomment-583541151
@sijie FYI.
----------------------------------------------------------------
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 to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [pulsar] devinbost commented on issue #6258: (Flaky-Test) Possible
Race Condition - Namespace already exists
Posted by GitBox <gi...@apache.org>.
devinbost commented on issue #6258: (Flaky-Test) Possible Race Condition - Namespace already exists
URL: https://github.com/apache/pulsar/issues/6258#issuecomment-583538379
When I run this test locally, I'm getting this exception:
```
org.apache.pulsar.client.api.PulsarClientException$BrokerPersistenceException: org.apache.bookkeeper.mledger.ManagedLedgerException: Not enough non-faulty bookies available
at org.apache.pulsar.client.api.PulsarClientException.unwrap(PulsarClientException.java:691)
at org.apache.pulsar.client.impl.ProducerBuilderImpl.create(ProducerBuilderImpl.java:93)
at org.apache.pulsar.broker.service.ReplicatorTest.testReplicatedCluster(ReplicatorTest.java:834)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:583)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.privateRun(TestRunner.java:648)
at org.testng.TestRunner.run(TestRunner.java:505)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:455)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:450)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:415)
at org.testng.SuiteRunner.run(SuiteRunner.java:364)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:84)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1208)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1137)
at org.testng.TestNG.runSuites(TestNG.java:1049)
at org.testng.TestNG.run(TestNG.java:1017)
at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:73)
at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:123)
```
I've attached the test log and the test runner log from reproducing this issue locally:
[test_log.txt](https://github.com/apache/pulsar/files/4172300/test_log.txt)
[test_runner_log.txt](https://github.com/apache/pulsar/files/4172301/test_runner_log.txt)
This issue consistently occurs when I run the test from master, and it's also blocking my PR https://github.com/apache/pulsar/pull/6202
----------------------------------------------------------------
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 to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services