szkoludasebastian commented on issue #22709:
URL: https://github.com/apache/pulsar/issues/22709#issuecomment-2134827997

   > > I was building that from our gitlab-ci which we use always when building 
our own image based on apachepulsar/pulsar:{version} image. When I build it 
with version 3.2.2 everything is correct and when I build it with 3.2.3 I've 
got this mentioned error. I pulled also to my local both images from our ECR 
and it's linux/amd64
   > 
   > Do you have a change to test the 3.2.3 images available at 
`apachepulsar/pulsar:3.2.3` or `apachepulsar/pulsar-all:3.2.3` on DockerHub? 
Those were built with commands in the release guide, 
https://pulsar.apache.org/contribute/release-process/#release-pulsar-30-and-later
 .
   
   As I said before, I built image using this 
   
![image](https://github.com/apache/pulsar/assets/141229367/7ce93331-f095-4190-a917-46eca08abbfb)
   so I tested my scenario on version 3.2.3 and I was still able to observe 
message loss there.


-- 
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: commits-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to