Re: [DISCUESS] PIP 57: Improve Broker's Zookeeper Session Timeout Handling

On Sat, Feb 22, 2020 at 6:28 PM PengHui Li wrote: > Hi, joe > > The fundamental correctness is guaranteed by the fencing mechanism > provided by Apache BookKeeper and the CAS operation provided by the > metadata storage. Both fencing and CAS operations will prevent two owners > updating data or m

Re: [DISCUESS] PIP 57: Improve Broker's Zookeeper Session Timeout Handling

Hi, joe The fundamental correctness is guaranteed by the fencing mechanism provided by Apache BookKeeper and the CAS operation provided by the metadata storage. Both fencing and CAS operations will prevent two owners updating data or metadata at the same time. This default shutdown behavior isn

Re: [DISCUESS] PIP 57: Improve Broker's Zookeeper Session Timeout Handling

My concerns are listed in the PR comments. A broker is allowed to operate on a (resource) bundle under a lock. When a broker loses its session, the lock ownership COULD be lost. The right thing at this point is to give up the resource and re-acquire it. ( In fact, shutdown is just a shortcut to do

Slack digest for #dev - 2020-02-22

2020-02-21 10:21:31 UTC - Jon Bennett: @Jon Bennett has joined the channel 2020-02-21 17:01:27 UTC - rani: @rani has joined the channel 2020-02-22 00:07:20 UTC - Roman Popenov: @Roman Popenov has joined the channel 2020-02-22 00:08:57 UTC - Roman Popenov: Hello! I am running into iss

Build failed in Jenkins: pulsar-website-build #916

See Changes: [github] Fix CI not triggered (#6397) [github] [Issue 6355][HELM] autorecovery - could not find or load main class -- [...truncated 3.32 MB...] [WARNING]

Re: Pulsar Release 2.5.1 Discussion

Thanks Guangning E work for this. LGTM +1 -- Thanks Xiaolong Ran > 在 2020年2月22日，下午4:52，Guangning E 写道： > > Hi everyone, > > There are a few bug fixes and enhancement for 2.5.0. And the planned 2.5.0 > the release has past due by a few days. Of course, according to PIP47, we > can also consid

Pulsar Release 2.5.1 Discussion

Hi everyone, There are a few bug fixes and enhancement for 2.5.0. And the planned 2.5.0 the release has past due by a few days. Of course, according to PIP47, we can also consider starting to discuss the release of 2.5.1. It would be good to start cut the release soon. I would like to volunteer f