You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/12/05 02:51:12 UTC

[jira] [Commented] (TAJO-1221) HA TajoClient should not connect TajoMaster at the first.

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

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

Github user blrunner closed the pull request at:

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


> 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)