[
https://issues.apache.org/jira/browse/HBASE-16790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-16790.
-----------------------------------------
Resolution: Incomplete
> 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
> Priority: Major
> 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
(v8.20.7#820007)
