[jira] [Updated] (HBASE-6055) Snapshots in HBase 0.96

[ https://issues.apache.org/jira/browse/HBASE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated HBASE-6055: --- Attachment: (was: Snapshots in HBase.docx) > Snapshots in HBase 0.96 > --

[jira] [Updated] (HBASE-6055) Snapshots in HBase 0.96

[ https://issues.apache.org/jira/browse/HBASE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated HBASE-6055: --- Attachment: Snapshots in HBase.docx Adding updated documentation - realized it fudged a couple things

[jira] [Commented] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281408#comment-13281408 ] chunhui shen commented on HBASE-6065: - @ram I think both ok. Since current patchV2 co

[jira] [Commented] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281406#comment-13281406 ] ramkrishna.s.vasudevan commented on HBASE-6065: --- @Chunhui Again thinking on

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281402#comment-13281402 ] Hudson commented on HBASE-6047: --- Integrated in HBase-0.94 #209 (See [https://builds.apache.

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281399#comment-13281399 ] Hudson commented on HBASE-6047: --- Integrated in HBase-TRUNK #2915 (See [https://builds.apach

[jira] [Commented] (HBASE-6068) Secure HBase cluster : Client not able to call some admin APIs

[ https://issues.apache.org/jira/browse/HBASE-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281397#comment-13281397 ] Anoop Sam John commented on HBASE-6068: --- HBaseAdmin isTableEnabled() isTableEnabled(

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281396#comment-13281396 ] Hadoop QA commented on HBASE-6059: -- -1 overall. Here are the results of testing the late

[jira] [Created] (HBASE-6068) Secure HBase cluster : Client not able to call some admin APIs

Anoop Sam John created HBASE-6068: - Summary: Secure HBase cluster : Client not able to call some admin APIs Key: HBASE-6068 URL: https://issues.apache.org/jira/browse/HBASE-6068 Project: HBase

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281394#comment-13281394 ] Hudson commented on HBASE-6047: --- Integrated in HBase-0.92 #417 (See [https://builds.apache.

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281392#comment-13281392 ] Hudson commented on HBASE-6047: --- Integrated in HBase-0.94-security #29 (See [https://builds

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281387#comment-13281387 ] Zhihong Yu commented on HBASE-6047: --- Integrated to 0.92, 0.94 and trunk. Thanks for the

[jira] [Updated] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunhui shen updated HBASE-6059: Attachment: HBASE-6059v4.patch Patch v4 modified TestStore#testDeleteExpiredStoreFiles since we cou

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281379#comment-13281379 ] Zhihong Yu commented on HBASE-6059: --- I think test case should be modified.

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281377#comment-13281377 ] chunhui shen commented on HBASE-6059: - @ram Sorry, we don't have the test environment

[jira] [Updated] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-6047: -- Attachment: 6047-92.txt Patch for 0.92 branch > Put.has() can't determine result corre

[jira] [Updated] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-6047: -- Status: Open (was: Patch Available) > Put.has() can't determine result correctly > ---

[jira] [Commented] (HBASE-5916) RS restart just before master intialization we make the cluster non operative

[ https://issues.apache.org/jira/browse/HBASE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281357#comment-13281357 ] chunhui shen commented on HBASE-5916: - I have a doubt about patchV5 {code} +Set ac

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281317#comment-13281317 ] Hadoop QA commented on HBASE-6047: -- -1 overall. Here are the results of testing the late

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281305#comment-13281305 ] Zhihong Yu commented on HBASE-6047: --- The 3 test failures were not due to this change.

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281302#comment-13281302 ] Hadoop QA commented on HBASE-6047: -- -1 overall. Here are the results of testing the late

[jira] [Commented] (HBASE-6044) copytable: remove rs.* parameters

[ https://issues.apache.org/jira/browse/HBASE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281287#comment-13281287 ] Hudson commented on HBASE-6044: --- Integrated in HBase-0.94-security #28 (See [https://builds

[jira] [Commented] (HBASE-5757) TableInputFormat should handle as many errors as possible

[ https://issues.apache.org/jira/browse/HBASE-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281288#comment-13281288 ] Hudson commented on HBASE-5757: --- Integrated in HBase-0.94-security #28 (See [https://builds

[jira] [Commented] (HBASE-5840) Open Region FAILED_OPEN doesn't clear the TaskMonitor Status, keeps showing the old status

[ https://issues.apache.org/jira/browse/HBASE-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281289#comment-13281289 ] Hudson commented on HBASE-5840: --- Integrated in HBase-0.94-security #28 (See [https://builds

[jira] [Commented] (HBASE-6061) Fix ACL "Admin" Table inconsistent permission check

[ https://issues.apache.org/jira/browse/HBASE-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281290#comment-13281290 ] Hudson commented on HBASE-6061: --- Integrated in HBase-0.94-security #28 (See [https://builds

[jira] [Commented] (HBASE-6056) Restore hbase-default version check

[ https://issues.apache.org/jira/browse/HBASE-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281291#comment-13281291 ] Hudson commented on HBASE-6056: --- Integrated in HBase-0.94-security #28 (See [https://builds

[jira] [Commented] (HBASE-6067) HBase won't start when hbase.rootdir uses ViewFileSystem

[ https://issues.apache.org/jira/browse/HBASE-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281276#comment-13281276 ] Eli Collins commented on HBASE-6067: Here's the exception btw when configuring hbase.r

[jira] [Created] (HBASE-6067) HBase won't start when hbase.rootdir uses ViewFileSystem

Eli Collins created HBASE-6067: -- Summary: HBase won't start when hbase.rootdir uses ViewFileSystem Key: HBASE-6067 URL: https://issues.apache.org/jira/browse/HBASE-6067 Project: HBase Issue Type

[jira] [Updated] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-6047: -- Fix Version/s: 0.94.1 0.96.0 0.92.2 Hadoop Flags: Reviewed

[jira] [Commented] (HBASE-2110) Move to ivy broke our finding stylesheet (Tables don't have blue lines around them any more).

[ https://issues.apache.org/jira/browse/HBASE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281271#comment-13281271 ] Alex Newman commented on HBASE-2110: Can we close this? > Move to ivy

[jira] [Commented] (HBASE-1801) Tool to clean regions on DFS

[ https://issues.apache.org/jira/browse/HBASE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281267#comment-13281267 ] Alex Newman commented on HBASE-1801: Is this jira still relevant? Hbck fixes this no?

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281266#comment-13281266 ] Zhihong Yu commented on HBASE-6047: --- Thanks for the quick turnaround. +1 on patch v2.

[jira] [Updated] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman updated HBASE-6047: --- Attachment: 0001-HBASE-6047.-Put.has-can-t-determine-result-correctly-v2.patch > Put.has() can't

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281260#comment-13281260 ] Alex Newman commented on HBASE-6047: think i got your comments > Put.

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281255#comment-13281255 ] Zhihong Yu commented on HBASE-6047: --- Please add license to TestPutHas.java {code} +@Cate

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281252#comment-13281252 ] Alex Newman commented on HBASE-6047: Ooh I think I fixed it as well :)

[jira] [Updated] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman updated HBASE-6047: --- Attachment: 0001-HBASE-6047.-Put.has-can-t-determine-result-correctly.patch > Put.has() can't det

[jira] [Updated] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman updated HBASE-6047: --- Status: Patch Available (was: Open) > Put.has() can't determine result correctly > -

[jira] [Commented] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281251#comment-13281251 ] Alex Newman commented on HBASE-6047: I added a bunch of tests. The getvalue stuff didn

[jira] [Commented] (HBASE-5978) Scanner next() calls should return after a configurable time threshold regardless of number of accumulated rows

[ https://issues.apache.org/jira/browse/HBASE-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281253#comment-13281253 ] Elliott Clark commented on HBASE-5978: -- This has come up twice today. It should also

[jira] [Assigned] (HBASE-6047) Put.has() can't determine result correctly

[ https://issues.apache.org/jira/browse/HBASE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman reassigned HBASE-6047: -- Assignee: Alex Newman > Put.has() can't determine result correctly > --

[jira] [Commented] (HBASE-6043) Add Increment Coalescing in thrift.

[ https://issues.apache.org/jira/browse/HBASE-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281250#comment-13281250 ] Hadoop QA commented on HBASE-6043: -- -1 overall. Here are the results of testing the late

[jira] [Commented] (HBASE-5969) HRI.getRegionName/AsString are inconsistent for regions with the old encoding scheme

[ https://issues.apache.org/jira/browse/HBASE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281230#comment-13281230 ] Alex Newman commented on HBASE-5969: Does it make sense to focus on just fixing getReg

[jira] [Assigned] (HBASE-5969) HRI.getRegionName/AsString are inconsistent for regions with the old encoding scheme

[ https://issues.apache.org/jira/browse/HBASE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman reassigned HBASE-5969: -- Assignee: Alex Newman > HRI.getRegionName/AsString are inconsistent for regions with the ol

[jira] [Commented] (HBASE-5978) Scanner next() calls should return after a configurable time threshold regardless of number of accumulated rows

[ https://issues.apache.org/jira/browse/HBASE-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281227#comment-13281227 ] Alex Newman commented on HBASE-5978: Do we already have some choosen favorite way to c

[jira] [Commented] (HBASE-5978) Scanner next() calls should return after a configurable time threshold regardless of number of accumulated rows

[ https://issues.apache.org/jira/browse/HBASE-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281228#comment-13281228 ] Alex Newman commented on HBASE-5978: I assume you want this to return before any excep

[jira] [Updated] (HBASE-6043) Add Increment Coalescing in thrift.

[ https://issues.apache.org/jira/browse/HBASE-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-6043: - Attachment: HBASE-6043-3.patch updating to keep up with phabricator. > Add Incre

[jira] [Assigned] (HBASE-2750) Add sanity check for system configs in hbase-daemon wrapper

[ https://issues.apache.org/jira/browse/HBASE-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman reassigned HBASE-2750: -- Assignee: (was: Alex Newman) > Add sanity check for system configs in hbase-daemon wrap

[jira] [Assigned] (HBASE-2739) Master should fail to start if it cannot successfully split logs

[ https://issues.apache.org/jira/browse/HBASE-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman reassigned HBASE-2739: -- Assignee: (was: Alex Newman) > Master should fail to start if it cannot successfully sp

[jira] [Assigned] (HBASE-4587) HBase MR support for multiple tables as input

[ https://issues.apache.org/jira/browse/HBASE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman reassigned HBASE-4587: -- Assignee: (was: Alex Newman) > HBase MR support for multiple tables as input >

[jira] [Assigned] (HBASE-5534) HBase shell's return value is almost always 0

[ https://issues.apache.org/jira/browse/HBASE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Newman reassigned HBASE-5534: -- Assignee: (was: Alex Newman) > HBase shell's return value is almost always 0 >

[jira] [Updated] (HBASE-6041) NullPointerException prevents the master from starting up

[ https://issues.apache.org/jira/browse/HBASE-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-6041: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) This

[jira] [Updated] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Yu updated HBASE-6065: -- Fix Version/s: 0.94.1 0.96.0 Hadoop Flags: Reviewed > Log for flush would a

[jira] [Commented] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281090#comment-13281090 ] Zhihong Yu commented on HBASE-6065: --- I ran TestAtomicOperation 3 times on MacBook and th

[jira] [Commented] (HBASE-1697) Discretionary access control

[ https://issues.apache.org/jira/browse/HBASE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280904#comment-13280904 ] Laxman commented on HBASE-1697: --- Able to find the issue. In client machines we didn't replac

[jira] [Commented] (HBASE-1697) Discretionary access control

[ https://issues.apache.org/jira/browse/HBASE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280832#comment-13280832 ] Laxman commented on HBASE-1697: --- Thanks for the info Andrew. I'm discussing this issue with

[jira] [Updated] (HBASE-5927) SSH and DisableTableHandler happening together does not clear the znode of the region and RIT map.

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

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280825#comment-13280825 ] ramkrishna.s.vasudevan commented on HBASE-6059: --- @Chunhui Can you run the en

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280823#comment-13280823 ] Hadoop QA commented on HBASE-6059: -- -1 overall. Here are the results of testing the late

[jira] [Commented] (HBASE-5974) Scanner retry behavior with RPC timeout on next() seems incorrect

[ https://issues.apache.org/jira/browse/HBASE-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280815#comment-13280815 ] Anoop Sam John commented on HBASE-5974: --- @Todd {quote} this isn't currently compatib

[jira] [Updated] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunhui shen updated HBASE-6059: Attachment: HBASE-6059v3.patch Patch v3 with Ted's comment, And I run the TestColumnSeeking, it pa

[jira] [Commented] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280788#comment-13280788 ] chunhui shen commented on HBASE-6065: - bq.updateRegionMaximumEditLogSeqNum() is called

[jira] [Commented] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280787#comment-13280787 ] Hadoop QA commented on HBASE-6065: -- -1 overall. Here are the results of testing the late

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280785#comment-13280785 ] Hadoop QA commented on HBASE-6059: -- -1 overall. Here are the results of testing the late

[jira] [Commented] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280783#comment-13280783 ] Zhihong Yu commented on HBASE-6065: --- updateRegionMaximumEditLogSeqNum() is called by two

[jira] [Commented] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280781#comment-13280781 ] Zhihong Yu commented on HBASE-6059: --- Nice work. Minor comments: {code} -// Get minim

[jira] [Assigned] (HBASE-6066) some low hanging read path improvement ideas

[ https://issues.apache.org/jira/browse/HBASE-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reassigned HBASE-6066: -- Assignee: (was: Todd Lipcon) oops, did not mean to click "assign to me" :) But I noticed se

[jira] [Updated] (HBASE-6066) some low hanging read path improvement ideas

[ https://issues.apache.org/jira/browse/HBASE-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HBASE-6066: --- Attachment: metric-stringbuilder-fix.patch This patch improved CPU pretty noticeably for my tests. I

[jira] [Assigned] (HBASE-6066) some low hanging read path improvement ideas

[ https://issues.apache.org/jira/browse/HBASE-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reassigned HBASE-6066: -- Assignee: Todd Lipcon > some low hanging read path improvement ideas > ---

[jira] [Updated] (HBASE-6059) Replaying recovered edits would make deleted data exist again

[ https://issues.apache.org/jira/browse/HBASE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6059: -- Status: Patch Available (was: Open) > Replaying recovered edits would make

[jira] [Updated] (HBASE-6065) Log for flush would append a non-sequential edit in the hlog， may cause data loss

[ https://issues.apache.org/jira/browse/HBASE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-6065: -- Status: Patch Available (was: Open) > Log for flush would append a non-seq