dmercuriali commented on issue #4287: URL: https://github.com/apache/bookkeeper/issues/4287#issuecomment-2085675635
@eolivelli our system is pretty old. In the znode `/ledgers/LAYOUT` we had `Flat`. We use the same BK cluster for pulsar and for some other parts of our application. Our code defaulted to `zk+null`. After the pulsar upgrade we noticed that the ledgers for pulsar topics were created with the `hierarchical` layout (while the ledgers created directly by us were still created with the `flat` layout). This might be a problem with pulsar, maybe It forces the layout instead of reliyng on the cluster-default. But the strange thing @hamadodene is reporting, is that pulsar was (apparently) able publish messages on the topics, but could not read the messages because bk was throwing `BKException$BKNoSuchLedgerExistsException: No such ledger exists on Bookies`. We then forced the `hierarchical` layout on the bk cluster, but bk still could not read the pulsar ledgers. Looking in the bk logs, we found no entries for the ledgers "created" before the layout switch. Is it possible that bk was creating the znode for the ledger (with `hierarchical` layout), and then silently failed to actually write because of the conflicting layout is use? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
