Re: [VOTE] Pulsar 1.19.0-incubating Release Candidate 0

+1. I ran the regression-tests and few of the load-tests with this version and looks fine. Thanks, Rajan On Wed, Aug 2, 2017 at 1:36 PM, Dave Fisher wrote: > Hi - > > I will cast an IPMC vote. > > +1 Release! > > I checked the source and binary package hashes. > I built

Re: CI builds on Jenkins

> Another option would be to make the Jenkins build status non-mandatory for merging the PRs. Then we might want to be careful before merging because flaky tests might be failing due to genuine reason or bug. Probably, we can keep it enable for sometime and disable if we really think that flaky

Re: [DISCUSS] PIP-1 Pulsar proxy component

>> or if people prefer we can create a GitHub issue to have the discussion on the proposal I think github issue would be more helpful for discussion. so, my vote to github-issue. Thanks, Rajan On Thu, Jun 29, 2017 at 1:51 PM, Matteo Merli wrote: > I have created the wiki

Re: [VOTE] Pulsar 1.20.0-incubating Release Candidate 0

> - Verified Notice info related to cryptography in bin and src distribution > > Andrews. > > On Mon, Oct 2, 2017 at 2:06 PM, Rajan Dhabalia <rdhaba...@apache.org> > wrote: > > We can find closed and open items for this milestone: > > Closed: https://github.com/apache/inc

Re: [GitHub] merlimat commented on issue #742: Avoid huge backlog on topic reloading: due to large gap between markDelete-offset and read-position of cursor.

> and leave normal queue consumption out of this mechanism, (to reduce the ZK writes) >> To be precise, these are BookKeeper writes that would be happening anyway Just to clarify: Broker also stores ack-holes in ZK along with BK (Cursor-ledger). But Broker only writes it to ZK when broker unloads

Re: Add EventTime to pulsar messages

at an application can use a (string -> string) property, > though it would be a custom field and it will need to be in string format > and also carry the field name. I think event time is general enough to be > considered as a built-in field and exposed in API. > > Matteo > >

Re: Add EventTime to pulsar messages

> because this field might be accessed when processing every message. the overhead in key/value property is much higher than an int64 field. I have the same concern as Andrews mentioned. But a very quick implementation question: properties

Re: [DRAFT] Podling report

Looks good. Thanks, Rajan On Wed, Dec 6, 2017 at 10:10 AM, Matteo Merli wrote: > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. It provides simple pub-sub semantics over topics, > guaranteed at-least-once delivery of messages,

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

+1 (binding) Environment: Mac-OS 10.12.6 Checked: - signatures and checksum - start standalone service and producer/consumer client test (Src/Bin distribution) - rat check on Src distribution - compile and unit test on src distribution - maven repository artifacts Thanks, Rajan On Mon,

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

+1 (binding) Environment: Mac-OS 10.12.6 Checked: - signatures and checksum - maven repository artifacts - start standalone service and client-test for producer/consumer (src/bin distribution) - rat check on src distribution - compile and unit test on src distribution Thanks, Rajan On

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

+1 (binding) Environment: Mac-OS 10.12.6 Checked: - signatures and checksum - maven repository artifacts - start standalone service and client-test for producer/consumer (src/bin distribution) - rat check on src distribution - compile and unit test on src distribution Thanks, Rajan On

Re: pulsar-master build failures

Hi Prono, Thanks for letting us know. We had an issue earlier with one of our test: PulsarSinkE2ETes which was hanging and not finishing up due to one of the bug. Later we had fixed it and added the timeout to the test so, it should not generating big logs anymore. We have fixed this issue on

Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 1

+1 (binding) Environment: Mac-OS 10.12.6 Checked: - signatures and checksum - maven repository artifacts - start standalone service and client-test for producer/consumer (src/bin distribution) - rat check on src distribution - compile and unit test on src distribution Environment: REHL-6.7

Re: [PROPOSAL] Planning for next releases

Hi, Yes, we can target 1.22.0-incubating release by reviewing and merging pending PRs by end of this month and then we can prepare for 2.0 release. >> Also, are there any volunteers for release managers for both releases? Sure, I can be release manager for 1.22.0-incubating. Thanks, Rajan On

Re: PIP 20: Mechanism to revoke TLS authentication

Hi, Here, we would like to configure "subject-key-identifier" at every broker in the cluster dynamically. We also want to perform certain actions once this configuration-value has been changed. Broker's dynamic configuration is introduced for such usecases where dynamic-config value gets stored

Re: PIP 20: Mechanism to revoke TLS authentication

> I will consider both this and system topics and update the PIP. I think we should avoid more complexity by introducing system topic to store "subject key" and then process it. Instead we can store it to global/config zk as it requires to store keys with few bytes. I think dynamic-configuration

Re: [DRAFT] Graduation resolution proposal

lly > * Jai Asher > * Jia Zhai > * Jim Jagielski > * Joe Francis > * Ludwig Pummer > * Masahiro Sakamoto > * Masakazu Kitajo > * Matteo Merli > * Nozomi Kurihara

Re: [DRAFT] Podling report

+1. Thanks, Rajan Sent from my iPhone > On Sep 5, 2018, at 5:36 PM, Matteo Merli wrote: > > Sorry for sending out at very last minute (deadline is today). Please take > a look. > > I have added a paragraph regarding the branding discussion that happen in > early June (as discussed with

Re: [VOTE] Graduation resolution proposal

t; * Jia Zhai > * Jim Jagielski > * Joe Francis > * Ludwig Pummer > * Masahiro Sakamoto > * Masakazu Kitajo > * Matteo Merli > * Nozomi Kurihara > * P. Taylor Goetz > *