geo-replication AuthenticationException: Unable to authenticate
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
#### Actual behavior
##### broker.log
16:18:10.795 [pulsar-io-4-16] WARN org.apache.pulsar.broker.service.AbstractReplicator - [persistent://public/x01/iot-signal-canlog-testtwo-partition-0][pulsar-cluster-ontest-1 -> pulsar-ontest] Failed to create remote producer (org.apache.pulsar.client.api.PulsarClientException$AuthenticationException: Unable to authenticate), retrying in 57.915 s
##### source cluster name: pulsar-cluster-ontest-1
##### target cluster name: pulsar-ontest
##### Configure the target cluster information in the source cluster
##### Target cluster enable geo-replication at namespace level
#### System configuration
**Pulsar version**: 2.9.1
Contributor guide
Research direction
Start with broker.log and the source/target cluster configuration described in the issue, then reproduce geo-replication on Pulsar 2.9.1 with namespace-level replication enabled. Trace the failed remote-producer authentication between pulsar-cluster-ontest-1 and pulsar-ontest; done means replication authenticates without the logged AuthenticationException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100