hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yunjiong zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16790) Need a better way to handler user's coprocessor error
Date Fri, 07 Oct 2016 18:24:20 GMT

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

View raw message