Re: [DISCUSSION] Delayed message delivery

On Fri, Jan 18, 2019 at 2:51 PM Ivan Kelly wrote: > One thing missing from this discussion is details on the motivating > use-case. How many delayed messages per second are we expecting? And > what is the payload size? > > > If consumer control the delayed message specific execution time we must

Re: [DISCUSSION] Delayed message delivery

One thing missing from this discussion is details on the motivating use-case. How many delayed messages per second are we expecting? And what is the payload size? > If consumer control the delayed message specific execution time we must > trust clock of consumer, this can cause delayed message pro

Re: [DISCUSSION] Delayed message delivery

If consumer control the delayed message specific execution time we must trust clock of consumer, this can cause delayed message process ahead of time, some applications cannot tolerate this condition. > My concern of this category of approaches is "bandwidth" usage. It is > basically trading bandw

Re: [DISCUSSION] Delayed message delivery

On Thu, Jan 17, 2019 at 2:58 PM Matteo Merli wrote: > After a long delay (no pun intended), I finally got through the > previous discussions around the delayed message delivery proposals. > I'm referring to PIP-26 > https://github.com/apache/pulsar/wiki/PIP-26%3A-Delayed-Message-Delivery > and th

Build failed in Jenkins: pulsar-website-build #529

See Changes: [zhaijia] Fixed links to RPM/Deb package signature files (#3371) [zhaijia] Fix bug consumer stop consume(issue-3131) (#3358) [github] [dev] PIP 27: Add checklist in github pull request template