Re: 3.5.7

> Would you have time for a quick fix ? The measures to avoid the problem are listed at the end of the JIRA description. I can't submit a PR until I get permission from my company legal to push to ZK. -Ivan

Re: 3.5.7

> "Log disk filling up is a pretty easy position to get yourself into.” - > Agreed, which can be easily avoided with proper monitoring. We had monitoring set up to alarm at 80%, but for some reason it didn't trigger. Each node only hit 100% for less than an hour, as the PurgeTxnLog kicked in

Re: 3.5.7

bug. > > Andor > > > > > > On 2020. Jan 22., at 11:21, Ivan Kelly wrote: > > > > We discovered a split brain bug last week, which should probably be > > fixed before any new release. ZOOKEEPER-3701. > > > > -Ivan > > > > On Wed, Jan 22, 2020 at 1

Re: 3.5.7

We discovered a split brain bug last week, which should probably be fixed before any new release. ZOOKEEPER-3701. -Ivan On Wed, Jan 22, 2020 at 11:13 AM Andor Molnar wrote: > > Makes perfect sense. I just committed both. > > Thanks, > Andor > > > > > On 2020. Jan 22., at 6:57, Szalay-Bekő Máté

[jira] [Created] (ZOOKEEPER-3701) Split brain on log disk full

Ivan Kelly created ZOOKEEPER-3701: - Summary: Split brain on log disk full Key: ZOOKEEPER-3701 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3701 Project: ZooKeeper Issue Type: Bug

[jira] [Commented] (ZOOKEEPER-3066) Expose on JMX of Followers the id of the current leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517117#comment-16517117 ] Ivan Kelly commented on ZOOKEEPER-3066: --- It would also be useful to have this available via

Re: Review Request 47354: ZOOKEEPER-1045 : Quorum mutual authentication using SASL mechanism

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/47354/#review134333 --- Ship it! Ship It! - Ivan Kelly On May 20, 2016, 3:10 a.m

Re: [VOTE] Apache ZooKeeper release 3.4.8 candidate 0

