Build failed in Jenkins: distributedlog-nightly-build #89

See -- [...truncated 150 lines...] [WARNING]

Best practices

The best practices page says in "write ordering" , use the core api if you need strict write order in the log. Can I have a little more clarity what this means. I assumed that whether I use the fat or thin client that the writes I make would be ordered in the log in bk. I assume I am misunderstan

Re: Best practices

When using core api, there can be only one writer at a given time. so when the writer issues two writes, the two writes will be in the time order of when they were written. However when using thin client, there can be multiple writers. the order of the writes coming from different writers is deter

Re: Proxy Client - Batch Ordering / Commit

Cameron, Thank you for your summary. I liked the discussion here. I also liked the summary of your requirement - 'single-writer-per-key, multiple-writers-per-log'. If I understand correctly, the core concern here is almost 'exact-once' write (or a way to explicit tell if a write can be retried or

Re: Proxy Client - Batch Ordering / Commit

Answer inline: On Mon, Oct 17, 2016 at 11:46 AM, Sijie Guo wrote: > Cameron, > > Thank you for your summary. I liked the discussion here. I also liked the > summary of your requirement - 'single-writer-per-key, > multiple-writers-per-log'. If I understand correctly, the core concern here > is al