AntiBit82 opened a new issue #14378: URL: https://github.com/apache/pulsar/issues/14378
**Describe the bug** Referring to bug https://github.com/apache/pulsar/issues/3828 https://github.com/apache/pulsar/issues/4976 which was fixed in https://github.com/apache/pulsar/pull/5822 I'm still having this exact problem. **Steps to reproduce** Running Pulsar standalone 2.9.1 on EC2. In /home/ec2-user/apache-pulsar-2.9.1/conf/broker.conf I set the value according to the fix: bookkeeperExplicitLacIntervalInMills=10 Restart Pulsar. Spawn ./pulsar sql-worker run Event sending: I parse a CSV file and send the records to Pulsar like this: 1.) Create Pulsar client + producer 2.) Read Csv line by line, map to PoJo, send via producer (async) + save returned CompletableFuture 3.) Make sure all CompletableFutures complete by calling completableFutures.forEach(CompletableFuture::join); 4.) Close pulsar producer & pulsar client Afterwards when I query my topic via Pulsar SQL I'm missing the last record (until I parse the CSV again and send it, then the previous missing record is there, but ofc the new last record is missing). Now, since parsing lines and sending them are fast operations, I also tried to add some delay between the sending of each record (Thread.sleep(20), even Thread.sleep(1000)). Event then the issue remains. **Question** Is there anything I can check to see if the bookkeeperExplicitLacIntervalInMills=10 setting is actually in effect? Do you need more explanation? -- 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]
