Jenkins build is still unstable: distributedlog-nightly-build #77

See

October 2016 Podling Report Draft Feedback

I have reviewed the current draft of the next podling report. http://wiki.apache.org/incubator/October2016 This looks good, but I’m also wondering if we can give any more specific updates about progress toward a first Apache release.  I know there has been some discussion of this (e.g. th

Re: Proxy Client - Batch Ordering / Commit

> > So, my basic question is if this is currently possible in the proxy? I > don't believe it gives these guarantees as it stands today, but I am not > 100% of how all of the futures in the code handle failures. > As long as you use this method

Re: Proxy Client - Batch Ordering / Commit

Main question I have then is what happens in the case of retry due to network failure, where the client doesn't get a success response, but it succeeds / will succeed proxy server side? What do I have to ensure that no duplicates are written to distributedlog in such a case? -Cameron On Wed, Oct

Re: Proxy Client - Batch Ordering / Commit

There is no automatic dedup or key based update. In failure scenarios you would need to recover by reading the latest id, and retry based on this. Would that work? On Wed, Oct 5, 2016 at 2:02 PM, Cameron Hatfield wrote: > Main question I have then is what happens in the case of retry due to >

Re: Proxy Client - Batch Ordering / Commit

Basically, its point 6 above. What ends up being the timeout for me to ensure that a result is committed or not, so that I guarantee a read actually gives me the last value?? -Cameron On Wed, Oct 5, 2016 at 2:51 PM, Leigh Stewart wrote: > There is no automatic dedup or key based update. > > In