Re: High-availability for transactions

2018-11-09 Thread James Taylor
Hi Curtis, The omid2 branch is up to date with 4.x-hbase-1.3 and we’ll merge it once the Omid release is complete (vote will start on Mon). Pedro is the main one maintaining the CDH branches, so this work should make it into a 4.15 CDH release. If you have some spare cycles, I’m sure he could use

Re: High-availability for transactions

2018-11-07 Thread Curtis Howard
Hi James, Great - thanks very much for confirming Omid will be available on 4.x branches - that includes the cdh/Cloudera branches as well? Would you have any suggestions on the best approach to merging 'omid2' branch work with say, 4.14-cdh5.14? Curtis On Tue, Nov 6, 2018 at 3:28 PM James

Re: High-availability for transactions

2018-11-06 Thread James Taylor
The Omid integration will be available on all active 4.x branches (1.2, 1.3, and 1.4) as well as on 5.x. The Omid integration has the same unit test coverage as Tephra. If you want to give it a spin, let us know. You'd just need to pull the phoenix-integration branch for Omid and the omid2 branch

Re: High-availability for transactions

2018-11-05 Thread Curtis Howard
Hi Omid, Thanks for the quick reply. When the Omid/Phoenix integration is complete, will it be released only with Phoenix 5.x, or will it also be integrated and tested with 4.14.x branches? Can you comment at all on what level of testing the integration will have had, once released? (will it be

Re: High-availability for transactions

2018-11-05 Thread Ohad Shacham
Hi Curtis, Omid does provide high availability for transactions, you can find the full technical details in here: https://www.usenix.org/conference/fast17/technical-sessions/presentation/shacham In a nutshell, in-flight transactions in this case are aborted by the transaction manager, they are