[ 
https://issues.apache.org/jira/browse/TAJO-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234915#comment-14234915
 ] 

ASF GitHub Bot commented on TAJO-1221:
--------------------------------------

GitHub user blrunner opened a pull request:

    https://github.com/apache/tajo/pull/286

    TAJO-1221: HA TajoClient should not connect TajoMaster at the first.

    I added a method to update TableStats at CatalogStore. For reference, all 
unit cases for physical operators verify output row numbers and it finished 
successfully with my patch. So, I didn't implement unit test cases. In 
addition, HCatalogStore::updateTableStats is dummy method. Because hive don't 
provide no api to update table row numbers.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/blrunner/tajo TAJO-1221

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/286.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #286
    
----
commit 9dc6cedce24a999c8f01fa701d4bc74e18642e28
Author: JaeHwa Jung <[email protected]>
Date:   2014-12-04T03:01:19Z

    TAJO-1221: HA TajoClient should not connect TajoMaster at the first.

----


> HA TajoClient should not connect TajoMaster at the first.
> ---------------------------------------------------------
>
>                 Key: TAJO-1221
>                 URL: https://issues.apache.org/jira/browse/TAJO-1221
>             Project: Tajo
>          Issue Type: Improvement
>          Components: tajo master
>            Reporter: Hyunsik Choi
>            Assignee: Jaehwa Jung
>              Labels: failure-handling, fault-tolerance, high-availability
>             Fix For: 0.9.1
>
>
> *Problem*
> We TajoClient is opened, TajoClient initially tries to connect TajoMaster. 
> This manner does not guarantee high availability. A known TajoMaster host may 
> be not work anymore. So, this manner still has some failure point.
> Also, this manner prohibits a Tajo cluster to run on some dynamic cluster 
> environments like Yarn.
> *Solution*
> Tajo HA client should get directly TajoMaster addresses and others from HA 
> component without contacting TajoMaster.



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

Reply via email to