[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350033#comment-14350033
]
James Taylor edited comment on PHOENIX-1674 at 3/6/15 6:19 PM:
---------------------------------------------------------------
[~lhofhansl] - any questions from your end? I seem to remember you wondering if
three transaction managers can run (1 active, 2 stand-bys).
Can these be co-located with RSs (and does that make sense)? Would it be
possible to communicate to them via an EndPoint coprocessor and even run in the
same JVM as the RS? Not that Tephra may want to always work this way, but for
Phoenix I think it'd make sense, as we're already pinging the RS (as mentioned
above) to ensure our metadata is up to date, so there'd be no extra overhead.
It'd also negate any issues with ensuring a separate, new service is up and
running.
was (Author: jamestaylor):
[~lhofhansl] - any questions from your end? I seem to remember you wondering if
three transaction managers can run (1 active, 2 stand-bys).
Can these be co-located with RSs (and does that make sense)? Would it be
possible to communicate to them via an EndPoint coprocessor and even run in the
same JVM as the RS?
> Snapshot isolation transaction support through Tephra
> -----------------------------------------------------
>
> Key: PHOENIX-1674
> URL: https://issues.apache.org/jira/browse/PHOENIX-1674
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
>
> Tephra (http://tephra.io/ and https://github.com/caskdata/tephra) is one
> option for getting transaction support in Phoenix. Let's use this JIRA to
> discuss the way in which this could be integrated along with the pros and
> cons.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
