[jira] [Commented] (BOOKKEEPER-852) Release LedgerDescriptor and master-key objects when not used anymore

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

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

See Changes: [govindappumenon] BOOKKEEPER-1018: Allow client to select older V2 protocol (no protobuf) -- [...truncated 19.36 KB...] [INFO] [INFO] --- ma

[jira] [Commented] (BOOKKEEPER-1018) Allow client to select older V2 protocol (no protobuf)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946265#comment-15946265 ] ASF GitHub Bot commented on BOOKKEEPER-1018: GitHub user govind-menon ope

[jira] [Commented] (BOOKKEEPER-390) Provide support for ZooKeeper authentication

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

[jira] [Resolved] (BOOKKEEPER-1004) Allow bookie garbage collection to be triggered manually from tests

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

[jira] [Commented] (BOOKKEEPER-1004) Allow bookie garbage collection to be triggered manually from tests

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

[jira] [Commented] (BOOKKEEPER-852) Release LedgerDescriptor and master-key objects when not used anymore

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

[jira] [Resolved] (BOOKKEEPER-852) Release LedgerDescriptor and master-key objects when not used anymore

[ https://issues.apache.org/jira/browse/BOOKKEEPER-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo resolved BOOKKEEPER-852. -- Resolution: Fixed Issue resolved by merging pull request 78 [https://github.com/

[jira] [Resolved] (BOOKKEEPER-950) Ledger placement policy to accomodate different storage capacity of bookies

[ https://issues.apache.org/jira/browse/BOOKKEEPER-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo resolved BOOKKEEPER-950. -- Resolution: Fixed Issue resolved by merging pull request 93 [https://github.com/

[jira] [Commented] (BOOKKEEPER-950) Ledger placement policy to accomodate different storage capacity of bookies

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

Re: Support for reading entries after LAC (causal consistency driven by out-of-band communications)

Enrico what we do is, we do it at the application level. The client does // Sanity check before trying to read; Get the latest LAC. if (rquest_entryId > lh.getLastAddConfirmed()) { // Get the latest Lac. try { lh.readExplicitLastConfirmed();

Re: Support for reading entries after LAC (causal consistency driven by out-of-band communications)

Il mar 28 mar 2017, 20:57 Sijie Guo ha scritto: > On Tue, Mar 28, 2017 at 11:21 AM, Enrico Olivelli > wrote: > > > Il mar 28 mar 2017, 17:45 Venkateswara Rao Jujjuri > ha > > scritto: > > > > > We have Explicit LAC updates now, and I recall you have made it more > > > granular (milli seconds) >

Re: Support for reading entries after LAC (causal consistency driven by out-of-band communications)

On Tue, Mar 28, 2017 at 11:21 AM, Enrico Olivelli wrote: > Il mar 28 mar 2017, 17:45 Venkateswara Rao Jujjuri ha > scritto: > > > We have Explicit LAC updates now, and I recall you have made it more > > granular (milli seconds) > > given that, I am just wondering the need of your out of band > c

Re: Support for reading entries after LAC (causal consistency driven by out-of-band communications)

Il mar 28 mar 2017, 17:45 Venkateswara Rao Jujjuri ha scritto: > We have Explicit LAC updates now, and I recall you have made it more > granular (milli seconds) > given that, I am just wondering the need of your out of band communication > and taking an alternate route > in the client code. > JV

[jira] [Updated] (BOOKKEEPER-1018) Allow client to select older V2 protocol (no protobuf)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Govind Menon updated BOOKKEEPER-1018: - Description: Oriignally done by Matteo Merli (was: Oriignally done by Mattero Merli)

Re: Support for reading entries after LAC (causal consistency driven by out-of-band communications)

We have Explicit LAC updates now, and I recall you have made it more granular (milli seconds) given that, I am just wondering the need of your out of band communication and taking an alternate route in the client code. Thanks, JV On Tue, Mar 28, 2017 at 7:36 AM, Enrico Olivelli wrote: > Hi all,

[jira] [Commented] (BOOKKEEPER-1019) Support for reading entries after LAC (causal consistency driven by out-of-band communications)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945292#comment-15945292 ] Enrico Olivelli commented on BOOKKEEPER-1019: - I think that the only issu

Support for reading entries after LAC (causal consistency driven by out-of-band communications)

Hi all, I have just created this issue about a new small "feature" https://issues.apache.org/jira/browse/BOOKKEEPER-1019. The patch is very simple and I wonder if I am missing something. I'm copying the description of the issue in this email in order to start some discussion Currently we check i

[jira] [Commented] (BOOKKEEPER-1019) Support for reading entries after LAC (causal consistency driven by out-of-band communications)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945253#comment-15945253 ] Enrico Olivelli commented on BOOKKEEPER-1019: - This issue relates to BOOK

[jira] [Created] (BOOKKEEPER-1019) Support for reading entries after LAC (causal consistency driven by out-of-band comunications)

Enrico Olivelli created BOOKKEEPER-1019: --- Summary: Support for reading entries after LAC (causal consistency driven by out-of-band comunications) Key: BOOKKEEPER-1019 URL: https://issues.apache.org/jira/brow

[jira] [Updated] (BOOKKEEPER-1019) Support for reading entries after LAC (causal consistency driven by out-of-band communications)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated BOOKKEEPER-1019: Summary: Support for reading entries after LAC (causal consistency driven by ou

Build failed in Jenkins: bookkeeper-master #1701

See -- [...truncated 22.70 KB...] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.032 sec - in org.apache.bookkeeper.test.AsyncLedgerOpsTest Running org.apache.bookkee