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:41:05 UTC

[GitHub] [pulsar] Raven888888 opened a new issue #12209: Pulsar SQL cannot get the latest message (still!)

Raven888888 opened a new issue #12209:
URL: https://github.com/apache/pulsar/issues/12209


   **Describe the bug**
   Exactly the same as #7076.
   Tried exactly [this](https://github.com/apache/pulsar/issues/7076#issuecomment-699638900) in both standalone and clustered setup, both unable to get the latest row.
   
   **Expected behavior**
   This bug is said to have been fixed in 2.7.0 pulsar release.
   
   The previous issue is closed, thus opening a new one to track on this.
   Any pointer is appreciated.


-- 
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

[GitHub] [pulsar] MarvinCai commented on issue #12209: Pulsar SQL cannot get the latest message (still!)

Posted by GitBox <gi...@apache.org>.
MarvinCai commented on issue #12209:
URL: https://github.com/apache/pulsar/issues/12209#issuecomment-930211837


   Have you try setting the following config:
   In Broker config, set
   bookkeeperExplicitLacIntervalInMills > 0
   bookkeeperUseV2WireProtocol=false
   
   And in Presto config, set
   pulsar.bookkeeper-explicit-interval > 0
   pulsar.bookkeeper-use-v2-protocol=false
   
   This is related Bookie explicit LAC mentioned here: https://bookkeeper.apache.org/docs/4.5.0/overview/releaseNotes/


-- 
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

[GitHub] [pulsar] Raven888888 commented on issue #12209: Pulsar SQL cannot get the latest message (still!)

Posted by GitBox <gi...@apache.org>.
Raven888888 commented on issue #12209:
URL: https://github.com/apache/pulsar/issues/12209#issuecomment-943201315


   Greetings @MarvinCai 
   
   Can confirm that after applying your settings, it is working perfectly! TQVM.
   
   Closing this.


-- 
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

[GitHub] [pulsar] Raven888888 closed issue #12209: Pulsar SQL cannot get the latest message (still!)

Posted by GitBox <gi...@apache.org>.
Raven888888 closed issue #12209:
URL: https://github.com/apache/pulsar/issues/12209


   


-- 
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

[GitHub] [pulsar] MarvinCai commented on issue #12209: Pulsar SQL cannot get the latest message (still!)

Posted by GitBox <gi...@apache.org>.
MarvinCai commented on issue #12209:
URL: https://github.com/apache/pulsar/issues/12209#issuecomment-930211837


   Have you try setting the following config:
   In Broker config, set
   bookkeeperExplicitLacIntervalInMills > 0
   bookkeeperUseV2WireProtocol=false
   
   And in Presto config, set
   pulsar.bookkeeper-explicit-interval > 0
   pulsar.bookkeeper-use-v2-protocol=false
   
   This is related Bookie explicit LAC mentioned here: https://bookkeeper.apache.org/docs/4.5.0/overview/releaseNotes/


-- 
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