[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=16034058#comment-16034058 ] 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 @eolivelli @sijie fixed rat check warnings you mentioned. Yes 'decommissionbookie' bkshell command has to be executed in the node, which is being decommissioned. added consi

[jira] [Commented] (BOOKKEEPER-1088) Ledger Recovery - Add a ReadEntryListener to callback on individual request

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

[GitHub] bookkeeper issue #178: BOOKKEEPER-1088: Ledger Recovery - Add a ReadEntryLis...

Github user jvrao commented on the issue: https://github.com/apache/bookkeeper/pull/178 LGTM --- 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 feat

[jira] [Commented] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

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

[GitHub] bookkeeper issue #168: BOOKKEEPER-989: Enable Travis CI for Apache BookKeepe...

Github user jvrao commented on the issue: https://github.com/apache/bookkeeper/pull/168 Is the plan to move to Travis from Jenkins?? Any reason to go with Travis instead of Circle? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] bookkeeper issue #174: BOOKKEEPER-748: Move fence requests out of read threa...

Github user jiazhai commented on the issue: https://github.com/apache/bookkeeper/pull/174 This is a great feature. --- 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 wis

[jira] [Commented] (BOOKKEEPER-748) Move fence requests out of read threads

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

[jira] [Commented] (BOOKKEEPER-1041) Multiple active entrylogs

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033958#comment-16033958 ] Charan Reddy Guttapalem commented on BOOKKEEPER-1041: - [~si...@ap

[jira] [Commented] (BOOKKEEPER-944) Multiple issues and improvements to BK Compaction.

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

[GitHub] bookkeeper issue #108: BOOKKEEPER-944: LowWaterMark Storage Threshold

Github user reddycharan commented on the issue: https://github.com/apache/bookkeeper/pull/108 @sijie @eolivelli resolved merge conflicts and added more description to the commit as we discussed in todays call. Thanks. --- If your project is set up for it, you can reply to this email

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

To add more context, this topic was discussed recently at ApacheCon. See this talk https://www.youtube.com/watch?v=yWurOHvm5WM Relevant portion start at 18:00. In short, they are saying that the ASF is trying to leverage Github more and more in the future. Matteo On Thu, Jun 1, 2017 at 4:48 PM

[jira] [Commented] (BOOKKEEPER-757) Ledger Recovery Improvement

[ https://issues.apache.org/jira/browse/BOOKKEEPER-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033931#comment-16033931 ] Sijie Guo commented on BOOKKEEPER-757: -- actually missed one change. > Ledger Rec

[jira] [Created] (BOOKKEEPER-1092) Ledger Recovery - parallel ledger metadata update with bookie entries recovery proceedure

Sijie Guo created BOOKKEEPER-1092: - Summary: Ledger Recovery - parallel ledger metadata update with bookie entries recovery proceedure Key: BOOKKEEPER-1092 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-109

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

I think the biggest advantage is JIRA has very good workflow management. Github issues doesn't have such feature. But projects like docker, k8s are using labels for such management. I think more and more large projects (non ASF) are using Github for both issues, pull requests and code. They might a

[jira] [Commented] (BOOKKEEPER-1090) Use LOG.isDebugEnabled() to avoid unexpected allocations

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

[GitHub] bookkeeper issue #179: BOOKKEEPER-1090: Use LOG.isDebugEnabled() to avoid un...

Github user jvrao commented on the issue: https://github.com/apache/bookkeeper/pull/179 can't we come up with a macro to wrap this? Chane looks fine to me though. +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If you

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

I agree, having one place is more convenient. But what is the feature parity between Jira and Github? Here is what I found by googling. https://confluence.sakaiproject.org/display/PMC/Github+Issues+vs+Jira+pros+and+cons On Thu, Jun 1, 2017 at 2:59 PM, Sijie Guo wrote: > Actually thinking a bit m

Re: [VOTE] Use Github Issues for Issue Tracking

+1 Having issues and PR in one tool is a great plus. If this proposal is accepted, we should also ask INFRA to allow to assign issues/PRs to committers/contributors and to create labels that fit our workflow. On Thu, Jun 1, 2017 at 3:03 PM Sijie Guo wrote: > My vote on this is +1. > > Simply

Re: [VOTE] Use Github Issues for Issue Tracking

My vote on this is +1. Simply because I'd like to have one central place for tracking issues and reviewing pull requests. - Sijie On Thu, Jun 1, 2017 at 12:59 PM, Sijie Guo wrote: > Per the community meeting > >

Re: [DISCUSS] Issue Tracking - Jira or Github Issues

Actually thinking a bit more, I think there is a bit inconvenient in current approach (JIRA for issue tracking and PR for patches). Each time I went to github for reviewing pull requests. I have to go back to JIRA (by copying the JIRA id and typing the URL) to check the descriptions and discussions

[jira] [Commented] (BOOKKEEPER-1090) Use LOG.isDebugEnabled() to avoid unexpected allocations

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

[GitHub] bookkeeper pull request #179: BOOKKEEPER-1090: Use LOG.isDebugEnabled() to a...

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/179 --- 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

[jira] [Created] (BOOKKEEPER-1091) Remove Hedwig from BookKeeper website page

Sijie Guo created BOOKKEEPER-1091: - Summary: Remove Hedwig from BookKeeper website page Key: BOOKKEEPER-1091 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1091 Project: Bookkeeper Iss

[jira] [Commented] (BOOKKEEPER-1087) Ledger Recovery - Add a parallel reading request in PendingReadOp

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

[GitHub] bookkeeper issue #177: BOOKKEEPER-1087: Ledger Recovery - Add a parallel rea...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/177 @sijie got it. Sorry. I will only proceed with reviews. Just wanted to help --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If yo

[jira] [Commented] (BOOKKEEPER-1090) Use LOG.isDebugEnabled() to avoid unexpected allocations

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033714#comment-16033714 ] Sijie Guo commented on BOOKKEEPER-1090: --- +1 I liked this idea. > Use LOG.isDeb

[jira] [Commented] (BOOKKEEPER-1090) Use LOG.isDebugEnabled() to avoid unexpected allocations

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

[GitHub] bookkeeper pull request #179: BOOKKEEPER-1090: Use LOG.isDebugEnabled() to a...

GitHub user merlimat opened a pull request: https://github.com/apache/bookkeeper/pull/179 BOOKKEEPER-1090: Use LOG.isDebugEnabled() to avoid unexpected allocations Using `LOG.debug(...)` can lead to multiple unexpected memory allocation, even when the logger it's turned off. For

[jira] [Created] (BOOKKEEPER-1090) Use LOG.isDebugEnabled() to avoid unexpected allocations

Matteo Merli created BOOKKEEPER-1090: Summary: Use LOG.isDebugEnabled() to avoid unexpected allocations Key: BOOKKEEPER-1090 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1090 Project: Book

[jira] [Commented] (BOOKKEEPER-748) Move fence requests out of read threads

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

[GitHub] bookkeeper issue #174: BOOKKEEPER-748: Move fence requests out of read threa...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/174 The CI passed (refs/remotes/origin/pr/174/head) at https://builds.apache.org/job/bookkeeper-precommit-pullrequest/21/ --- If your project is set up for it, you can reply to this email and have yo

[jira] [Commented] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

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

[GitHub] bookkeeper pull request #168: BOOKKEEPER-989: Enable Travis CI for Apache Bo...

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/168 --- 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

[jira] [Resolved] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

[ https://issues.apache.org/jira/browse/BOOKKEEPER-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo resolved BOOKKEEPER-989. -- Resolution: Fixed Fix Version/s: 4.5.0 Issue resolved by merging pull request 168

[jira] [Commented] (BOOKKEEPER-1088) Ledger Recovery - Add a ReadEntryListener to callback on individual request

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033683#comment-16033683 ] ASF GitHub Bot commented on BOOKKEEPER-1088: GitHub user sijie opened a p

[GitHub] bookkeeper pull request #178: BOOKKEEPER-1088: Ledger Recovery - Add a ReadE...

GitHub user sijie opened a pull request: https://github.com/apache/bookkeeper/pull/178 BOOKKEEPER-1088: Ledger Recovery - Add a ReadEntryListener to callback on individual request THIS CHANGE IS BASED ON #177 (you can review 868a3c8 for the only change that belongs to BOOKKEEPER-1

[jira] [Commented] (BOOKKEEPER-1087) Ledger Recovery - Add a parallel reading request in PendingReadOp

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

[GitHub] bookkeeper issue #177: BOOKKEEPER-1087: Ledger Recovery - Add a parallel rea...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/177 @eolivelli I think a better approach is to complete the reviews for all the sub-tasks for a given master JIRA before merging. otherwise, I have to rebase every time you merged. for example

[jira] [Commented] (BOOKKEEPER-1087) Ledger Recovery - Add a parallel reading request in PendingReadOp

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

[GitHub] bookkeeper issue #177: BOOKKEEPER-1087: Ledger Recovery - Add a parallel rea...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/177 @sijie I have merged #176 maybe you will have to rebase --- 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

[jira] [Commented] (BOOKKEEPER-1086) Ledger Recovery - Refactor PendingReadOp

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

[jira] [Resolved] (BOOKKEEPER-1086) Ledger Recovery - Refactor PendingReadOp

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

[GitHub] bookkeeper pull request #176: BOOKKEEPER-1086: Ledger Recovery - Refactor Pe...

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/176 --- 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

[GitHub] bookkeeper issue #168: BOOKKEEPER-989: Enable Travis CI for Apache BookKeepe...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/168 Ok Il gio 1 giu 2017, 22:35 Sijie Guo ha scritto: > @eolivelli @merlimat > @jiazhai

[jira] [Commented] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

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

[jira] [Commented] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

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

[GitHub] bookkeeper issue #168: BOOKKEEPER-989: Enable Travis CI for Apache BookKeepe...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/168 Ok --- 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 fe

[jira] [Commented] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

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

[GitHub] bookkeeper issue #168: BOOKKEEPER-989: Enable Travis CI for Apache BookKeepe...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/168 @eolivelli @merlimat @jiazhai if there is no objections, I am going to merge this one. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as wel

Re: [VOTE] Use Github Issues for Issue Tracking

+1 let's try github Il gio 1 giu 2017, 21:59 Sijie Guo ha scritto: > Per the community meeting > < > https://cwiki.apache.org/confluence/display/BOOKKEEPER/2017-06-01+Meeting+notes > > > this morning, JV proposed to start use Github issues for issue tracking for > a few months and see how does i

[jira] [Commented] (BOOKKEEPER-1087) Ledger Recovery - Add a parallel reading request in PendingReadOp

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033579#comment-16033579 ] ASF GitHub Bot commented on BOOKKEEPER-1087: GitHub user sijie opened a p

[GitHub] bookkeeper pull request #177: BOOKKEEPER-1087: Ledger Recovery - Add a paral...

GitHub user sijie opened a pull request: https://github.com/apache/bookkeeper/pull/177 BOOKKEEPER-1087: Ledger Recovery - Add a parallel reading request in PendingReadOp THIS CHANGE IS BASED ON #176 (you can review f0fb89c) bookkeeper recovery improvement (part-2): add a pa

[VOTE] Use Github Issues for Issue Tracking

Per the community meeting this morning, JV proposed to start use Github issues for issue tracking for a few months and see how does it work out. I am starting this email thread to vote for this. The vote will be: -

[jira] [Commented] (BOOKKEEPER-1086) Ledger Recovery - Refactor PendingReadOp

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

[GitHub] bookkeeper issue #176: BOOKKEEPER-1086: Ledger Recovery - Refactor PendingRe...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/176 @eolivelli no this is from my changes. --- 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 ena

[jira] [Commented] (BOOKKEEPER-1086) Ledger Recovery - Refactor PendingReadOp

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

[GitHub] bookkeeper issue #176: BOOKKEEPER-1086: Ledger Recovery - Refactor PendingRe...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/176 @sijie did you tell that we should mark some other contributor for this sequence of patches? Exact names? --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Resolved] (BOOKKEEPER-1056) Removed PacketHeader serialization/deserialization allocation

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

[jira] [Commented] (BOOKKEEPER-1056) Removed PacketHeader serialization/deserialization allocation

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

[GitHub] bookkeeper pull request #175: BOOKKEEPER-1056: Removed PacketHeader serializ...

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/175 --- 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

[GitHub] bookkeeper pull request #176: BOOKKEEPER-1086: Ledger Recovery - Refactor Pe...

GitHub user sijie opened a pull request: https://github.com/apache/bookkeeper/pull/176 BOOKKEEPER-1086: Ledger Recovery - Refactor PendingReadOp this change is the first part of improving ledger recovery. it is basically a refactor change, which: - abstract an interface for

[jira] [Commented] (BOOKKEEPER-1086) Ledger Recovery - Refactor PendingReadOp

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033521#comment-16033521 ] ASF GitHub Bot commented on BOOKKEEPER-1086: GitHub user sijie opened a p

[jira] [Commented] (BOOKKEEPER-989) Enable travis CI for bookkeeper git

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

[GitHub] bookkeeper issue #168: BOOKKEEPER-989: Enable Travis CI for Apache BookKeepe...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/168 https://travis-ci.org/apache/bookkeeper/jobs/238455091 somehow the tests are taking much longer time than they are running on jenkins (or laptop). ` Running org.apache.bookkeeper.client

[jira] [Created] (BOOKKEEPER-1089) Ledger Recovery - allow batch reads in ledger recovery

Sijie Guo created BOOKKEEPER-1089: - Summary: Ledger Recovery - allow batch reads in ledger recovery Key: BOOKKEEPER-1089 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1089 Project: Bookkeeper

[jira] [Created] (BOOKKEEPER-1088) Ledger Recovery - Add a ReadEntryListener to callback on individual request

Sijie Guo created BOOKKEEPER-1088: - Summary: Ledger Recovery - Add a ReadEntryListener to callback on individual request Key: BOOKKEEPER-1088 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1088

[jira] [Created] (BOOKKEEPER-1087) Ledger Recovery - Add a parallel reading request in PendingReadOp

Sijie Guo created BOOKKEEPER-1087: - Summary: Ledger Recovery - Add a parallel reading request in PendingReadOp Key: BOOKKEEPER-1087 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1087 Project:

[jira] [Created] (BOOKKEEPER-1086) Ledger Recovery - Refactor PendingReadOp

Sijie Guo created BOOKKEEPER-1086: - Summary: Ledger Recovery - Refactor PendingReadOp Key: BOOKKEEPER-1086 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1086 Project: Bookkeeper Issue

[GitHub] bookkeeper issue #175: BOOKKEEPER-1056: Removed PacketHeader serialization/d...

Github user eolivelli commented on the issue: https://github.com/apache/bookkeeper/pull/175 +1 --- 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 fe

[jira] [Commented] (BOOKKEEPER-1056) Removed PacketHeader serialization/deserialization allocation

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

[jira] [Commented] (BOOKKEEPER-1056) Removed PacketHeader serialization/deserialization allocation

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

[GitHub] bookkeeper issue #175: BOOKKEEPER-1056: Removed PacketHeader serialization/d...

Github user jvrao commented on the issue: https://github.com/apache/bookkeeper/pull/175 +1 --- 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 featur

[jira] [Commented] (BOOKKEEPER-1056) Removed PacketHeader serialization/deserialization allocation

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

[GitHub] bookkeeper issue #175: BOOKKEEPER-1056: Removed PacketHeader serialization/d...

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/pull/175 The CI (https://builds.apache.org/job/bookkeeper-precommit-pullrequest/17/) passed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

Re: Jenkins Pull-Request Build

Yeah. I updated the description for the master job. (yes. this wiki page is cloned from DL.) On Thu, Jun 1, 2017 at 11:14 AM, Enrico Olivelli wrote: > Great! > There is a reference to distributed log I think. > > Maybe you should mention that the master job now deploys snapshots to > repository

Re: Jenkins Pull-Request Build

Great! There is a reference to distributed log I think. Maybe you should mention that the master job now deploys snapshots to repository.apache.org Enrico Il gio 1 giu 2017, 20:10 Sijie Guo ha scritto: > Cleaned up the jenkins jobs. > > Also put up a wiki page documenting this - > > https://cw

Re: Jenkins Pull-Request Build

Cleaned up the jenkins jobs. Also put up a wiki page documenting this - https://cwiki.apache.org/confluence/display/BOOKKEEPER/Continuous+Integration+Setup - Sijie On Thu, Jun 1, 2017 at 11:05 AM, Enrico Olivelli wrote: > Yep. > Consider deleting the 'look for patches' job as we are only using

Re: Jenkins Pull-Request Build

Yep. Consider deleting the 'look for patches' job as we are only using github now Il gio 1 giu 2017, 19:56 Sijie Guo ha scritto: > since there is no objection coming up, deleting the broken > "bookkeeper-master-git-pullrequest" jenkins job. > > - Sijie > > On Thu, Jun 1, 2017 at 12:50 AM, Sijie

Re: Jenkins Pull-Request Build

since there is no objection coming up, deleting the broken "bookkeeper-master-git-pullrequest" jenkins job. - Sijie On Thu, Jun 1, 2017 at 12:50 AM, Sijie Guo wrote: > Hi all, > > Currently, the bookkeeper-master-git-pullrequest [1] build is broken due > to failing to find the "mvn" command. Th

[GitHub] bookkeeper issue #165: Apache BookKeeper Tutorial Implemented with Scala

Github user sijie commented on the issue: https://github.com/apache/bookkeeper/issues/165 @jvrao re "a separate git repo" - current java tutorial is a tutorial wrote by @ivankelly , it is not in bookkeeper's repo. a tutorial is just a sample application to show how t

[GitHub] bookkeeper issue #165: Apache BookKeeper Tutorial Implemented with Scala

Github user jvrao commented on the issue: https://github.com/apache/bookkeeper/issues/165 Sorry for being naive on this subject. What is the real use of implementing tutorial in Scala? and have a separate git repo for it? --- If your project is set up for it, you can reply to this em

Re: Agenda for community meeting this week

FYI Meeting minutes : https://cwiki.apache.org/confluence/display/BOOKKEEPER/2017-06-01+Meeting+notes - Sijie On Wed, May 31, 2017 at 1:14 AM, Enrico Olivelli wrote: > 2017-05-31 2:31 GMT+02:00 Sijie Guo : > > Hi all, > > > > Anyone wants to put up an agenda for community meeting this week? >

[jira] [Commented] (BOOKKEEPER-1056) Removed PacketHeader serialization/deserialization allocation

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

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

See Changes: [mmerli] BOOKKEEPER-1056: Removed PacketHeader serialization/deserialization -- GitHub pull request #175 to apache/bookkeeper [EnvInject] - Lo

[GitHub] bookkeeper pull request #175: BOOKKEEPER-1056: Removed PacketHeader serializ...

GitHub user merlimat opened a pull request: https://github.com/apache/bookkeeper/pull/175 BOOKKEEPER-1056: Removed PacketHeader serialization/deserialization allocation When parsing the request packet header, use static methods to avoid creating a `PacketHeader` instance. You can

[jira] [Commented] (BOOKKEEPER-1074) Remove JMX Bean

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

[GitHub] bookkeeper issue #161: BOOKKEEPER-1074: Remove JMX Bean

Github user reddycharan commented on the issue: https://github.com/apache/bookkeeper/pull/161 @jvrao @sijie we are using JMX not just for metrics (getters) but also for invoking actions, like forcecompact, forceflush,.. It is the easiest way to do out-of-band inter process communicati

[jira] [Commented] (BOOKKEEPER-1074) Remove JMX Bean

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

Jenkins build is back to stable : bookkeeper-master #1771

See

Re: Official Bookkeeper Docker Image

Thanks Sijie, I will re-read docker hub guidelines and write the proposal accordingly. Alas, I had no time for refreshing the topic, so I think that discussing it is useless in today meeting, but I think that in the next one I will be ready. On Wed, 2017-05-31 at 13:12 -0700, Sijie Guo wrote:

[jira] [Commented] (BOOKKEEPER-1071) BookieRecoveryTest is failing due to a Netty4 IllegalReferenceCountException

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

[jira] [Commented] (BOOKKEEPER-1084) Make variables finale if necessary

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

[jira] [Commented] (BOOKKEEPER-1073) Several stats provider related changes.

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

[jira] [Commented] (BOOKKEEPER-1083) Improvements on OrderedSafeExecutor

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

[jira] [Commented] (BOOKKEEPER-1085) Introduce the AlertStatsLogger

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

[jira] [Commented] (BOOKKEEPER-1078) Local BookKeeper enhancements for testability

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

[jira] [Resolved] (BOOKKEEPER-1074) Remove JMX Bean

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

[jira] [Commented] (BOOKKEEPER-1074) Remove JMX Bean

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

[GitHub] bookkeeper pull request #161: BOOKKEEPER-1074: Remove JMX Bean

Github user asfgit closed the pull request at: https://github.com/apache/bookkeeper/pull/161 --- 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

  1   2   >