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 2021/09/27 09:12:34 UTC

[GitHub] [pulsar] Raven888888 commented on issue #7076: Pulsar SQL cannot get the latest message

Raven888888 commented on issue #7076:
URL: https://github.com/apache/pulsar/issues/7076#issuecomment-927678755


   > 
   > 
   > @RobDickinson I replied in the email.
   > 
   > for ExplicitLac to work, you need to configure the following settings in bookies:
   > 
   > journalFormatVersionToWrite=6
   > fileInfoFormatVersionToWrite=1
   > 
   > and then turn on the explicit lac interval on broker.
   > 
   > bookkeeperExplicitLacIntervalInMills=1000
   
   Tried the above for a pulsar cluster of 3 nodes. Still unable to get the latest row. Am using 2.7.0 pulsar release.
   
   Anybody has any idea? Has this been verified on a cluster setup?
   
   Thank you


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org