2018-10-12 11:21:11 UTC - Steve Hicks: Added <https://github.com/apache/pulsar/issues/2786> ---- 2018-10-12 14:30:44 UTC - Julien Nioche: thanks @Sijie Guo and @Matteo Merli ---- 2018-10-12 15:53:04 UTC - Jon Bock: Hi Aaron, there are quite a few and the number is growing, including some who are in this Slack channel. A number of them aren’t willing to be named publicly, but here are some examples I know of, both named and anonymous: - Yahoo and Yahoo Japan have been using it in production at large scale for several years - A number of companies providing online services are using Pulsar in production to support those. A few examples of public ones are One Click Retail, STICorp, TaxiStartup. - A major industrial conglomerate in Europe is using Pulsar in production to support their IoT analytics. - A large media company is using Pulsar in production to support digital asset management and logging. - One of the largest marketplaces in Latin America is using Pulsar in production. - A large consumer electronics company is using Pulsar to handle data supporting connected device projects. - A large jobs site is using Pulsar in production to support their data flows.
Those are just a few examples, hope that helps! +1 : Aaron Langford, Grant Wu ---- 2018-10-12 16:50:41 UTC - Lei: @Lei has joined the channel ---- 2018-10-12 18:00:07 UTC - Lei: Hi, I am using Java PulsarClient. I am trying to understand how timeout is handled for consumer acknowledge. So I have tested this scenario: 1. Created a consumer with 12 seconds ackTimeout. 2. Produced a message in consumer subscribed topic. 3. Consumer received the message. 4. Consumer waited for 30 seconds. 5. Consumer called acknowledge(). (?? Expect an exception, nothing happened though.) 6. Consumer received same message second time. 7. Consumer waited for 30 seconds again. 8. Consumer called acknowledge() again. (This is suppose to be timeout again) 9. Couldn't receive same message any more. (?? Expect message to not be acknowledged) What are expected results for step 5 and 9. Is it possible to get expected result for step 5 and 9? ---- 2018-10-12 23:23:25 UTC - Matteo Merli: @Lei 5. acknowledging an already acked message won’t give you exception in any case. 9. The ack-timeout is forcing the re-delivery of the messages if they are not acked within the configured timeout, so in these cases you would see duplicates (either on same consumer or, in case of shared subscriptions, potentiall on other consumers). ----
