-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retryable Exception #343
Comments
Can you share your reproduction code? |
I face the same issue when deploying with 3.1.x docker-compose. If I worker:
restart: unless-stopped
networks:
- pulsar
command: node src/worker.js
environment:
REDIS_URL: redis://redis:6379
PULSAR_URL: pulsar://broker:6650
build:
context: .
deploy:
replicas: 3
depends_on:
zookeeper:
condition: service_healthy
redis:
condition: service_healthy
bookie:
condition: service_started
redis:
image: redis:7
networks:
- pulsar
volumes:
- ./redis-data:/data
command: redis-server --io-threads 4 --io-threads-do-reads yes --appendonly no --maxmemory-policy noeviction --bind 0.0.0.0 --maxclients 100000 --tcp-backlog 100000
healthcheck:
test: [ "CMD", "redis-cli", "--raw", "incr", "ping" ]
interval: 3s
timeout: 5s
retries: 5 I got this error I verified that Producer code is also default, if simplified: const URL = process.env.PULSAR_URL || 'pulsar://127.0.0.1:6650';
export const client = new PulsarClient.Client({serviceUrl: URL});
await client.createProducer({topic: 'my-topic',sendTimeoutMs: 1000}).catch(console.error); UPD Fixed it by changing env variable for broker service from |
@tomasantunes For your information , I reproduce the trouble with the 1.11.0 of the pulsar-client, but no trouble with 1.10.0 ... |
I'm getting the following error when trying to create a producer with Pulsar Node JS client:
The text was updated successfully, but these errors were encountered: