Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E019C9C15 for ; Tue, 21 May 2013 22:26:20 +0000 (UTC) Received: (qmail 94287 invoked by uid 500); 21 May 2013 22:26:21 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 94233 invoked by uid 500); 21 May 2013 22:26:21 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 94224 invoked by uid 99); 21 May 2013 22:26:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 22:26:21 +0000 Date: Tue, 21 May 2013 22:26:21 +0000 (UTC) From: "Jimmy Xiang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8585) AssignmentManager should handle RejectedExecutionException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663490#comment-13663490 ] Jimmy Xiang commented on HBASE-8585: ------------------------------------ In this case, I think we should put the event in the waiting list again. We need to make sure it is in the original position. The other choice is to remove the event from the list only after it is submitted properly at first. What do you say? > AssignmentManager should handle RejectedExecutionException > ---------------------------------------------------------- > > Key: HBASE-8585 > URL: https://issues.apache.org/jira/browse/HBASE-8585 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > > In test output, I noticed the following: > {code} > 2013-05-21 03:39:37,015 DEBUG [Thread-1446-EventThread] zookeeper.ZooKeeperWatcher(307): master:35255-0x13ec52b4ce30000 Received ZooKeeper Event, type=NodeDataChanged, state=SyncConnected, path=/hbase/region-in-transition/8b6ce00aafd483a6ed7a76425009ebf8 > 2013-05-21 03:39:37,015 ERROR [Thread-1446-EventThread] zookeeper.ClientCnxn$EventThread(521): Error while calling watcher > java.util.concurrent.RejectedExecutionException > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658) > at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:78) > at org.apache.hadoop.hbase.master.AssignmentManager.zkEventWorkersSubmit(AssignmentManager.java:1136) > at org.apache.hadoop.hbase.master.AssignmentManager.handleAssignmentEvent(AssignmentManager.java:1306) > at org.apache.hadoop.hbase.master.AssignmentManager.nodeDataChanged(AssignmentManager.java:1095) > at org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:338) > at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519) > at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495) > {code} > By default, ThreadPoolExecutor.AbortPolicy is used for zkEventWorkers, leading to the above exception. > We should examine the calls to zkEventWorkersSubmit() and devise proper handling for RejectedExecutionException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira