apache / apache/pulsar-client-cpp
disableReplication in MessageBuilder does not work in PulsarClient C++ and Java
- Langage dominant
- C++
- Étoiles
- 71
- Forks
- 90
- Merge moyen
- 2 h 33 min
- PR mergées (30 j)
- 3
Description
**Describe the bug**
Data is still replicated when disableReplication is enabled
**To Reproduce**
Steps to reproduce the behavior:
1. Setup Geo-Replication with 3 cluster(A,B,C)
2. Set disableReplication = true in MessageBuilder
```
Message msg = MessageBuilder().setContent("repl").disableReplication(true).build();
```
3. Producer create connect in cluster C and send ```Message msg```
```
producer.sendAsync(msg, notifySendMessage);
```
**Actual output is consumer**
1. Cluster A
```
Received message: repl
```
2. Cluster A
```
Received message: repl
```
3. Cluster C
```
Received message: repl
```
**Expected output is**
1. Cluster A
```
```
2. Cluster A
```
```
3. Cluster C
```
Received message: repl
```
Pulsar version: 2.3.0
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start by tracing MessageBuilder.disableReplication(true) through the C++ client and the producer.sendAsync path, using the three-cluster geo-replication steps to reproduce the behavior. Done means a message sent from cluster C remains in C and is not received by clusters A or B when replication is disabled.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- cpp, java
- Domaine
- distributed-systems
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100