semistone commented on issue #22601:
URL: https://github.com/apache/pulsar/issues/22601#issuecomment-2101968443
Hi @lhotari
I update perf tool in
https://github.com/semistone/pulsar/tree/debug_ssues_22601
it only include one commit which modify PerformanceProducer.java to include
big payload ( -bp 5 means 5 percent big payload)
and BatcherBuilder.KEY_BASED (-kb)
my consumer command is
```
bin/pulsar-perf consume persistent://my-tenant/my-namespace/my-topic-1
--auth-plugin org.apache.pulsar.client.impl.auth.AuthenticationTls
--auth-params
'{"tlsCertFile":"conf/superuser.cer","tlsKeyFile":"conf/superuser.key.pem"}' -n
10 -sp Latest -ss angus_test --batch-index-ack -st Key_Shared
```
and producer command is
```
bin/pulsar-perf produce persistent://my-tenant/my-namespace/my-topic-1 -r
6000 -kb -s 2000 -bp 5 -bm 1000 -b 1 -mk random --auth-plugin
org.apache.pulsar.client.impl.auth.AuthenticationTls --auth-params
'{"tlsCertFile":"conf/superuser.cer","tlsKeyFile":"conf/superuser.key.pem"}'
```
that error happen when
Batch builder is KEY_BASE
with random event key
and few big payload (in my environment 3% could reproduce 10% will crash
producer)
in my test
I use normal payload 2K bytes , big payload 20K bytes
if I removed any above conditions, that error will either reduced or
disappear.
when it happen it will have WARN message in pulsar-broker.log
```
2024-05-09T01:12:35,246+0000 [pulsar-io-3-31] WARN
org.apache.pulsar.broker.service.ServerCnx - [/100.96.184.253:39710] Got
exception java.lang.IllegalArgumentException: Invalid unknonwn tag type: 6
or
2024-05-09T01:12:35,260+0000 [broker-topic-workers-OrderedExecutor-15-0]
ERROR org.apache.pulsar.common.protocol.Commands -
[persistent://budas/budas-preprod-internal/bud_stream_input-partition-1]
[angus_test] Failed to peek sticky key from the message metadata
java.lang.IllegalArgumentException: Invalid unknonwn tag type: 4
```
unfortunately I can't preproduce in docker, I guess docker standalone is
different from my pulsar cluster.
my pulsar cluster is
almost default config but with TLS auth in broker/bookkeeper/zookeeper.
Please help to check it, if have any problem to reproduce this issue in your
environment,
then I will try to simplify my pulsar cluster to reproduce it.
Thanks
--
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]
