Open yebai1105 opened 1 year ago
Could you try the latest Python client? The retry logic was introduced since 3.0.0.
pulsar-client=3.1.0,I tried this version too, but there is also a problem
I tried this version too, but there is also a problem
Is the issue the same one? Or if you can provide logs on 3.1.0.
I got same error on pulsar-client 3.1.0
code: `from pulsar import Client, AuthenticationToken,BatchingType client = Client( service_url='pulsar://node01.public.pulsar.test:6650', authentication=AuthenticationToken( "xxxxxxxxxxxxxxxxxxxxxxxxx")) producer = client.create_producer( 'my-topic', block_if_queue_full=True, batching_enabled=True, batching_max_publish_delay_ms=10, properties={ "producer-name": "test-producer-name", "producer-id": "test-producer-id" }, batching_type=BatchingType.KeyBased )
for i in range(10): producer.send(('Hello-%d' % i).encode('utf-8'))
client.close()`
log:
`Connected to pydev debugger (build 213.7172.26)
2023-12-21 11:29:56.580 INFO [140635486381888] ClientConnection:190 | [
Process finished with exit code 1 `
I have same issue with Java pulsar client & pulsar 3.2 when I enabled authentication: authenticationEnabled=true
PulsarClient client = PulsarClient.builder() .serviceUrl("pulsar://127.0.0.1:6650") .authentication(AuthenticationFactory.token(token)) .build();
Describe the bug If you fail to get topic partition metadata through service_url, it will not retry and try to connect to other ip, and will directly exit abnormally after the connection fails pulsar-client=2.9.4
To Reproduce 1、Test Conditions 127.0.0.1:6650 The corresponding service is closed 127.0.0.2:6650 service is normal 2、Test code
error log
Expected behavior Within the timeout period, if the connection fails to be obtained, a retry is initiated Such as the processing method of java client: