[jira] [Updated] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rajeshbabu updated HBASE-6060: -- Attachment: 6060_suggestion_toassign_rs_wentdown_beforerequest.patch Regions's in OPENING state

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292474#comment-13292474 ] rajeshbabu commented on HBASE-6060: --- @Ram Attached patch. Just a suggestion to skip the

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292475#comment-13292475 ] stack commented on HBASE-6060: -- bq. But the gain with bulk assignment is its faster which we

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292476#comment-13292476 ] stack commented on HBASE-6060: -- @rajeshbabu So, you are allowing the single-assign to

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292479#comment-13292479 ] Hadoop QA commented on HBASE-6060: -- -1 overall. Here are the results of testing the

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292530#comment-13292530 ] Zhihong Ted Yu commented on HBASE-6060: --- For

[jira] [Updated] (HBASE-4791) Allow Secure Zookeeper JAAS configuration to be programmatically set (rather than only by reading JAAS configuration file)

[ https://issues.apache.org/jira/browse/HBASE-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi updated HBASE-4791: --- Attachment: HBASE-4791-v0.patch I've attached a first draft patch that allows Master, Region

[jira] [Updated] (HBASE-4368) Expose processlist in shell (per regionserver and perhaps by cluster)

[ https://issues.apache.org/jira/browse/HBASE-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shahin Saneinejad updated HBASE-4368: - Attachment: HBASE-4368.patch Attached a patch, I'd appreciate any feedback. I'm

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292549#comment-13292549 ] ramkrishna.s.vasudevan commented on HBASE-6060: --- @Ted Myself or Rajesh,

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292589#comment-13292589 ] stack commented on HBASE-6060: -- Rajesh says: bq. Lets suppose Region server went down after

[jira] [Created] (HBASE-6195) Increment data will lost when the memstore flushed

Xing Shi created HBASE-6195: --- Summary: Increment data will lost when the memstore flushed Key: HBASE-6195 URL: https://issues.apache.org/jira/browse/HBASE-6195 Project: HBase Issue Type: Bug

[jira] [Commented] (HBASE-6195) Increment data will lost when the memstore flushed

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292625#comment-13292625 ] Xing Shi commented on HBASE-6195: - Here is the data: I delete the row first, and then use

[jira] [Commented] (HBASE-6195) Increment data will lost when the memstore flushed

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292626#comment-13292626 ] Xing Shi commented on HBASE-6195: - Oh sorry, there is no delete in my test case.

[jira] [Updated] (HBASE-6195) Increment data will lost when the memstore flushed

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Shi updated HBASE-6195: Attachment: HBASE-6195-trunk.patch The patch. Increment data will lost when the memstore

[jira] [Updated] (HBASE-6195) Increment data will lost when the memstore flushed

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Shi updated HBASE-6195: Attachment: HBASE-6195-trunk-V2.patch The previous patch didn't mv the now variable into the lock, fix it.

[jira] [Commented] (HBASE-6060) Regions's in OPENING state from failed regionservers takes a long time to recover

[ https://issues.apache.org/jira/browse/HBASE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292646#comment-13292646 ] ramkrishna.s.vasudevan commented on HBASE-6060: --- @Stack Few comments, First