[jira] [Commented] (HBASE-5970) Improve the AssignmentManager#updateTimer and speed up handling opened event

[ https://issues.apache.org/jira/browse/HBASE-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294132#comment-13294132 ] ramkrishna.s.vasudevan commented on HBASE-5970: --- @Chunhui I think in trunk

[jira] [Commented] (HBASE-6204) Improvement for opening region on the regionserver

[ https://issues.apache.org/jira/browse/HBASE-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294133#comment-13294133 ] ramkrishna.s.vasudevan commented on HBASE-6204: --- @Chunhui See HBASE-5998.

[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=13294154#comment-13294154 ] ramkrishna.s.vasudevan commented on HBASE-6060: --- bq.Is this a fair

[jira] [Commented] (HBASE-5998) Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request

[ https://issues.apache.org/jira/browse/HBASE-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295448#comment-13295448 ] ramkrishna.s.vasudevan commented on HBASE-5998: --- @Stack We have a backport

[jira] [Updated] (HBASE-6196) MR testcases TestImportExport does not run in Trunk with hadoop2.0

[ https://issues.apache.org/jira/browse/HBASE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6196: -- Description: TEstImportExport test cases does not run in trunk when compiled

[jira] [Commented] (HBASE-6196) MR testcases TestImportExport does not run in Trunk with hadoop2.0

[ https://issues.apache.org/jira/browse/HBASE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295456#comment-13295456 ] ramkrishna.s.vasudevan commented on HBASE-6196: --- Update the title and

[jira] [Updated] (HBASE-5564) Bulkload is discarding duplicate records

[ https://issues.apache.org/jira/browse/HBASE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5564: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed

[jira] [Commented] (HBASE-6196) MR testcases TestImportExport does not run in Trunk with hadoop2.0

[ https://issues.apache.org/jira/browse/HBASE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295773#comment-13295773 ] ramkrishna.s.vasudevan commented on HBASE-6196: --- Can some one check this

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13393670#comment-13393670 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- @Chunhui Thanks for

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13395452#comment-13395452 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- @Chunhui In both SSH and

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13395791#comment-13395791 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- @Chunhui I got your issue

[jira] [Commented] (HBASE-6134) Improvement for split-worker to speed up distributed log splitting

[ https://issues.apache.org/jira/browse/HBASE-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13395981#comment-13395981 ] ramkrishna.s.vasudevan commented on HBASE-6134: --- @Chunhui You have patch for

[jira] [Updated] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6227: -- Status: Patch Available (was: Open) Submitting to QA SSH

[jira] [Updated] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6228: -- Status: Patch Available (was: Open) Submitting to HadoopQA.

[jira] [Commented] (HBASE-6232) HBase security commands should have a better error when used in insecure mode

[ https://issues.apache.org/jira/browse/HBASE-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13396066#comment-13396066 ] ramkrishna.s.vasudevan commented on HBASE-6232: --- @Stephen Once you submit a

[jira] [Commented] (HBASE-6134) Improvement for split-worker to speed up distributed log splitting

[ https://issues.apache.org/jira/browse/HBASE-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13396502#comment-13396502 ] ramkrishna.s.vasudevan commented on HBASE-6134: --- @Chunhui Thanks a lot. :)

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13396800#comment-13396800 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- @Chunhui I think this

[jira] [Commented] (HBASE-6229) AM.assign() should not set table state to ENABLED directly.

[ https://issues.apache.org/jira/browse/HBASE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397244#comment-13397244 ] ramkrishna.s.vasudevan commented on HBASE-6229: --- +1 Ted. Thanks for making

[jira] [Commented] (HBASE-4246) Cluster with too many regions cannot withstand some master failover scenarios

[ https://issues.apache.org/jira/browse/HBASE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397269#comment-13397269 ] ramkrishna.s.vasudevan commented on HBASE-4246: --- @Gao You got this in 0.90?

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397286#comment-13397286 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- @Chunhui So this happens

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397297#comment-13397297 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- So as i see the code if in

[jira] [Commented] (HBASE-5918) Master will block forever when startup if root server died between assign root and assign meta

[ https://issues.apache.org/jira/browse/HBASE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397512#comment-13397512 ] ramkrishna.s.vasudevan commented on HBASE-5918: --- This issue needs to be

[jira] [Updated] (HBASE-6164) Correct the bug in block encoding usage in bulkload

[ https://issues.apache.org/jira/browse/HBASE-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6164: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved

[jira] [Updated] (HBASE-5918) Master will block forever at startup if root server dies between assigning root and assigning meta

[ https://issues.apache.org/jira/browse/HBASE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5918: -- Attachment: HBASE-5918_0.94 Patch for 0.94. Master will

[jira] [Updated] (HBASE-5918) Master will block forever at startup if root server dies between assigning root and assigning meta

[ https://issues.apache.org/jira/browse/HBASE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5918: -- Resolution: Fixed Fix Version/s: 0.94.1 0.96.0

[jira] [Commented] (HBASE-5843) Improve HBase MTTR - Mean Time To Recover

[ https://issues.apache.org/jira/browse/HBASE-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397674#comment-13397674 ] ramkrishna.s.vasudevan commented on HBASE-5843: --- @N Just for update, I feel

[jira] [Created] (HBASE-6246) Admin.move() without specifying destination calls am.unassign() and does not go through AccessController.

ramkrishna.s.vasudevan created HBASE-6246: - Summary: Admin.move() without specifying destination calls am.unassign() and does not go through AccessController. Key: HBASE-6246 URL:

[jira] [Commented] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398481#comment-13398481 ] ramkrishna.s.vasudevan commented on HBASE-5875: --- @Devs {code} + // Make

[jira] [Commented] (HBASE-6253) isLegalTableName API should check for the _acl_ table name

[ https://issues.apache.org/jira/browse/HBASE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398649#comment-13398649 ] ramkrishna.s.vasudevan commented on HBASE-6253: --- @Ted {code} if

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

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398725#comment-13398725 ] ramkrishna.s.vasudevan commented on HBASE-6195: --- @Xing {code} //

[jira] [Commented] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398734#comment-13398734 ] ramkrishna.s.vasudevan commented on HBASE-5875: --- I will integrate this

[jira] [Updated] (HBASE-5206) Port HBASE-5155 to 0.92, 0.94, and TRUNK

[ https://issues.apache.org/jira/browse/HBASE-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5206: -- Fix Version/s: (was: 0.92.2) Port HBASE-5155 to 0.92, 0.94, and TRUNK

[jira] [Commented] (HBASE-6229) AM.assign() should not set table state to ENABLED directly.

[ https://issues.apache.org/jira/browse/HBASE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398741#comment-13398741 ] ramkrishna.s.vasudevan commented on HBASE-6229: --- @Ted This change is not

[jira] [Commented] (HBASE-5816) Balancer and ServerShutdownHandler concurrently reassign the same region

[ https://issues.apache.org/jira/browse/HBASE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399104#comment-13399104 ] ramkrishna.s.vasudevan commented on HBASE-5816: --- @Jimmy Yes, you are

[jira] [Updated] (HBASE-6246) Admin.move() without specifying destination calls am.unassign() and does not go through AccessController.

[ https://issues.apache.org/jira/browse/HBASE-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6246: -- Fix Version/s: 0.94.1 Admin.move() without specifying destination calls

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399273#comment-13399273 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- +1 on patch. This along

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399370#comment-13399370 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- @Chunhui Going thro the

[jira] [Commented] (HBASE-6246) Admin.move without specifying destination does not go through AccessController

[ https://issues.apache.org/jira/browse/HBASE-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399894#comment-13399894 ] ramkrishna.s.vasudevan commented on HBASE-6246: --- @Ted, @Andy and @Stack

[jira] [Updated] (HBASE-6240) Race in HCM.getMaster stalls clients

[ https://issues.apache.org/jira/browse/HBASE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6240: -- Attachment: HBASE-6240_1_0.94.patch Pls check the latest patch. With JD's

[jira] [Commented] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400284#comment-13400284 ] ramkrishna.s.vasudevan commented on HBASE-5875: ---

[jira] [Commented] (HBASE-6253) Dont allow user to disable/drop _acl_ table

[ https://issues.apache.org/jira/browse/HBASE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400297#comment-13400297 ] ramkrishna.s.vasudevan commented on HBASE-6253: --- I think its better we fix

[jira] [Commented] (HBASE-5360) [uberhbck] Add options for how to handle offline split parents.

[ https://issues.apache.org/jira/browse/HBASE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400381#comment-13400381 ] ramkrishna.s.vasudevan commented on HBASE-5360: --- Small nit {code}

[jira] [Updated] (HBASE-5630) hbck should disable the balancer using synchronousBalanceSwitch.

[ https://issues.apache.org/jira/browse/HBASE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5630: -- Resolution: Fixed Status: Resolved (was: Patch Available) hbck

[jira] [Commented] (HBASE-6240) Race in HCM.getMaster stalls clients

[ https://issues.apache.org/jira/browse/HBASE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400715#comment-13400715 ] ramkrishna.s.vasudevan commented on HBASE-6240: --- bq.Did you see how we get

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400723#comment-13400723 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- I am planning to commit

[jira] [Updated] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5875: -- Attachment: HBASE-5875_0.94_2.patch PAtch for 0.94 ready for commit.

[jira] [Updated] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5875: -- Attachment: HBASE-5875_trunk_1.patch Patch for trunk, ready for commit.

[jira] [Updated] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5875: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed

[jira] [Updated] (HBASE-5875) Process RIT and Master restart may remove an online server considering it as a dead server

[ https://issues.apache.org/jira/browse/HBASE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-5875: -- Fix Version/s: 0.96.0 Process RIT and Master restart may remove an online

[jira] [Commented] (HBASE-6268) Can't enable a table on a 0.94 cluster from a 0.92 client

[ https://issues.apache.org/jira/browse/HBASE-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401156#comment-13401156 ] ramkrishna.s.vasudevan commented on HBASE-6268: ---

[jira] [Commented] (HBASE-5904) is_enabled from shell returns differently from pre- and post- HBASE-5155

[ https://issues.apache.org/jira/browse/HBASE-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401173#comment-13401173 ] ramkrishna.s.vasudevan commented on HBASE-5904: --- +1. @Stack bq.Let us know

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401243#comment-13401243 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- +1 Chunhui. Your

[jira] [Commented] (HBASE-6205) Support an option to keep data of dropped table for some time

[ https://issues.apache.org/jira/browse/HBASE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401245#comment-13401245 ] ramkrishna.s.vasudevan commented on HBASE-6205: --- bq.if we set table

[jira] [Commented] (HBASE-6269) Lazyseek should use the maxSequenseId StoreFile's KeyValue as the latest KeyValue

[ https://issues.apache.org/jira/browse/HBASE-6269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401296#comment-13401296 ] ramkrishna.s.vasudevan commented on HBASE-6269: --- @ShiXing If the data is not

[jira] [Commented] (HBASE-6269) Lazyseek should use the maxSequenseId StoreFile's KeyValue as the latest KeyValue

[ https://issues.apache.org/jira/browse/HBASE-6269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401325#comment-13401325 ] ramkrishna.s.vasudevan commented on HBASE-6269: --- @ShiXing Yes, I agree that

[jira] [Updated] (HBASE-6269) Lazyseek should use the maxSequenseId StoreFile's KeyValue as the latest KeyValue

[ https://issues.apache.org/jira/browse/HBASE-6269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6269: -- Status: Patch Available (was: Open) Lazyseek should use the

[jira] [Resolved] (HBASE-6240) Race in HCM.getMaster stalls clients

[ https://issues.apache.org/jira/browse/HBASE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan resolved HBASE-6240. --- Resolution: Fixed Assignee: ramkrishna.s.vasudevan Hadoop

[jira] [Created] (HBASE-6273) HMasterInterface.isMasterRunning() requires clean up

ramkrishna.s.vasudevan created HBASE-6273: - Summary: HMasterInterface.isMasterRunning() requires clean up Key: HBASE-6273 URL: https://issues.apache.org/jira/browse/HBASE-6273 Project: HBase

[jira] [Commented] (HBASE-6240) Race in HCM.getMaster stalls clients

[ https://issues.apache.org/jira/browse/HBASE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401534#comment-13401534 ] ramkrishna.s.vasudevan commented on HBASE-6240: --- HBASE-6273 raised.

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401539#comment-13401539 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- @Jon So you not ok with

[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=13401542#comment-13401542 ] ramkrishna.s.vasudevan commented on HBASE-6060: --- @Stack So for the latest

[jira] [Resolved] (HBASE-6200) KeyComparator.compareWithoutRow can be wrong when families have the same prefix

[ https://issues.apache.org/jira/browse/HBASE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan resolved HBASE-6200. --- Resolution: Fixed Hadoop Flags: Reviewed Resolving as committed to all

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402091#comment-13402091 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- @Chunhui Thanks for the

[jira] [Updated] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6228: -- Attachment: HBASE-6228v4.patch Fixup daughters twice cause daughter

[jira] [Updated] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6228: -- Status: Patch Available (was: Open) Fixup daughters twice cause

[jira] [Updated] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6228: -- Status: Open (was: Patch Available) Fixup daughters twice cause

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402145#comment-13402145 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- @Jon I have added a

[jira] [Assigned] (HBASE-6273) HMasterInterface.isMasterRunning() requires clean up

[ https://issues.apache.org/jira/browse/HBASE-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-6273: - Assignee: ramkrishna.s.vasudevan HMasterInterface.isMasterRunning()

[jira] [Commented] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402336#comment-13402336 ] ramkrishna.s.vasudevan commented on HBASE-6227: --- Planning to commit this

[jira] [Updated] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6227: -- Fix Version/s: 0.94.1 0.96.0 SSH and cluster startup

[jira] [Updated] (HBASE-6227) SSH and cluster startup causes data loss

[ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6227: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved

[jira] [Commented] (HBASE-6269) Lazyseek should use the maxSequenseId StoreFile's KeyValue as the latest KeyValue

[ https://issues.apache.org/jira/browse/HBASE-6269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402833#comment-13402833 ] ramkrishna.s.vasudevan commented on HBASE-6269: --- @Ted For 0.94? We need to

[jira] [Commented] (HBASE-6289) ROOT region doesn't get re-assigned in ServerShutdownHandler if the RS is still working but only the RS's ZK node expires.

[ https://issues.apache.org/jira/browse/HBASE-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403085#comment-13403085 ] ramkrishna.s.vasudevan commented on HBASE-6289: --- @Maryann Good one Maraynn.

[jira] [Comment Edited] (HBASE-6289) ROOT region doesn't get re-assigned in ServerShutdownHandler if the RS is still working but only the RS's ZK node expires.

[ https://issues.apache.org/jira/browse/HBASE-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403085#comment-13403085 ] ramkrishna.s.vasudevan edited comment on HBASE-6289 at 6/28/12 1:24 PM:

[jira] [Assigned] (HBASE-6197) HRegion's append operation may lose data

[ https://issues.apache.org/jira/browse/HBASE-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-6197: - Assignee: ShiXing (was: ramkrishna.s.vasudevan) Incorrectly assigned

[jira] [Assigned] (HBASE-6197) HRegion's append operation may lose data

[ https://issues.apache.org/jira/browse/HBASE-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-6197: - Assignee: ramkrishna.s.vasudevan (was: ShiXing) HRegion's append

[jira] [Assigned] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-6210: - Assignee: ramkrishna.s.vasudevan Backport HBASE-6197 to 0.94 and

[jira] [Updated] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6210: -- Attachment: HBASE-6210.patch Patch for 0.94. Backport

[jira] [Commented] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403218#comment-13403218 ] ramkrishna.s.vasudevan commented on HBASE-6210: --- Yes Stack

[jira] [Updated] (HBASE-6284) Introduce HRegion#doMiniBatchDelete()

[ https://issues.apache.org/jira/browse/HBASE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6284: -- Fix Version/s: 0.94.1 0.96.0 Introduce

[jira] [Commented] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403242#comment-13403242 ] ramkrishna.s.vasudevan commented on HBASE-6210: --- Append i could not find in

[jira] [Commented] (HBASE-6287) Port HBASE-5941 improve multiDelete performance by grabbing locks ahead of time

[ https://issues.apache.org/jira/browse/HBASE-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403246#comment-13403246 ] ramkrishna.s.vasudevan commented on HBASE-6287: --- @Andy HBASE-6284 does what

[jira] [Commented] (HBASE-6289) ROOT region doesn't get re-assigned in ServerShutdownHandler if the RS is still working but only the RS's ZK node expires.

[ https://issues.apache.org/jira/browse/HBASE-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403256#comment-13403256 ] ramkrishna.s.vasudevan commented on HBASE-6289: --- @Stack Any specific reason

[jira] [Commented] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403264#comment-13403264 ] ramkrishna.s.vasudevan commented on HBASE-6210: --- I will commit the current

[jira] [Commented] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92?

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403292#comment-13403292 ] ramkrishna.s.vasudevan commented on HBASE-6210: --- Committed to 0.94

[jira] [Commented] (HBASE-6289) ROOT region doesn't get re-assigned in ServerShutdownHandler if the RS is still working but only the RS's ZK node expires.

[ https://issues.apache.org/jira/browse/HBASE-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403686#comment-13403686 ] ramkrishna.s.vasudevan commented on HBASE-6289: --- @Stack I was asking why

[jira] [Assigned] (HBASE-6117) Revisit default condition added to Switch cases in Trunk

[ https://issues.apache.org/jira/browse/HBASE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-6117: - Assignee: ramkrishna.s.vasudevan (was: Ashutosh Jindal) Revisit

[jira] [Updated] (HBASE-6117) Revisit default condition added to Switch cases in Trunk

[ https://issues.apache.org/jira/browse/HBASE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6117: -- Status: Patch Available (was: Open) Revisit default condition added to

[jira] [Updated] (HBASE-6117) Revisit default condition added to Switch cases in Trunk

[ https://issues.apache.org/jira/browse/HBASE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6117: -- Attachment: HBASE-6117.patch Revisit default condition added to Switch

[jira] [Commented] (HBASE-6117) Revisit default condition added to Switch cases in Trunk

[ https://issues.apache.org/jira/browse/HBASE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403835#comment-13403835 ] ramkrishna.s.vasudevan commented on HBASE-6117: --- Patch for trunk.

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

[ https://issues.apache.org/jira/browse/HBASE-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan resolved HBASE-6195. --- Resolution: Fixed Resolving as HBASE-6269 got committed.

[jira] [Updated] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6210: -- Fix Version/s: 0.92.2 Summary: Backport HBASE-6197 to 0.94 and 0.92

[jira] [Updated] (HBASE-6210) Backport HBASE-6197 to 0.94 and 0.92

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6210: -- Attachment: HBASE-6210_0.92.patch Patch for 0.92. Pls review. If it is ok I

[jira] [Commented] (HBASE-6228) Fixup daughters twice cause daughter region assigned twice

[ https://issues.apache.org/jira/browse/HBASE-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403908#comment-13403908 ] ramkrishna.s.vasudevan commented on HBASE-6228: --- @Chunhui We are able to

[jira] [Updated] (HBASE-6210) Backport HBASE-6197 to 0.94

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6210: -- Fix Version/s: (was: 0.92.2) Summary: Backport HBASE-6197 to 0.94

[jira] [Created] (HBASE-6297) Backport HBASE-6195 to 0.92

ramkrishna.s.vasudevan created HBASE-6297: - Summary: Backport HBASE-6195 to 0.92 Key: HBASE-6297 URL: https://issues.apache.org/jira/browse/HBASE-6297 Project: HBase Issue Type: Bug

[jira] [Updated] (HBASE-6297) Backport HBASE-6195 to 0.92

[ https://issues.apache.org/jira/browse/HBASE-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6297: -- Attachment: HBASE-6297_0.92.patch Patch for 0.92. Backport

[jira] [Commented] (HBASE-6298) Region balancer not balancing

[ https://issues.apache.org/jira/browse/HBASE-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13404890#comment-13404890 ] ramkrishna.s.vasudevan commented on HBASE-6298: --- @Dave/Stack As Rajesh

[jira] [Commented] (HBASE-6210) Backport HBASE-6197 to 0.94

[ https://issues.apache.org/jira/browse/HBASE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405011#comment-13405011 ] ramkrishna.s.vasudevan commented on HBASE-6210: --- HBASE-6297 raised for

[jira] [Commented] (HBASE-5360) [uberhbck] Add options for how to handle offline split parents.

[ https://issues.apache.org/jira/browse/HBASE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405074#comment-13405074 ] ramkrishna.s.vasudevan commented on HBASE-5360: --- @Jimmy I have a question

<    1   2   3   4   5   6   7   8   9   10   >