+1 - Verified checksums and sig - Licensing looks good (though there are jars without attribution in contrib/, but this isn't anything new) - ant test ran cleanly - Ran client and server code through our CI. Nothing broke. - ant releaseaudit ran cleanly Good work Raul! -Ivan On Wed, Feb 17,

[jira] [Commented] (ZOOKEEPER-1045) Quorum Peer mutual authentication

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098287#comment-15098287 ] Ivan Kelly commented on ZOOKEEPER-1045: --- {quote}Two concerns that I have

[jira] [Commented] (ZOOKEEPER-2353) QuorumCnxManager protocol needs to be upgradable with-in a specific Version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098376#comment-15098376 ] Ivan Kelly commented on ZOOKEEPER-2353: --- [~fpj] 3.4.8 will be in the same situation as all

Re: [VOTE] Remove release 3.4.7 from mirrors and Web site references

+1 On Sun, Dec 20, 2015 at 7:21 PM, Chris Nauroth wrote: > +1 non-binding (assuming this is like a "Product Release" vote, where only > PMC votes are binding) > > --Chris Nauroth > > > > > On 12/20/15, 7:29 AM, "Flavio Junqueira" wrote: > >>As per our

Re: [DISCUSS] Remove 3.4.7 from mirrors and the Web site references

> A slightly separate issue is what to do with 3.4.7. It is a bad release and > we don't want folks using it, so I started this discussion to determine what > to do with it. I'm suggesting we remove it from mirrors and from the web > site, just like we did with 3.3.1 back in the day. +1 for

Re: [DISCUSS] Remove 3.4.7 from mirrors and the Web site references

> The specific issue is described and it is being discussed in ZOOKEEPER-2347. > Please share your opinion about the 3.4.7 release in this thread. It looks like there's already a fix for the issue and very little has gone into 3.4 since the release, so why no release a 3.4.8? -Ivan

Re: [DISCUSS] Remove 3.4.7 from mirrors and the Web site references

> +1 on removing 3.4.7. If others speak up soon I can go ahead and remove > 3.4.7 from the website/archive and get started with the RC.. Just to clarify, you'll only remove the archive and not touch the maven repo? The issue is only in the server, and people are already using the client via maven

Re: [DISCUSS] Remove 3.4.7 from mirrors and the Web site references

> The same fixes that are in 3.4.7 will be in 3.4.8, and we'll add the one to > the deadlock. I was thinking that we should remove it from the maven repo too > and ask people to move their dependencies back to 3.4.6. I'm fine if you want > to hold removing 3.4.7 from the maven repo until we

Re: [DISCUSS] Using Apache Yetus Pre-Commit for Zookeeper

> - We should move away from ant and start using either maven or gradle. There > is a patch (ZOOKEEPER-1078) for maven by phunt, but hasn't been able to > finish it. I'm very supportive of making this move. +1000 for this. > - I'd rather be using git at this point, so someone would need to the

Re: [DISCUSS] Using Apache Yetus Pre-Commit for Zookeeper

On Sun, Dec 13, 2015 at 12:18 AM, Chris Nauroth wrote: > I'd like to propose that we migrate the ZooKeeper pre-commit process to use > Apache Yetus [1]. +1. This looks very cool. -Ivan

Re: Documentation For Writing ZooKeeper Client

> I'm trying to find documentation about the ZooKeeper protocol from the > perspective of a client talking to a server cluster. Is there a suggested > place to find that kind of documentation, or would I be better off just > reading other client's source code? I've never seen nor heard of such a

Re: [VOTE] Apache ZooKeeper release 3.4.7 candidate 0

+1 Checked checksums/sig. Ran release-audit/test (passed). Eyeballed licences, they seem ok. Put it through the CI for our application (passed). Good job Raul! -Ivan On Tue, Nov 17, 2015 at 11:41 PM, Patrick Hunt wrote: > I just noticed that the netty jar includes it's own

Re: QOP SASL property

@hortonworks.com> > wrote: > > > > I filed ZOOKEEPER-2289 to track adding support for the full set of QOP > > settings. I did not target any specific fix version since there isn't > > consensus yet on that. Thank you, Flavio and Ivan. > > > > --Chris Naur

Re: QOP SASL property

anges. > > -Flavio > > > On 09 Oct 2015, at 15:30, Ivan Kelly <iv...@apache.org> wrote: > > > > IMO, adding QOP to 3.4 would be a fairly large and invasive change, which > > is something which shouldn't be done on the stable branch. > > > > -Ivan >

Re: QOP SASL property

Is auth-int necessary if we have SSL on the client (as there is in trunk)? My understanding is that all comms would have to be wrapped by sasl if you have QOP enabled. -Ivan On Fri, Oct 9, 2015 at 9:42 AM Flavio Junqueira wrote: > Hi Chris, > > Yeah, I was thinking along the

Re: QOP SASL property

he moment. > > -Flavio > > > On 09 Oct 2015, at 15:00, Ivan Kelly <iv...@apache.org> wrote: > > > > Is auth-int necessary if we have SSL on the client (as there is in > trunk)? > > My understanding is that all comms would have to be wrapped by sasl if > you >

Re: QOP SASL property

orry > about repeated wrapping and unwrapping. However, even if we set up > something like these classes in ZooKeeper, it appears the ZooKeeper > codebase isn't structured to make inserting those wrappers easy. > > This does look like it would be more invasive than I originally descr

Re: QOP SASL property

> Ok, got it, but it sounds like we can just wrap and unwrap the bytes we > are sending, no? Do you think that will end up being a lot of changes? > > -Flavio > > > On 09 Oct 2015, at 15:38, Ivan Kelly <iv...@apache.org> wrote: > > > > To protect th

[jira] [Commented] (ZOOKEEPER-2277) Zookeeper off-line snapshot and transaction log viewer

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791050#comment-14791050 ] Ivan Kelly commented on ZOOKEEPER-2277: --- Maybe you want to have a look at: https://github.com

[jira] [Commented] (ZOOKEEPER-2243) Supported platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14718490#comment-14718490 ] Ivan Kelly commented on ZOOKEEPER-2243: --- Ok. Lets check in again once there's

[jira] [Commented] (ZOOKEEPER-2243) Supported platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704541#comment-14704541 ] Ivan Kelly commented on ZOOKEEPER-2243: --- I wouldn't even try to support

[jira] [Updated] (ZOOKEEPER-2243) Supports platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-2243: -- Description: http://zookeeper.apache.org/doc/r3.4.6/zookeeperAdmin.html

[jira] [Updated] (ZOOKEEPER-2243) Supported platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-2243: -- Summary: Supported platforms is completely out of date (was: Supports platforms

[jira] [Created] (ZOOKEEPER-2243) Supports platforms is completely out of date

Ivan Kelly created ZOOKEEPER-2243: - Summary: Supports platforms is completely out of date Key: ZOOKEEPER-2243 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2243 Project: ZooKeeper

[jira] [Updated] (ZOOKEEPER-2243) Supports platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-2243: -- Fix Version/s: 3.6.0 3.5.2 3.4.7 Supports platforms

[jira] [Commented] (ZOOKEEPER-2243) Supported platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681586#comment-14681586 ] Ivan Kelly commented on ZOOKEEPER-2243: --- That solaris build on jenkins hasn't

[jira] [Commented] (ZOOKEEPER-2243) Supported platforms is completely out of date

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681744#comment-14681744 ] Ivan Kelly commented on ZOOKEEPER-2243: --- In that case, I think Windows (and Mac

[jira] [Updated] (ZOOKEEPER-2237) Port async multi to 3.4 branch

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated ZOOKEEPER-2237: -- Attachment: 0001-ZOOKEEPER-2237-Port-async-multi-to-3.4-branch.patch Port async multi

[jira] [Commented] (ZOOKEEPER-2237) Port async multi to 3.4 branch

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647670#comment-14647670 ] Ivan Kelly commented on ZOOKEEPER-2237: --- [~hustlmsp] [~rakeshr] This patch

Re: [VOTE] Apache ZooKeeper release 3.5.1-alpha candidate 4

+1 lgtm I checked the checksums and sig. Built and tested with ant jar Checked the licenses Ran it against our internal QA system. -Ivan On Tue, Jul 28, 2015 at 10:03 AM Michi Mutsuzaki mutsuz...@gmail.com wrote: This is the fifth release candidate for 3.5.1-alpha. There are 6 commits since

[jira] [Commented] (ZOOKEEPER-2237) Port async multi to 3.4 branch

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647805#comment-14647805 ] Ivan Kelly commented on ZOOKEEPER-2237: --- Thanks for taking a look. Hadoop QA

[jira] [Created] (ZOOKEEPER-2237) Port async multi to 3.4 branch

Ivan Kelly created ZOOKEEPER-2237: - Summary: Port async multi to 3.4 branch Key: ZOOKEEPER-2237 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2237 Project: ZooKeeper Issue Type: Sub

[jira] [Commented] (ZOOKEEPER-1572) Add an async interface for multi request

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645777#comment-14645777 ] Ivan Kelly commented on ZOOKEEPER-1572: --- This would be good to have on the 3.4

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640855#comment-14640855 ] Ivan Kelly commented on ZOOKEEPER-2235: --- lgtm +1 License update

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640441#comment-14640441 ] Ivan Kelly commented on ZOOKEEPER-2235: --- As the patch is, the LICENSE and NOTICE

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638740#comment-14638740 ] Ivan Kelly commented on ZOOKEEPER-2235: --- For jline, I don't think anything new

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14637012#comment-14637012 ] Ivan Kelly commented on ZOOKEEPER-2235: --- For the missing notices, I found

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635558#comment-14635558 ] Ivan Kelly commented on ZOOKEEPER-2235: --- I'll take a look tomorrow. License

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632743#comment-14632743 ] Ivan Kelly commented on ZOOKEEPER-2235: --- My understanding

Re: [VOTE] Apache ZooKeeper release 3.5.1-alpha candidate 3

. That's the longest release process ever in this project! -Flavio On 16 Jul 2015, at 12:41, Ivan Kelly iv...@apache.org wrote: Hi Michi, -1 The tarball contains a bunch of jars(under lib), but there is no mention of these in the NOTICE file. Perhaps phunt

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632853#comment-14632853 ] Ivan Kelly commented on ZOOKEEPER-2235: --- {quote}All files under META-INF

[jira] [Commented] (ZOOKEEPER-2235) License update

[ https://issues.apache.org/jira/browse/ZOOKEEPER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632607#comment-14632607 ] Ivan Kelly commented on ZOOKEEPER-2235: --- The jackson jars are not ASF, even

Re: [VOTE] Apache ZooKeeper release 3.5.1-alpha candidate 3

Hi Michi, -1 The tarball contains a bunch of jars(under lib), but there is no mention of these in the NOTICE file. Perhaps phunt knows whether this is ok, but my understanding is that if you are distributing the binaries, you need to mention them in the NOTICE. Apart from that the release looks

Configuration service for zookeeper

Hey folks, I've just had an discussion about how zookeeper is harder to configure than etcd or consul for example. See: https://coreos.com/docs/cluster-management/setup/cluster-discovery/ As I understand it, they have a central quorum that they use for recording requests for new node

[jira] [Assigned] (BOOKKEEPER-806) Please create a DOAP file for your TLP

[ https://issues.apache.org/jira/browse/BOOKKEEPER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly reassigned BOOKKEEPER-806: - Assignee: Ivan Kelly Please create a DOAP file for your TLP

[jira] [Commented] (BOOKKEEPER-770) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/BOOKKEEPER-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227453#comment-14227453 ] Ivan Kelly commented on BOOKKEEPER-770: --- 4.2.3 is current also. 4.3.0 contains

[jira] [Commented] (BOOKKEEPER-806) Please create a DOAP file for your TLP

[ https://issues.apache.org/jira/browse/BOOKKEEPER-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227456#comment-14227456 ] Ivan Kelly commented on BOOKKEEPER-806: --- Added. It has the current info for now

[jira] [Commented] (BOOKKEEPER-770) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/BOOKKEEPER-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227454#comment-14227454 ] Ivan Kelly commented on BOOKKEEPER-770: --- I'll remove the others. Please

[jira] [Commented] (BOOKKEEPER-770) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/BOOKKEEPER-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14227477#comment-14227477 ] Ivan Kelly commented on BOOKKEEPER-770: --- removed all but 4.2.3 and 4.3.0

[jira] [Commented] (BOOKKEEPER-805) NullPointException in bookie server when using twitter-ostrich-provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224453#comment-14224453 ] Ivan Kelly commented on BOOKKEEPER-805: --- Best for [~hustlmsp] to review

Re: Office

First thing I added. The permissions are available straight away. Waiting on infra now (INFRA-8697) On 25 November 2014 at 14:29, Flavio Junqueira fpjunque...@yahoo.com.invalid wrote: We already have an office entry and a VP on the foundation page! http://www.apache.org/foundation/ -Flavio

IMPORTANT: Do not commit anything

Hi folks, As you'll have seen, we're going TLP. This means our source needs to be moved out from under Zookeeper. Therefore, don't commit anything until after this has happened. The umbrella jira for the move is https://issues.apache.org/jira/browse/INFRA-8697 Cheers, Ivan

[jira] [Commented] (BOOKKEEPER-804) Client program is not terminated when using openLedgerNoRecovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222965#comment-14222965 ] Ivan Kelly commented on BOOKKEEPER-804: --- Strange, it only happens if you call

[jira] [Assigned] (BOOKKEEPER-804) Client program is not terminated when using openLedgerNoRecovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly reassigned BOOKKEEPER-804: - Assignee: Ivan Kelly Client program is not terminated when using

[jira] [Updated] (BOOKKEEPER-804) Client program is not terminated when using openLedgerNoRecovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-804: -- Fix Version/s: 4.3.1 4.4.0 Client program is not terminated when using

[jira] [Commented] (BOOKKEEPER-804) Client program is not terminated when using openLedgerNoRecovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223074#comment-14223074 ] Ivan Kelly commented on BOOKKEEPER-804: --- The problem came in with BOOKKEEPER-654

[jira] [Updated] (BOOKKEEPER-804) Client program is not terminated when using openLedgerNoRecovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-804: -- Attachment: 0001-BOOKKEEPER-804-Client-program-is-not-terminated-when.patch Client program

[jira] [Updated] (BOOKKEEPER-804) Client program is not terminated when using openLedgerNoRecovery

[ https://issues.apache.org/jira/browse/BOOKKEEPER-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-804: -- Attachment: 0001-BOOKKEEPER-804-Client-program-is-not-terminated-when.patch Actually

[jira] [Created] (BOOKKEEPER-799) Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum

Ivan Kelly created BOOKKEEPER-799: - Summary: Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum Key: BOOKKEEPER-799 URL: https://issues.apache.org/jira

[jira] [Updated] (BOOKKEEPER-799) Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum

[ https://issues.apache.org/jira/browse/BOOKKEEPER-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-799: -- Attachment: 0001-BOOKKEEPER-799-Distribution-schedule-coverage-sets-d.patch Fix is to check

Review Request 28326: BOOKKEEPER-799 Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum

/28326/diff/ Testing --- Thanks, Ivan Kelly

[jira] [Commented] (BOOKKEEPER-799) Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum

[ https://issues.apache.org/jira/browse/BOOKKEEPER-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220801#comment-14220801 ] Ivan Kelly commented on BOOKKEEPER-799: --- https://reviews.apache.org/r/28326

[jira] [Updated] (BOOKKEEPER-799) Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum

[ https://issues.apache.org/jira/browse/BOOKKEEPER-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-799: -- Fix Version/s: 4.3.1 Distribution schedule coverage sets don't take gaps in response lists

[jira] [Commented] (BOOKKEEPER-799) Distribution schedule coverage sets don't take gaps in response lists into account when writequorum ackquorum

[ https://issues.apache.org/jira/browse/BOOKKEEPER-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220892#comment-14220892 ] Ivan Kelly commented on BOOKKEEPER-799: --- I think that once this is in we should

[jira] [Created] (BOOKKEEPER-800) Expose whether a ledger is closed or not

Ivan Kelly created BOOKKEEPER-800: - Summary: Expose whether a ledger is closed or not Key: BOOKKEEPER-800 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-800 Project: Bookkeeper Issue

[jira] [Updated] (BOOKKEEPER-800) Expose whether a ledger is closed or not

[ https://issues.apache.org/jira/browse/BOOKKEEPER-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-800: -- Attachment: 0001-Expose-whether-a-ledger-has-been-closed.patch Expose whether a ledger

[jira] [Commented] (BOOKKEEPER-800) Expose whether a ledger is closed or not

[ https://issues.apache.org/jira/browse/BOOKKEEPER-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220912#comment-14220912 ] Ivan Kelly commented on BOOKKEEPER-800: --- patch is trivial Expose whether

[jira] [Updated] (BOOKKEEPER-800) Expose whether a ledger is closed or not

[ https://issues.apache.org/jira/browse/BOOKKEEPER-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-800: -- Attachment: 0001-Expose-whether-a-ledger-has-been-closed.patch Had forgotten to commit

[jira] [Created] (BOOKKEEPER-801) Bookkeeper client tutorial

Ivan Kelly created BOOKKEEPER-801: - Summary: Bookkeeper client tutorial Key: BOOKKEEPER-801 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-801 Project: Bookkeeper Issue Type: Bug

[jira] [Updated] (BOOKKEEPER-801) Bookkeeper client tutorial

[ https://issues.apache.org/jira/browse/BOOKKEEPER-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-801: -- Attachment: 0001-Bookkeeper-tutorial.patch Postprocessing it looks like: http

[jira] [Created] (BOOKKEEPER-798) Make website look more modern

Ivan Kelly created BOOKKEEPER-798: - Summary: Make website look more modern Key: BOOKKEEPER-798 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-798 Project: Bookkeeper Issue Type: Bug

[jira] [Updated] (BOOKKEEPER-798) Make website look more modern

[ https://issues.apache.org/jira/browse/BOOKKEEPER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-798: -- Attachment: 0001-Adding-bootstrap-resources-for-site-reboot.patch 0001-Make

Re: NativeIO?

NativeIO is linux only i think, I don't think mac's have fadvise. -Ivan On 15 November 2014 18:03, Flavio Junqueira fpjunque...@yahoo.com.invalid wrote: I just noticed this message when running on my mac laptop: [BookieJournal-3183:NativeIO@43] - Unable to link C library. Native methods

Review Request 28119: Documentation: The bookkeeper protocol

bk_protocol.txt https://reviews.apache.org/media/uploaded/files/2014/11/17/f47f48e9-c284-4473-b4e9-584b24af7a14__bk_protocol.txt Thanks, Ivan Kelly

Re: Review Request 28119: Documentation: The bookkeeper protocol

://reviews.apache.org//r/28119/#fcomment54 I really should have spellchecked :/ - Ivan Kelly On Nov. 17, 2014, 2:58 p.m., Ivan Kelly wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28119

Re: Synchronous calls in asynchronous callbacks for bookie auto recovery

I wasn't aware of this. No objections to changing it. In fact, I actively encourage it. -Ivan On 14 November 2014 01:56, Sijie Guo guosi...@gmail.com wrote: Hi guys: I am revisiting the auto-recovery code. There were tons of synchronous calls in asynchronous callbacks (zookeeper/bookkeeper

Re: Review Request 27529: BOOKKEEPER-795 Race condition causes writes to hang if ledger is fences

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27529/#review60997 --- On Nov. 3, 2014, 5:02 p.m., Ivan Kelly wrote

Re: Review Request 27529: BOOKKEEPER-795 Race condition causes writes to hang if ledger is fences

Thanks, Ivan Kelly

[jira] [Updated] (BOOKKEEPER-795) Race condition causes writes to hang if ledger is fences

[ https://issues.apache.org/jira/browse/BOOKKEEPER-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-795: -- Attachment: 0001-Made-ledger-metadata-immutable.patch Race condition causes writes to hang

[jira] [Commented] (BOOKKEEPER-705) handle session expire event in bookie server bookie watcher

[ https://issues.apache.org/jira/browse/BOOKKEEPER-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209958#comment-14209958 ] Ivan Kelly commented on BOOKKEEPER-705: --- Over a year later :/ I made an attempt

Re: Zookeeper availability coupling in bookkeeper

the session expiry event on client server side. - Sijie On Fri, Nov 7, 2014 at 7:11 AM, Ivan Kelly iv...@apache.org wrote: Hi folks, Currently bookie lifetime is dependent on the zookeeper session which the bookie was started with. This is bad, and unnecessary and something that has

[jira] [Created] (BOOKKEEPER-796) Make bookkeeper client use reconnectable zookeeper wrapper

Ivan Kelly created BOOKKEEPER-796: - Summary: Make bookkeeper client use reconnectable zookeeper wrapper Key: BOOKKEEPER-796 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-796 Project

[jira] [Updated] (BOOKKEEPER-796) Make bookkeeper client use reconnectable zookeeper wrapper

[ https://issues.apache.org/jira/browse/BOOKKEEPER-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-796: -- Issue Type: Sub-task (was: Bug) Parent: BOOKKEEPER-537 Make bookkeeper client use

[jira] [Updated] (BOOKKEEPER-796) Make bookkeeper client use reconnectable zookeeper wrapper

[ https://issues.apache.org/jira/browse/BOOKKEEPER-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-796: -- Attachment: 0001-BOOKKEEPER-796-Make-bookkeeper-client-use-reconnecta.patch Make

[jira] [Commented] (BOOKKEEPER-796) Make bookkeeper client use reconnectable zookeeper wrapper

[ https://issues.apache.org/jira/browse/BOOKKEEPER-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14204954#comment-14204954 ] Ivan Kelly commented on BOOKKEEPER-796: --- Patch has two parts. Firstly, it hooks

Zookeeper availability coupling in bookkeeper

Hi folks, Currently bookie lifetime is dependent on the zookeeper session which the bookie was started with. This is bad, and unnecessary and something that has causes us some downtime here. I have a fix for this available, but before I put up the patch, I'd like to know if anyone has also fixed

[jira] [Commented] (BOOKKEEPER-788) Provide release inspector script

[ https://issues.apache.org/jira/browse/BOOKKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194727#comment-14194727 ] Ivan Kelly commented on BOOKKEEPER-788: --- [~jiannan] [~fpj] I was referring

[jira] [Updated] (BOOKKEEPER-795) Race condition causes writes to hang if ledger is fences

[ https://issues.apache.org/jira/browse/BOOKKEEPER-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-795: -- Attachment: 0001-Made-ledger-metadata-immutable.patch Patch makes LedgerMetadata immutable

Review Request 27529: BOOKKEEPER-795 Race condition causes writes to hang if ledger is fences

-server/src/test/java/org/apache/bookkeeper/test/ConditionalSetTest.java a06accd Diff: https://reviews.apache.org/r/27529/diff/ Testing --- All tests pass Thanks, Ivan Kelly

[jira] [Commented] (BOOKKEEPER-795) Race condition causes writes to hang if ledger is fences

[ https://issues.apache.org/jira/browse/BOOKKEEPER-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194734#comment-14194734 ] Ivan Kelly commented on BOOKKEEPER-795: --- Review board: https

[jira] [Created] (BOOKKEEPER-795) Race condition causes writes to hang if ledger is fences

Ivan Kelly created BOOKKEEPER-795: - Summary: Race condition causes writes to hang if ledger is fences Key: BOOKKEEPER-795 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-795 Project: Bookkeeper

[jira] [Updated] (BOOKKEEPER-795) Race condition causes writes to hang if ledger is fences

[ https://issues.apache.org/jira/browse/BOOKKEEPER-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-795: -- Attachment: TEST-org.apache.bookkeeper.client.LedgerCloseTest.xml 0001

Re: [VOTE] Taking Bookkeeper Subproject to a Top Level Project

this is the IPMC, so in our case I guess it would be the Zookeeper PMC. Perhaps @phunt, @tdunning or @mahadev could give guidance here, given their position on IPMC? -Ivan On 17 October 2014 15:26, Ivan Kelly iv...@apache.org wrote: Hi folks, I'd like to run a community vote on converting the Bookkeeper

  1   2   3   4   5   6   7   8   9   10   >