[jira] [Commented] (HBASE-2247) [performance] Small scans should run like a random-read

[ https://issues.apache.org/jira/browse/HBASE-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461331#comment-13461331 ] LiuLei commented on HBASE-2247: --- Hi stack， I think We can new smallScan() method in HTable,

[jira] [Updated] (HBASE-6869) Update our hadoop-2 to 2.0.1-alpha

[ https://issues.apache.org/jira/browse/HBASE-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6869: - Attachment: 6869.txt Update our hadoop-2 to 2.0.1-alpha --

[jira] [Resolved] (HBASE-6869) Update our hadoop-2 to 2.0.1-alpha

[ https://issues.apache.org/jira/browse/HBASE-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-6869. -- Resolution: Fixed Fix Version/s: 0.96.0 Assignee: stack Update from 2.0.0-alpha to

[jira] [Commented] (HBASE-6869) Update our hadoop-2 to 2.0.1-alpha

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

[jira] [Commented] (HBASE-6868) Skip checksum is broke; are we double-checksumming by default?

[ https://issues.apache.org/jira/browse/HBASE-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461485#comment-13461485 ] Lars Hofhansl commented on HBASE-6868: -- OK. So can we just document then that

[jira] [Commented] (HBASE-6868) Skip checksum is broke; are we double-checksumming by default?

[ https://issues.apache.org/jira/browse/HBASE-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461494#comment-13461494 ] Lars Hofhansl commented on HBASE-6868: -- We keep going back and forth between

[jira] [Updated] (HBASE-6868) Skip checksum is broke; are we double-checksumming by default?

[ https://issues.apache.org/jira/browse/HBASE-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6868: - Attachment: 6868-0.96-idea.txt So how about this? Check that short circuit is enabled for HBase

[jira] [Updated] (HBASE-6868) Skip checksum is broke; are we double-checksumming by default?

[ https://issues.apache.org/jira/browse/HBASE-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6868: - Attachment: (was: 6868-0.96-idea.txt) Skip checksum is broke; are we

[jira] [Updated] (HBASE-6868) Skip checksum is broke; are we double-checksumming by default?

[ https://issues.apache.org/jira/browse/HBASE-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-6868: - Attachment: 6868-0.96-idea.txt The right patch, this time. Skip checksum is

[jira] [Updated] (HBASE-6381) AssignmentManager should use the same logic for clean startup and failover

[ https://issues.apache.org/jira/browse/HBASE-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-6381: --- Attachment: trunk-6381_v9.patch AssignmentManager should use the same logic for clean startup

[jira] [Updated] (HBASE-6381) AssignmentManager should use the same logic for clean startup and failover

[ https://issues.apache.org/jira/browse/HBASE-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-6381: --- Status: Open (was: Patch Available) AssignmentManager should use the same logic for clean

[jira] [Updated] (HBASE-6381) AssignmentManager should use the same logic for clean startup and failover

[ https://issues.apache.org/jira/browse/HBASE-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-6381: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open) AssignmentManager should

[jira] [Commented] (HBASE-6381) AssignmentManager should use the same logic for clean startup and failover

[ https://issues.apache.org/jira/browse/HBASE-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461520#comment-13461520 ] Jimmy Xiang commented on HBASE-6381: The latest patch addressed Rajesh's comments.

[jira] [Updated] (HBASE-6071) getRegionServerWithRetires, should log unsuccessful attempts and exceptions.

[ https://issues.apache.org/jira/browse/HBASE-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igal Shilman updated HBASE-6071: Attachment: HBASE-6071.v5.patch Attaching a version, that logs unsuccessful attempts only if

[jira] [Commented] (HBASE-6381) AssignmentManager should use the same logic for clean startup and failover

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

[jira] [Commented] (HBASE-6071) getRegionServerWithRetires, should log unsuccessful attempts and exceptions.

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

[jira] [Commented] (HBASE-6869) Update our hadoop-2 to 2.0.1-alpha

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

[jira] [Commented] (HBASE-6869) Update our hadoop-2 to 2.0.1-alpha

[ https://issues.apache.org/jira/browse/HBASE-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461544#comment-13461544 ] Andrew Purtell commented on HBASE-6869: --- @Lars: There was discussion (on general@ I

[jira] [Commented] (HBASE-2247) [performance] Small scans should run like a random-read

[ https://issues.apache.org/jira/browse/HBASE-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461546#comment-13461546 ] Andrew Purtell commented on HBASE-2247: --- -1 on adding a new API that duplicates

[jira] [Commented] (HBASE-6852) SchemaMetrics.updateOnCacheHit costs too much while full scanning a table with all of its fields

[ https://issues.apache.org/jira/browse/HBASE-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461559#comment-13461559 ] Cheng Hao commented on HBASE-6852: -- {quote} Cheng Hao: you said that your dataset size

[jira] [Commented] (HBASE-3909) Add dynamic config

[ https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461560#comment-13461560 ] Subbu M Iyer commented on HBASE-3909: - Stack: Which RB version should l target my

[jira] [Commented] (HBASE-2247) [performance] Small scans should run like a random-read

[ https://issues.apache.org/jira/browse/HBASE-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461563#comment-13461563 ] binlijin commented on HBASE-2247: - or we can take the hint information in the Scan object,

[jira] [Commented] (HBASE-6854) Deletion of SPLITTING node on split rollback should clear the region from RIT

[ https://issues.apache.org/jira/browse/HBASE-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461565#comment-13461565 ] Jieshan Bean commented on HBASE-6854: - We also found the same problem. Only 2 minor

[jira] [Commented] (HBASE-2247) [performance] Small scans should run like a random-read

[ https://issues.apache.org/jira/browse/HBASE-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461575#comment-13461575 ] LiuLei commented on HBASE-2247: --- +1 on adding one option in Scan.

[jira] [Commented] (HBASE-6679) RegionServer aborts due to race between compaction and split

[ https://issues.apache.org/jira/browse/HBASE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461594#comment-13461594 ] ramkrishna.s.vasudevan commented on HBASE-6679: --- Any updates on this issue?

[jira] [Commented] (HBASE-6854) Deletion of SPLITTING node on split rollback should clear the region from RIT

[ https://issues.apache.org/jira/browse/HBASE-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461597#comment-13461597 ] ramkrishna.s.vasudevan commented on HBASE-6854: --- @Jieshan Is it ok if i

[jira] [Created] (HBASE-6870) HTable#coprocessorExec always scan the whole table

chunhui shen created HBASE-6870: --- Summary: HTable#coprocessorExec always scan the whole table Key: HBASE-6870 URL: https://issues.apache.org/jira/browse/HBASE-6870 Project: HBase Issue Type:

[jira] [Updated] (HBASE-6870) HTable#coprocessorExec always scan the whole table

[ https://issues.apache.org/jira/browse/HBASE-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chunhui shen updated HBASE-6870: Attachment: HBASE-6870.patch Instead of scanning .META. for whole table,We could use region