315157973 opened a new pull request, #21940:
URL: https://github.com/apache/pulsar/pull/21940

   
   Main Issue: https://github.com/apache/pulsar/issues/21347
   
   ### Motivation
   
   When the client machine's clock is incorrect (eg: set to 1 year later) and 
the Broker does not set the AppendBrokerTimestampMetadataInterceptor, the 
Ledger will not be cleaned up.
   Because if the Broker's timestamp is not set, the expiration check will be 
based on the client's publish time.
   
   As we discuss in 
https://lists.apache.org/thread/0vtjt436xvlg0fr4ogchkjdvjcp56mvz
   
   ### Modifications
   TTL not base the on wrong client publish time
   
   ### Verifying this change
   
   - [x] Make sure that the change passes the CI checks.
   
   ### Documentation
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   
   ### Matching PR in forked repository
   
   PR in forked repository: <!-- ENTER URL HERE -->
   
   


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

Reply via email to