I am using Pulsar 3.2.1, the cluster has been runn...
# general
m
I am using Pulsar 3.2.1, the cluster has been running for 24h. I've ingested around 30k messages during that time. It looks like some messages were not delivered and are in the backlog, but were acked. Happens on Shared and Exclusive subscriptions. One of the affected topic is:
__change_events
, therefore I don't think it's related to my code. All my affected topics has subscriptions with readCompacted set to
true
. Anyone faced this issue and knows the potential cause/solution? I am using KAAP
👍 1
g
Yes I stumbled upon the same issue: all messages acknowledged, but some still appear in the backlog (shared topics without compaction). I do not know the cause / solution. The issue seems related to the Java client since v3 (I do not have the issue with Pulsar 3+ and client 2.11)
👍 1
m
For now I've changed Pulsar release to 3.1 (3.1.3), for now no issues, but we'll see ...
g
Which client do you use?
m
The client is 3.2.0
l
There's a bug report and fix that matches the description in this thread: issue https://github.com/apache/pulsar/issues/22352 and fix https://github.com/apache/pulsar/pull/22353
👀 1
👍 1
@è§æ˜“ćźą ^^^
Thanks for sharing that you were running into this issue @MichaƂ Cukierman. Do you have a chance to run tests with a snapshot version after we get fixes into branch-3.2 ? It seems that our test suite isn't sufficient to catch such issues at the moment. @Gilles Barbier Contributions for a test that reproduces the issue is more than welcome.
m
@Lari Hotari I am on a conference and just downgraded the version to get rid of the problem.
l
@MichaƂ Cukierman the fixed version isn't available yet. It is a useful contribution to Pulsar to validate that snapshot or release candidate versions fix a problem or don't cause regressions. We need more Pulsar users that would be willing to contribute to Pulsar in this way. /cc @Gilles Barbier
m
Sure, I am on Adobe Summit on a booth, cannot try the SNAPSHOT version. I had 50 visitors yesterday, looking for the same number today 😉
Had a conversation with Infosys yesterday, they told that our solution (which uses Pulsar) is great, but they target enterprises, so they a looking into proven technologies with no bugs. We could advice our future customers/partners to use SN saas or byoc, to not get overwhelmed with the support, but I do agree that stabilizing Pulsar is the key to get to the enterprises.
we've just launched the product: www.streamx.dev and we have no customers yet
🎉 1
l
Pulsar 3.2.2 and 3.0.4 will contain the required 2 fixes to this problem. Both releases are in release candidate phase and in release voting. Will be released on Tuesday or Wednesday. https://lists.apache.org/thread/qp0bto5fbto1djg0lro9k1pmfcrkq1hv https://lists.apache.org/thread/pl5c0hx2z19kg4v76lgxhfxxccmcoj56
@MichaƂ Cukierman @Gilles Barbier If you have a chance to test the release candidate, that would be helpful and a useful contribution to Pulsar development. The project needs such contributions.
g
@Lari Hotari sure - what’s the easiest way to access it?
l
@Gilles Barbier the release vote emails contain the links. For Maven deps, there's a staging repository url. There's also docker images. Links in the previous message https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1711715458390569?thread_ts=1711399325.293829&cid=C5Z4T36F7
👀 1
g
Is there an update of the java client as well in this version?
l
Yes, that's available via the maven staging repository url. The voting emails contain the URLs.
g
l
@Gilles Barbier The version has been released and is currently syncing to maven central. It should be available within a few hours.
for immediate access, the repository url https://repository.apache.org/content/repositories/releases/ can be used.
g
ok - I will test it today.
@Lari Hotari Yes the release 3.2.2 of the java client seems to fix the bug I had about acknowledgment not taken into account 👏
🎉 1
l
sounds good. The 3.0.4 and 3.2.2 versions aren't yet synced in Maven central. https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1712141547255429 . There has been some incident in the repository sync and it is being resolved by Sonatype.
g
it seems to work now
l
ok great
g
ok. Same for 3.0.4 - bug fixed for me 🙂
@MichaƂ Cukierman check with client 3.2.2 - it works now for me - no more acked but unack messages
m
I will have a look tomorrow or next week. Will let you know if we encounter the issue again. Thanks!
👍 2