[
https://issues.apache.org/jira/browse/TAJO-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keuntae Park updated TAJO-274:
------------------------------
Attachment: TAJO-274.patch_2
Thank you for the review, Jihoon.
(Sorry for the late reply)
I've uploaded the new patch for the issue.
- Actually, connectToTajoMaster() method is no longer needed because of new
reconnecting logic, hence, remove it.
- set default controller and add exception handling in async rpc.
- rebase
> Maintaining connectivity to Tajo master even though the restart of the Tajo
> master
> ----------------------------------------------------------------------------------
>
> Key: TAJO-274
> URL: https://issues.apache.org/jira/browse/TAJO-274
> Project: Tajo
> Issue Type: Improvement
> Reporter: Keuntae Park
> Attachments: TAJO-274.patch, TAJO-274.patch_2
>
>
> Currently, when you restart the Tajo master, you should restart all the
> workers and clients also.
> When client or worker has problem with connection to Tajo master due to the
> master restart, it needs to close the previous connection and try to
> reconnect to the master
--
This message was sent by Atlassian JIRA
(v6.1#6144)
