[jira] [Updated] (HBASE-3725) HBase increments from old value after delete and write to disk

[ https://issues.apache.org/jira/browse/HBASE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ShiXing updated HBASE-3725: --- Attachment: HBASE-3725-0.92-V6.patch toTed bq. TestHRegion#testIncrementWithFlushAndDelete passed without

[jira] [Commented] (HBASE-6411) Move Master Metrics to metrics 2

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

[jira] [Created] (HBASE-6433) improve getRemoteAddress

binlijin created HBASE-6433: --- Summary: improve getRemoteAddress Key: HBASE-6433 URL: https://issues.apache.org/jira/browse/HBASE-6433 Project: HBase Issue Type: Improvement Reporter:

[jira] [Updated] (HBASE-6429) Filter with filterRow() returning true is also incompatible with scan with limit

[ https://issues.apache.org/jira/browse/HBASE-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6429: -- Status: Patch Available (was: Open) Filter with filterRow() returning true is also

[jira] [Commented] (HBASE-3725) HBase increments from old value after delete and write to disk

[ https://issues.apache.org/jira/browse/HBASE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419046#comment-13419046 ] Zhihong Ted Yu commented on HBASE-3725: --- How about renaming leftResults as

[jira] [Updated] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] binlijin updated HBASE-6433: Attachment: HBASE-6433-trunk.patch improve getRemoteAddress

[jira] [Updated] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] binlijin updated HBASE-6433: Attachment: HBASE-6433-94.patch HBASE-6433-90.patch HBASE-6433-92.patch

[jira] [Commented] (HBASE-6429) Filter with filterRow() returning true is also incompatible with scan with limit

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

[jira] [Updated] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] binlijin updated HBASE-6433: Description: Without this patch it costs 4000ns, with this patch it costs 1600ns improve

[jira] [Updated] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6433: -- Status: Patch Available (was: Open) improve getRemoteAddress

[jira] [Updated] (HBASE-6429) Filter with filterRow() returning true is incompatible with scan with limit

[ https://issues.apache.org/jira/browse/HBASE-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6429: -- Summary: Filter with filterRow() returning true is incompatible with scan with limit (was:

[jira] [Commented] (HBASE-6429) Filter with filterRow() returning true is incompatible with scan with limit

[ https://issues.apache.org/jira/browse/HBASE-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419124#comment-13419124 ] Zhihong Ted Yu commented on HBASE-6429: --- TestFilterWithScanLimits.java and

[jira] [Updated] (HBASE-6429) Filter with filterRow() returning true is incompatible with scan with limit

[ https://issues.apache.org/jira/browse/HBASE-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6429: -- Status: Open (was: Patch Available) Filter with filterRow() returning true is

[jira] [Commented] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419152#comment-13419152 ] Zhihong Ted Yu commented on HBASE-6433: --- The trunk patch contains reordering of

[jira] [Assigned] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu reassigned HBASE-6433: - Assignee: binlijin improve getRemoteAddress

[jira] [Updated] (HBASE-6433) improve getRemoteAddress

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

[jira] [Commented] (HBASE-6433) improve getRemoteAddress

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

[jira] [Updated] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6433: -- Attachment: 6433-getRemoteAddress-trunk.txt Simplified patch for trunk.

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419207#comment-13419207 ] Zhihong Ted Yu commented on HBASE-5547: --- Will integrate in 3 hours if there is no

[jira] [Commented] (HBASE-3725) HBase increments from old value after delete and write to disk

[ https://issues.apache.org/jira/browse/HBASE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419255#comment-13419255 ] Zhihong Ted Yu commented on HBASE-3725: --- In trunk, getLastIncrement() call has been

[jira] [Assigned] (HBASE-3725) HBase increments from old value after delete and write to disk

[ https://issues.apache.org/jira/browse/HBASE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu reassigned HBASE-3725: - Assignee: ShiXing (was: Jonathan Gray) HBase increments from old value after

[jira] [Updated] (HBASE-3725) HBase increments from old value after delete and write to disk

[ https://issues.apache.org/jira/browse/HBASE-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-3725: -- Fix Version/s: 0.92.2 HBase increments from old value after delete and write to disk

[jira] [Commented] (HBASE-6432) HRegionServer doesn't properly set clusterId in conf

[ https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419263#comment-13419263 ] Andrew Purtell commented on HBASE-6432: --- Seems reasonable and low risk to pull the

[jira] [Updated] (HBASE-6432) HRegionServer doesn't properly set clusterId in conf

[ https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-6432: -- Affects Version/s: 0.96.0 Fix Version/s: (was: 0.96.0) HRegionServer doesn't

[jira] [Comment Edited] (HBASE-6432) HRegionServer doesn't properly set clusterId in conf

[ https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419271#comment-13419271 ] Andrew Purtell edited comment on HBASE-6432 at 7/20/12 3:44 PM:

[jira] [Commented] (HBASE-6432) HRegionServer doesn't properly set clusterId in conf

[ https://issues.apache.org/jira/browse/HBASE-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419271#comment-13419271 ] Andrew Purtell commented on HBASE-6432: --- However, the master is responsible for

[jira] [Commented] (HBASE-6428) Pluggable Compaction policies

[ https://issues.apache.org/jira/browse/HBASE-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419279#comment-13419279 ] Andrew Purtell commented on HBASE-6428: --- bq. For example one could envision storing

[jira] [Commented] (HBASE-6433) improve getRemoteAddress

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

[jira] [Created] (HBASE-6434) Document effect of slow compressors on the flush path and workaround in the online book

Andrew Purtell created HBASE-6434: - Summary: Document effect of slow compressors on the flush path and workaround in the online book Key: HBASE-6434 URL: https://issues.apache.org/jira/browse/HBASE-6434

[jira] [Commented] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419316#comment-13419316 ] Zhihong Ted Yu commented on HBASE-6433: --- I ran the two tests listed above and they

[jira] [Created] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

nkeywal created HBASE-6435: -- Summary: Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes Key: HBASE-6435 URL: https://issues.apache.org/jira/browse/HBASE-6435

[jira] [Commented] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

[ https://issues.apache.org/jira/browse/HBASE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419356#comment-13419356 ] nkeywal commented on HBASE-6401: @stack bq. Does svn blame/git bisecting not turn up the

[jira] [Commented] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

[ https://issues.apache.org/jira/browse/HBASE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419358#comment-13419358 ] nkeywal commented on HBASE-6401: HBASE-6435 will lower the probability to get the issue

[jira] [Commented] (HBASE-6433) improve getRemoteAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419360#comment-13419360 ] Jean-Daniel Cryans commented on HBASE-6433: --- Can we have a meaningful jira title

[jira] [Updated] (HBASE-6411) Move Master Metrics to metrics 2

[ https://issues.apache.org/jira/browse/HBASE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Baranau updated HBASE-6411: Attachment: HBASE-6411-1.patch Adjusted Elliott's patch. Added example unit-test for

[jira] [Updated] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhihong Ted Yu updated HBASE-6433: -- Description: Currently, HBaseServer#getRemoteAddress would call getRemoteIp(), leading to

[jira] [Commented] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

[ https://issues.apache.org/jira/browse/HBASE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419398#comment-13419398 ] nkeywal commented on HBASE-6401: @stack The oldest version of DFSInputStream.java (its

[jira] [Commented] (HBASE-6411) Move Master Metrics to metrics 2

[ https://issues.apache.org/jira/browse/HBASE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419399#comment-13419399 ] Elliott Clark commented on HBASE-6411: -- bq.Will try to extract maps in

[jira] [Commented] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419408#comment-13419408 ] Jean-Daniel Cryans commented on HBASE-6433: --- Thanks you!

[jira] [Created] (HBASE-6436) Netty should be moved off of snapshots.

Elliott Clark created HBASE-6436: Summary: Netty should be moved off of snapshots. Key: HBASE-6436 URL: https://issues.apache.org/jira/browse/HBASE-6436 Project: HBase Issue Type: Task

[jira] [Updated] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-6435: --- Attachment: 6435.unfinished.patch Reading WAL files after a recovery leads to time lost in HDFS

[jira] [Commented] (HBASE-6411) Move Master Metrics to metrics 2

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

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419414#comment-13419414 ] nkeywal commented on HBASE-6435: The patch is not finished. Actually, it contains for code

[jira] [Commented] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

[ https://issues.apache.org/jira/browse/HBASE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419423#comment-13419423 ] nkeywal commented on HBASE-6401: HDFS-3222 is not exactly this one, but not far, and fixed

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419446#comment-13419446 ] Todd Lipcon commented on HBASE-6435: I'm -1 on this kind of hack going into HBase

[jira] [Commented] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419461#comment-13419461 ] Zhihong Ted Yu commented on HBASE-6433: --- Integrated to trunk. Thanks for the patch,

[jira] [Commented] (HBASE-6389) Modify the conditions to ensure that Master waits for sufficient number of Region Servers before starting region assignments

[ https://issues.apache.org/jira/browse/HBASE-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419491#comment-13419491 ] Aditya Kishore commented on HBASE-6389: --- bq. BTW what do Ri, C and Fi represent in

[jira] [Commented] (HBASE-6389) Modify the conditions to ensure that Master waits for sufficient number of Region Servers before starting region assignments

[ https://issues.apache.org/jira/browse/HBASE-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419529#comment-13419529 ] stack commented on HBASE-6389: -- @Lars Its up to you (But since you asked, fine by me ... I

[jira] [Commented] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419535#comment-13419535 ] stack commented on HBASE-6433: -- @binlijin Why not change what getRemoteIp does internally

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419551#comment-13419551 ] stack commented on HBASE-6435: -- Yeah, we should do both (I'd think that whats added to HDFS

[jira] [Commented] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419552#comment-13419552 ] Hudson commented on HBASE-6433: --- Integrated in HBase-TRUNK #3155 (See

[jira] [Commented] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419561#comment-13419561 ] Zhihong Ted Yu commented on HBASE-6433: --- Looking at the code, Connection has this

[jira] [Commented] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

[ https://issues.apache.org/jira/browse/HBASE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419579#comment-13419579 ] stack commented on HBASE-6401: -- @Nkeywal We need another patch on top of hdfs-3222?

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419581#comment-13419581 ] nkeywal commented on HBASE-6435: My thinking was it could make it on a hdfs release that

[jira] [Commented] (HBASE-6401) HBase may lose edits after a crash if used with HDFS 1.0.3 or older

[ https://issues.apache.org/jira/browse/HBASE-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419585#comment-13419585 ] nkeywal commented on HBASE-6401: On 1.x, yes, I think that backporting hdfs-3222 won't be

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419588#comment-13419588 ] Todd Lipcon commented on HBASE-6435: I think there's a good motivation to add these

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419608#comment-13419608 ] nkeywal commented on HBASE-6435: I understand that you don't want to expose the internal

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419623#comment-13419623 ] Todd Lipcon commented on HBASE-6435: bq. With the current DFSClient implementation, a

[jira] [Updated] (HBASE-6321) ReplicationSource dies reading the peer's id

[ https://issues.apache.org/jira/browse/HBASE-6321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans updated HBASE-6321: -- Attachment: HBASE-6321-0.94.patch Had a stab at this. What I figured is that the

[jira] [Updated] (HBASE-6321) ReplicationSource dies reading the peer's id

[ https://issues.apache.org/jira/browse/HBASE-6321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans updated HBASE-6321: -- Fix Version/s: (was: 0.90.8) Assignee: Jean-Daniel Cryans Assigning this

[jira] [Commented] (HBASE-6321) ReplicationSource dies reading the peer's id

[ https://issues.apache.org/jira/browse/HBASE-6321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419633#comment-13419633 ] Jean-Daniel Cryans commented on HBASE-6321: --- Oh I forgot to mention that I ran

[jira] [Commented] (HBASE-6435) Reading WAL files after a recovery leads to time lost in HDFS timeouts when using dead datanodes

[ https://issues.apache.org/jira/browse/HBASE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419646#comment-13419646 ] nkeywal commented on HBASE-6435: If I can to keep the existing interface Today, when you

[jira] [Commented] (HBASE-5985) TestMetaMigrationRemovingHTD failed with HADOOP 2.0.0

[ https://issues.apache.org/jira/browse/HBASE-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419648#comment-13419648 ] Hudson commented on HBASE-5985: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6397) [hbck] print out bulk load commands for sidelined regions if necessary

[ https://issues.apache.org/jira/browse/HBASE-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419654#comment-13419654 ] Hudson commented on HBASE-6397: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6426) Add Hadoop 2.0.x profile to 0.92+

[ https://issues.apache.org/jira/browse/HBASE-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419647#comment-13419647 ] Hudson commented on HBASE-6426: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6389) Modify the conditions to ensure that Master waits for sufficient number of Region Servers before starting region assignments

[ https://issues.apache.org/jira/browse/HBASE-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419649#comment-13419649 ] Hudson commented on HBASE-6389: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6406) TestReplicationPeer.testResetZooKeeperSession and TestZooKeeper.testClientSessionExpired fail frequently

[ https://issues.apache.org/jira/browse/HBASE-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419651#comment-13419651 ] Hudson commented on HBASE-6406: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6319) ReplicationSource can call terminate on itself and deadlock

[ https://issues.apache.org/jira/browse/HBASE-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419650#comment-13419650 ] Hudson commented on HBASE-6319: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-4956) Control direct memory buffer consumption by HBaseClient

[ https://issues.apache.org/jira/browse/HBASE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419652#comment-13419652 ] Hudson commented on HBASE-4956: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6392) UnknownRegionException blocks hbck from sideline big overlap regions

[ https://issues.apache.org/jira/browse/HBASE-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419657#comment-13419657 ] Hudson commented on HBASE-6392: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6420) Gracefully shutdown logsyncer

[ https://issues.apache.org/jira/browse/HBASE-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419653#comment-13419653 ] Hudson commented on HBASE-6420: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6325) [replication] Race in ReplicationSourceManager.init can initiate a failover even if the node is alive

[ https://issues.apache.org/jira/browse/HBASE-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419658#comment-13419658 ] Hudson commented on HBASE-6325: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-6382) Upgrade Jersey to 1.8 to match Hadoop 1 and 2

[ https://issues.apache.org/jira/browse/HBASE-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419656#comment-13419656 ] Hudson commented on HBASE-6382: --- Integrated in HBase-0.94-security #44 (See

[jira] [Commented] (HBASE-5966) MapReduce based tests broken on Hadoop 2.0.0-alpha

[ https://issues.apache.org/jira/browse/HBASE-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419655#comment-13419655 ] Hudson commented on HBASE-5966: --- Integrated in HBase-0.94-security #44 (See

[jira] [Resolved] (HBASE-6310) -ROOT- corruption when .META. is using the old encoding scheme

[ https://issues.apache.org/jira/browse/HBASE-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans resolved HBASE-6310. --- Resolution: Invalid Fix Version/s: (was: 0.94.2)

[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=13419691#comment-13419691 ] Jimmy Xiang commented on HBASE-6228: I'd like to fix this in HBASE-6381 by making sure

[jira] [Commented] (HBASE-6433) Improve HBaseServer#getRemoteAddress by utilizing HBaseServer.Connection.hostAddress

[ https://issues.apache.org/jira/browse/HBASE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419692#comment-13419692 ] Hudson commented on HBASE-6433: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #101 (See

[jira] [Commented] (HBASE-6428) Pluggable Compaction policies

[ https://issues.apache.org/jira/browse/HBASE-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419695#comment-13419695 ] Lars Hofhansl commented on HBASE-6428: -- That is an excellent point. Should also think

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419696#comment-13419696 ] Lars Hofhansl commented on HBASE-5547: -- +1 on patch. Ted pinged me, that he is out

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419697#comment-13419697 ] Jesse Yates commented on HBASE-5547: @Lars I don't think it would be all that

[jira] [Commented] (HBASE-5659) TestAtomicOperation.testMultiRowMutationMultiThreads is still failing occasionally

[ https://issues.apache.org/jira/browse/HBASE-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419722#comment-13419722 ] Lars Hofhansl commented on HBASE-5659: -- Without parent the revised test fails every

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419723#comment-13419723 ] Lars Hofhansl commented on HBASE-5547: -- I also verified in a real setup, that an

[jira] [Updated] (HBASE-5659) TestAtomicOperation.testMultiRowMutationMultiThreads is still failing occasionally

[ https://issues.apache.org/jira/browse/HBASE-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-5659: - Fix Version/s: 0.94.2 TestAtomicOperation.testMultiRowMutationMultiThreads is still failing

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419724#comment-13419724 ] Lars Hofhansl commented on HBASE-5547: -- Ok. On more question I asked just now on RB:

[jira] [Comment Edited] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419725#comment-13419725 ] Lars Hofhansl edited comment on HBASE-5547 at 7/21/12 2:49 AM:

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419725#comment-13419725 ] Lars Hofhansl commented on HBASE-5547: -- Or is it that all region are first deleted

[jira] [Commented] (HBASE-5954) Allow proper fsync support for HBase

[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419738#comment-13419738 ] Lars Hofhansl commented on HBASE-5954: -- I think the API going multiple ways (these

[jira] [Comment Edited] (HBASE-5954) Allow proper fsync support for HBase

[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419738#comment-13419738 ] Lars Hofhansl edited comment on HBASE-5954 at 7/21/12 4:01 AM:

[jira] [Updated] (HBASE-6406) TestReplicationPeer.testResetZooKeeperSession and TestZooKeeper.testClientSessionExpired fail frequently

[ https://issues.apache.org/jira/browse/HBASE-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6406: - Fix Version/s: (was: 0.94.1) 0.94.2

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419746#comment-13419746 ] Zhihong Ted Yu commented on HBASE-5547: --- I think the latest patch has addressed

[jira] [Commented] (HBASE-5547) Don't delete HFiles when in backup mode

[ https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419748#comment-13419748 ] Lars Hofhansl commented on HBASE-5547: -- True, but if dropping a table just drops the