[jira] [Commented] (HBASE-5715) Revert 'Instant schema alter' for now, HBASE-4213

["Subbu M Iyer (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246490#comment-13246490 ] 

Subbu M Iyer commented on HBASE-5715:
-------------------------------------

I reviewed the thread above and I do see mixed feeling about this. 

So, just wanted to clarify whether addressing the monitoring leaks (5702), introduce throttling to address rapid open/close region concerns (5713) and addressing the ambiguity in the flags that enables/disables this feature is even an option or not?

I can take up addressing the above two minor issues if that's an option. Also, since the default alter does not go through this path the impact to the common user should be none. 

Please note that what we have is based on loose set of requirements and I sincerely think that what is lacking is rock solid testing in a production kind-of environment and having cycles to address the issues if any. 



 
                
> Revert 'Instant schema alter' for now, HBASE-4213
> -------------------------------------------------
>
>                 Key: HBASE-5715
>                 URL: https://issues.apache.org/jira/browse/HBASE-5715
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>
> See this discussion: http://search-hadoop.com/m/NxCQh1KlSxR1/Pull+instant+schema+updating+out%253F&subj=Pull+instant+schema+updating+out+
> Pull out hbase-4213 for now.  Can add it back later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira