[jira] [Resolved] (BOOKKEEPER-1055) Optimize handling of masterKey in case it is empty

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli resolved BOOKKEEPER-1055. - Resolution: Fixed Issue resolved by merging pull request 156 [htt

[jira] [Commented] (BOOKKEEPER-1055) Optimize handling of masterKey in case it is empty

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013640#comment-16013640 ] ASF GitHub Bot commented on BOOKKEEPER-1055: Github user asfgit closed th

[GitHub] bookkeeper pull request #156: BOOKKEEPER-1055: Optimize handling of masterKe...

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/156 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Build failed in Jenkins: bookkeeper-master-git-pullrequest #383

See Changes: [mmerli] BOOKKEEPER-1055: Optimize handling of masterKey in case it is empty [mmerli] Removed unneeded check for all zeroes master key [mmerli] Addressed findbugs issues --

[jira] [Commented] (BOOKKEEPER-1055) Optimize handling of masterKey in case it is empty

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012969#comment-16012969 ] ASF GitHub Bot commented on BOOKKEEPER-1055: Github user merlimat comment

[GitHub] bookkeeper issue #156: BOOKKEEPER-1055: Optimize handling of masterKey in ca...

Github user merlimat commented on the issue: https://github.com/apache/bookkeeper/pull/156 @eolivelli Sure, I'll fix that. Thanks for checking it out ! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[jira] [Commented] (BOOKKEEPER-1028) inc/excl opts listunderreplicate

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012968#comment-16012968 ] ASF GitHub Bot commented on BOOKKEEPER-1028: Github user reddycharan comm

[GitHub] bookkeeper issue #127: BOOKKEEPER-1028 and BOOKKEEPER-1029

Github user reddycharan commented on the issue: https://github.com/apache/bookkeeper/pull/127 sure, will do. I was just waiting for full code review and comments, so that I can address all of them at once. Thanks, Charan --- If your project is set up for it, you can rep

Build failed in Jenkins: bookkeeper-master #1751

See -- [...truncated 47.86 KB...] org.apache.bookkeeper.client.BKException$BKLedgerRecoveryException at org.apache.bookkeeper.client.BookieRecoveryTest.ensurePasswordUsedForOldL

Re: Bookie labels and Placement policy

We have this use case too. I believe introducing "pools" Is the right approach for this. Pools are very high level abstraction and it is treated as simply two different clusters, but wrapped into one. Some of the high level thoughts: * Pools are top level abstraction. * Pool is assigned at the ti

Re: Client-Bookie Protocol Enhancements.

Please note that I started this thread to stir up discussion.. not my final proposals. On Tue, May 16, 2017 at 1:02 AM, Sijie Guo wrote: > On May 16, 2017 12:09 AM, "Enrico Olivelli - Diennea" < > enrico.olive...@diennea.com> wrote: > > Il giorno mar, 16/05/2017 alle 00.06 -0700, Sijie Guo ha s

Re: Bookie labels and Placement policy

OK so I am not keen on the idea of labels.  Probably because when I have seen it done in the past (YARN) it just felt like a hack that was trying to avoid fixing the real underlying problem. YARN wanted to schedule for arbitrary resources but that is hard so they went with Node Labels instead. 

Re: Publish SNAPSHOT artifacts on Maven Central

2017-05-03 11:23 GMT+02:00 Sijie Guo : > Gotcha. Let me check the wiki. (I am currently traveling.) I will try to > get this ready for you when I have a better access to internet. > Did you have time to check this activity ? Thanks -- Enrico > - Sijie > > On Tue, May 2, 2017 at 8:48 PM, Enrico

Re: Bookie labels and Placement policy

2017-05-16 15:53 GMT+02:00 Sijie Guo : > My personal feeling is the use cases are so different across organizations. > It would be really hard to design a **standard** policy for such things. > What is your major concern of customizing your own placement policy? The first step I would like to do i

Re: Bookie labels and Placement policy

My personal feeling is the use cases are so different across organizations. It would be really hard to design a **standard** policy for such things. What is your major concern of customizing your own placement policy? - Sijie On Tue, May 16, 2017 at 4:05 AM, Enrico Olivelli wrote: > Hi bookkeep

[jira] [Commented] (BOOKKEEPER-1008) Move to netty4

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012400#comment-16012400 ] Hudson commented on BOOKKEEPER-1008: FAILURE: Integrated in Jenkins build bookkee

[jira] [Commented] (BOOKKEEPER-1058) Ignore already deleted ledger on replication audit

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012398#comment-16012398 ] Hudson commented on BOOKKEEPER-1058: FAILURE: Integrated in Jenkins build bookkee

[jira] [Commented] (BOOKKEEPER-1061) BookieWatcher should not do ZK blocking operations from ZK async callback thread

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012402#comment-16012402 ] Hudson commented on BOOKKEEPER-1061: FAILURE: Integrated in Jenkins build bookkee

[jira] [Commented] (BOOKKEEPER-1069) If client uses V2 proto, set the connection to always decode V2 messages

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012404#comment-16012404 ] Hudson commented on BOOKKEEPER-1069: FAILURE: Integrated in Jenkins build bookkee

[jira] [Commented] (BOOKKEEPER-1067) Add Prometheus stats provider

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012401#comment-16012401 ] Hudson commented on BOOKKEEPER-1067: FAILURE: Integrated in Jenkins build bookkee

[jira] [Commented] (BOOKKEEPER-1048) Use ByteBuf in LedgerStorageInterface

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012403#comment-16012403 ] Hudson commented on BOOKKEEPER-1048: FAILURE: Integrated in Jenkins build bookkee

Build failed in Jenkins: bookkeeper-master #1750

See Changes: [sijie] BOOKKEEPER-1058: Ignore already deleted ledger on replication audit [sijie] BOOKKEEPER-1008: Netty 4.1 [sijie] BOOKKEEPER-1067: Add Prometheus stats provider [sijie] BOOKKEEPER-1061: Book

[GitHub] bookkeeper issue #156: BOOKKEEPER-1055: Optimize handling of masterKey in ca...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/156 I was trying to merge, but FindBugs check failed, @merlimat can you fix the warnings ? ``` [INFO] BugInstance size is 3 [INFO] Error size is 0 [INFO] Total bugs: 3 [

[jira] [Commented] (BOOKKEEPER-1055) Optimize handling of masterKey in case it is empty

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012183#comment-16012183 ] ASF GitHub Bot commented on BOOKKEEPER-1055: Github user eolivelli commen

[jira] [Commented] (BOOKKEEPER-1069) If client uses V2 proto, set the connection to always decode V2 messages

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012177#comment-16012177 ] ASF GitHub Bot commented on BOOKKEEPER-1069: Github user asfgit closed th

[GitHub] bookkeeper pull request #157: BOOKKEEPER-1069: If client uses V2 proto, set ...

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/157 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Bookie labels and Placement policy

Hi bookkeepers, I'm using BookKeeper for serveral projects, every project has its own workload characteristics and I would like to be able to assign bookies depending of the client type. It is quite common to share a BookKeeper cluster between different applications. For instance I am using Bookie

Re: Client-Bookie Protocol Enhancements.

On May 16, 2017 12:09 AM, "Enrico Olivelli - Diennea" < enrico.olive...@diennea.com> wrote: Il giorno mar, 16/05/2017 alle 00.06 -0700, Sijie Guo ha scritto: On Mon, May 15, 2017 at 10:35 PM, Venkateswara Rao Jujjuri < jujj...@gmail.com> wrote: As we are moving toward

Re: Client-Bookie Protocol Enhancements.

Il giorno mar, 16/05/2017 alle 00.06 -0700, Sijie Guo ha scritto: On Mon, May 15, 2017 at 10:35 PM, Venkateswara Rao Jujjuri < jujj...@gmail.com> wrote: As we are moving towards mega store, which can house 10s of millions(even 100s) of ledgers, and 1000s of bookies, th

Re: Client-Bookie Protocol Enhancements.

On Mon, May 15, 2017 at 10:35 PM, Venkateswara Rao Jujjuri < jujj...@gmail.com> wrote: > As we are moving towards mega store, which can house 10s of millions(even > 100s) of ledgers, and 1000s of bookies, there can be a huge overhead on > some of the operations we are performing right now. > > 1.