phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-2653) Used data.tx.zookeeper.quorum property while initializing TransactionServiceClient falling back to HBase ZK quorum setting
Date Fri, 05 Feb 2016 17:37:39 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-2653:
----------------------------------
    Summary: Used data.tx.zookeeper.quorum property while initializing TransactionServiceClient
falling back to HBase ZK quorum setting  (was: Provide a way for users to override the zookeeperQuorum
used while initializing TransactionServiceClient by setting the "data.tx.zookeeper.quorum"
property )

> Used data.tx.zookeeper.quorum property while initializing TransactionServiceClient falling
back to HBase ZK quorum setting
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2653
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2653
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Thomas D'Silva
>            Assignee: Thomas D'Silva
>             Fix For: 4.7.0
>
>
> From an email discussion with [~poornachandra] [~gokulavasan]
> CDAP's transaction manager's discovery information in zookeeper uses a namespace. The
regular znode to discover tx manager is /discoverable/transaction, but for CDAP's tx manager
it is /cdap/discoverable/transaction, and can change based on CDAP's root.namespace value.
> Picking up the zk connection string from connection info in fine in most cases. We'll
just need a way for user's to override that by setting "data.tx.zookeeper.quorum" in a config
file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message