Pulsar Geo replication is not working

2023-08-31 Thread Sathiskumar Perumal
Hi, I have followed the steps and completed the Geo replication setup as per the pulsar documentation https://pulsar.apache.org/docs/3.1.x/administration-geo/ All the geo replication related setup was enabled and working fine. When I try to produce a message from the US-WEST cluster , I am unable t

Re: Pulsar Geo replication is not working

2023-08-31 Thread Eric Shen
Hi Sathis, Did you deploy a global configure store for both US-West and US-EAST clusters? If there is no global configure store in your deployment when you create the namespaces or topics with the —clusters flag should be executed duplicately on both clusters. Because without the global config

Re: Pulsar Geo replication is not working

2023-08-31 Thread Sathiskumar Perumal
Hi Eric, Thanks for your response. I have executed the following commands. PFA. I have separate PODs for each cluster and enabled Geo replication. Can you please elaborate about the Global Configuration store or the cluster flag settings, if there is no global configuration store. Would you pleas

Re: Pulsar Geo replication is not working

2023-08-31 Thread Eric Shen
Your shared steps are not using global configuration store and both US-EAST and US-WEST are using their own zk cluster as the configuration store. To deploy with a global configuration store, you may need to follow: 1. Use a separate helm release to provision a zk-only cluster. 2. When provisioni

Re: [VOTE] PIP-264: Enhanced OTel-based metric system

2023-08-31 Thread Asaf Mesika
Thank you all for your review and corresponding votes. The PIP vote has passed with 3 binding +1 votes by Matteo, Lari and Hang. On Wed, Aug 30, 2023 at 3:40 PM Lari Hotari wrote: > +1 (binding) > > -Lari > > On Mon, Aug 28, 2023 at 5:55 PM Asaf Mesika wrote: > > > Hi, > > > > I'm very happy

Re: [DISCUSS] Consistent code style (esp. ws/indent) and autotools

2023-08-31 Thread Asaf Mesika
Opentelemetry-java employs both spotless for coding style You run "./gradlew spotlessCheck" and it shows the problems. You run "./gradlew spotlessApply" to automatically fix it. It also uses errorprone to detect bugs. I wonder if we can run it only in GitHub PRs, so we can instruct it to run only

Re: [DISCUSS] Cherry-pick #18518 into branch-2.10 and branch-2.11

2023-08-31 Thread Yubiao Feng
Cherry-picked. Since the method `isPartitionedTopicBeingDeletedAsync` only exists in `branch-3.0`, the change https://github.com/apache/pulsar/pull/18518/files#diff-38fac527320b93f0e9ea2459420f56638299627f7f29c01484f7e4aae0c5f0b7R330 was not be cherry-picked into `branch-2.10` and `branch-2.11` T

Re: [VOTE] PIP 296: Introduce the `getLastMessageIds` API to Reader

2023-08-31 Thread Xiangying Meng
Close this vote with 4 binding - Penghui - Mattison - Hang - tison On Mon, Aug 28, 2023 at 10:41 AM Zili Chen wrote: > > +1 (binding) > > Thanks for driving the proposal! > > On 2023/08/25 06:52:38 Xiangying Meng wrote: > > Hi Pulsar Community, > > > > This is the vote thread for PIP 296: > > htt

Re: [DISCUSS] Consistent code style (esp. ws/indent) and autotools

2023-08-31 Thread Zixuan Liu
This idea looks good to me, but we need to format all codebase to avoid conflicts during cherry picking. +1 Asaf Mesika 于2023年8月31日周四 20:39写道: > > Opentelemetry-java employs both spotless for coding style > You run "./gradlew spotlessCheck" and it shows the problems. > You run "./gradlew spotles

Re: [DISCUSS] Consistent code style (esp. ws/indent) and autotools

2023-08-31 Thread Dave Fisher
-0. I think it will introduce too much change. We have classes that are quite large and having to fix code style after making a small correction seems like a waste of volunteer energy. Best, Dave Sent from my iPhone > On Aug 31, 2023, at 9:05 PM, Zixuan Liu wrote: > > This idea looks good t