Return-Path: X-Original-To: apmail-tajo-dev-archive@minotaur.apache.org Delivered-To: apmail-tajo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 542FC1012A for ; Fri, 25 Oct 2013 02:42:39 +0000 (UTC) Received: (qmail 78079 invoked by uid 500); 25 Oct 2013 02:42:32 -0000 Delivered-To: apmail-tajo-dev-archive@tajo.apache.org Received: (qmail 77951 invoked by uid 500); 25 Oct 2013 02:42:29 -0000 Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.incubator.apache.org Delivered-To: mailing list dev@tajo.incubator.apache.org Received: (qmail 77931 invoked by uid 99); 25 Oct 2013 02:42:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 02:42:28 +0000 X-ASF-Spam-Status: No, hits=-2000.4 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 25 Oct 2013 02:42:25 +0000 Received: (qmail 77331 invoked by uid 99); 25 Oct 2013 02:42:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 02:42:03 +0000 Date: Fri, 25 Oct 2013 02:42:03 +0000 (UTC) From: "Jihoon Son (JIRA)" To: dev@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (TAJO-274) Maintaining connectivity to Tajo master even though the restart of the Tajo master MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/TAJO-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804951#comment-13804951 ] Jihoon Son edited comment on TAJO-274 at 10/25/13 2:41 AM: ----------------------------------------------------------- Thanks for your contribution, but this patch includes some strange codes like this. {code} In TajoWorker private void connectToTajoMaster(String tajoMasterAddrString) { LOG.info("Connecting to TajoMaster (" + tajoMasterAddrString +")"); this.tajoMasterAddress = NetUtils.createSocketAddr(tajoMasterAddrString); while(true) { try { // tajoMasterRpc = new AsyncRpcClient(TajoMasterProtocol.class, this.tajoMasterAddress); // tajoMasterRpcClient = tajoMasterRpc.getStub(); break; } catch (Exception e) { LOG.error("Can't connect to TajoMaster[" + NetUtils.normalizeInetSocketAddress(tajoMasterAddress) + "], " + e.getMessage(), e); } try { Thread.sleep(3000); } catch (InterruptedException e) { } } } {code} was (Author: jihoonson): Thanks for your contribution, but this patch some strange codes like this. {code} In TajoWorker private void connectToTajoMaster(String tajoMasterAddrString) { LOG.info("Connecting to TajoMaster (" + tajoMasterAddrString +")"); this.tajoMasterAddress = NetUtils.createSocketAddr(tajoMasterAddrString); while(true) { try { // tajoMasterRpc = new AsyncRpcClient(TajoMasterProtocol.class, this.tajoMasterAddress); // tajoMasterRpcClient = tajoMasterRpc.getStub(); break; } catch (Exception e) { LOG.error("Can't connect to TajoMaster[" + NetUtils.normalizeInetSocketAddress(tajoMasterAddress) + "], " + e.getMessage(), e); } try { Thread.sleep(3000); } catch (InterruptedException e) { } } } {code} > 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 > > > 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)