semistone commented on issue #22601:
URL: https://github.com/apache/pulsar/issues/22601#issuecomment-2126606215

   > > I tested with that patch.. rollback all libs to version 3.2.2 and only 
replace pulsar-testclient.jar and pulsar-common.jar I also tried to run my test 
in one data center only. unfortunately it seems still reproducible. I guess 
there might be two different issues or something wrong in my test procedure :( 
let's wait and see.
   > > I may try to recreate my cluster this week as standalone server to check 
it again
   > 
   > @semistone It's better to base on 3.2.3 since there are also other issues 
where which could result in the same symptoms. I have been testing with 3.2.3 + 
patches, 
[branch-3.2...lhotari:pulsar:lh-3.2.3-patched-pulsar-perf](https://github.com/apache/pulsar/compare/branch-3.2...lhotari:pulsar:lh-3.2.3-patched-pulsar-perf)
 .
   > 
   > I'm also hitting other issues when running the repro scripts. `Key_Shared` 
subscription gets stuck very often. What I do is that I run `./produce.sh` for 
a few seconds and then starts `./start_consuming.sh` which will run 3 different 
`./consume.sh` processes in parallel with different subscriptions. That was the 
way how I triggered the problems, however I never was able to reproduce the 
partMessageMetadata error, so it's possible that you are facing yet another 
issue.
   > 
   > @semistone would you be able to share more details of your repro sequence? 
I shared complete details of my setup and repro steps in 
https://github.com/lhotari/pulsar-playground/tree/master/issues/issue22601 so 
that others could build upon it if they wish. You could decide to share what 
you wish, but obviously having more details will be helpful.
   
   I will do it later this week. 


-- 
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]

Reply via email to