eolivelli opened a new issue #10871: URL: https://github.com/apache/pulsar/issues/10871
**Describe the bug** While testing the 2.8.0rc2 I found that if you start a Pulsar broker with transactionCoordinatorEnabled=true and allowAutoTopicCreation=false the broker does not work. I see these errors: > 2021-06-09 12:39:19,214 - ERROR - [bookkeeper-ml-scheduler-OrderedScheduler-2-0:ServerCnx@1292] - [/192.168.1.111:58508] Failed to create topic persistent://public/default/__transaction_buffer_snapshot, producerId=1 > java.util.concurrent.CompletionException: java.util.NoSuchElementException: No value present > at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) > at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319) > at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645) > at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) > at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073) > at org.apache.pulsar.broker.service.BrokerService$3.openLedgerFailed(BrokerService.java:1261) > at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl.lambda$asyncOpen$8(ManagedLedgerFactoryImpl.java:402) > at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986) > at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970) > at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) > at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) > at org.apache.bookkeeper.mledger.impl.ManagedLedgerFactoryImpl$2.initializeFailed(ManagedLedgerFactoryImpl.java:397) > at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl$1.operationFailed(ManagedLedgerImpl.java:396) > at org.apache.bookkeeper.mledger.impl.MetaStoreImpl.lambda$getManagedLedgerInfo$2(MetaStoreImpl.java:87) It looks like that the only way to make the system work it to manually create a topic named: `persistent://public/default/__transaction_buffer_snapshot` Please note that the topic MUST NOT be partitioned One important fact is that the broker is configured for transactionCoordinatorEnabled=true **but NO CLIENT is using transactions** and this looks like a problem because in order to use transactionCoordinatorEnabled=true and allowAutoTopicCreation=false you probably have to manually create such topic for every namespace. -- 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: [email protected]
