Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4FC4B200BAB for ; Fri, 7 Oct 2016 20:24:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4E9BE160AC6; Fri, 7 Oct 2016 18:24:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B3E3A160AE9 for ; Fri, 7 Oct 2016 20:24:21 +0200 (CEST) Received: (qmail 89778 invoked by uid 500); 7 Oct 2016 18:24:20 -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 89488 invoked by uid 99); 7 Oct 2016 18:24:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Oct 2016 18:24:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 935FE2C2A67 for ; Fri, 7 Oct 2016 18:24:20 +0000 (UTC) Date: Fri, 7 Oct 2016 18:24:20 +0000 (UTC) From: "yunjiong zhao (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-16790) Need a better way to handler user's coprocessor error MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 07 Oct 2016 18:24:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yunjiong zhao updated HBASE-16790: ---------------------------------- Attachment: HBASE-16790.master.001.patch Seems we can disable table when load coprocessor throw exceptions. If the idea works, I can spend more time on this. > Need a better way to handler user's coprocessor error > ----------------------------------------------------- > > Key: HBASE-16790 > URL: https://issues.apache.org/jira/browse/HBASE-16790 > Project: HBase > Issue Type: Bug > Reporter: yunjiong zhao > Attachments: HBASE-16790.master.001.patch > > > User's bad coprocessor caused our hbase cluster down few times. > Now we are going to set hbase.coprocessor.abortonerror to false to avoid them bring down whole cluster accidentally. But this is not encourage in production since it will cause inconsistent. Do we have better ways to handle this situation? > Just few thoughts: > 1. Instead of shutdown RegionServer, can we just disable the table which have coprocessor error? > 2. Can we give some of user privilege to add coprocessor only? We can't just set hbase.coprocessor.user.enabled=false, that will cause lots of works to operation the cluster. > 3. Can we add another step, wait for supper user approve before hbase dynamically load the coprocessor? -- This message was sent by Atlassian JIRA (v6.3.4#6332)