Re: [DISCUSSION] Delayed message delivery

Hi All, Actually, I also prefer to simplify at broker side. If pulsar support set arbitrary timeout on each message, if not cluster failure or consumer failure, it needs to behave normally(on time). Otherwise, user need to understand how pulsar dispatching messages and how limit of unacked messag

Re: [DISCUSSION] Delayed message delivery

> If the goal is to minimize the amount of redeliveries from broker -> client, there are multiple ways to achieve that with the client based approach (eg. send message id and delay time instead of the full payload to consumers as Ivan proposed). But the main reason to put this logic on client side

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

See Changes: [mmerli] [cpp-build] support run specific cpp-test using docker build script [mmerli] fix get topic name for input message (#3384) -- [...truncated 996.81