[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13071842#comment-13071842 ] nkeywal commented on HBASE-1938: bq. Any chance of our calling a 'next' without doing a

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072052#comment-13072052 ] nkeywal commented on HBASE-1938: Ok, that's strange. This patch includes multiple small

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072064#comment-13072064 ] nkeywal commented on HBASE-1938: Yes, I can provide a patch with all the changes except

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072085#comment-13072085 ] nkeywal commented on HBASE-1938: Thank you. It's interesting because the tests with 15

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072284#comment-13072284 ] nkeywal commented on HBASE-1938: Ok, I understand what's going on. The enhancement on

[jira] [Updated] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-1938: --- Attachment: 20110802_MemStore.patch MemStoreScanPerformance.java Test added to show the

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13078377#comment-13078377 ] nkeywal commented on HBASE-1938: For any future modification on this part: on jdk 1.6.24,

[jira] [Created] (HBASE-4157) Possible performance improvement in Bytes.java

Possible performance improvement in Bytes.java -- Key: HBASE-4157 URL: https://issues.apache.org/jira/browse/HBASE-4157 Project: HBase Issue Type: Improvement Components: performance

[jira] [Commented] (HBASE-1938) Make in-memory table scanning faster

[ https://issues.apache.org/jira/browse/HBASE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082435#comment-13082435 ] nkeywal commented on HBASE-1938: Yes, I believe Andy's issue was cause by: - the

[jira] [Commented] (HBASE-3855) Performance degradation of memstore because reseek is linear

[ https://issues.apache.org/jira/browse/HBASE-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083679#comment-13083679 ] nkeywal commented on HBASE-3855: I saw some points related to numIterReseek, used in the

[jira] [Created] (HBASE-4195) Possible unconsistency in a memstore read after a reseek, possible performance improvement

Possible unconsistency in a memstore read after a reseek, possible performance improvement -- Key: HBASE-4195 URL: https://issues.apache.org/jira/browse/HBASE-4195

[jira] [Updated] (HBASE-4195) Possible unconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4195: --- Description: This follows the dicussion around HBASE-3855, and the random errors (20% failure on trunk) on

[jira] [Commented] (HBASE-4195) Possible unconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083808#comment-13083808 ] nkeywal commented on HBASE-4195: FWIW, I also tried to change reseek to call seek all the

[jira] [Commented] (HBASE-4195) Possible unconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084160#comment-13084160 ] nkeywal commented on HBASE-4195: The issue with the implementation calling only seek is

[jira] [Commented] (HBASE-4195) Possible unconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1308#comment-1308 ] nkeywal commented on HBASE-4195: With the current implementation, setting the config

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13085122#comment-13085122 ] nkeywal commented on HBASE-4195: Do you want me do write the patch? You confirm that we

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086358#comment-13086358 ] nkeywal commented on HBASE-4195: I can do a simple patch (removing all the code around

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13089407#comment-13089407 ] nkeywal commented on HBASE-4195: Update: I have two other scenarios for failure, both

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13089856#comment-13089856 ] nkeywal commented on HBASE-4195: For #2, yes, it seems that HBASE-2856 is addressing this

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090073#comment-13090073 ] nkeywal commented on HBASE-4195: The behavior we have with the previous (or with the one I

[jira] [Assigned] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal reassigned HBASE-4195: -- Assignee: nkeywal Possible inconsistency in a memstore read after a reseek, possible performance

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090324#comment-13090324 ] nkeywal commented on HBASE-4195: I tested 2 cases: 1) The current implementation 2) A new

[jira] [Updated] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4195: --- Attachment: 20110824_4195_TestHRegion.patch 20110824_4195_MemStore.patch TestHRegion: added

[jira] [Commented] (HBASE-4188) Make in-memory table scanning faster, part2 (continuation of hbase-1938)

[ https://issues.apache.org/jira/browse/HBASE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090625#comment-13090625 ] nkeywal commented on HBASE-4188: Yes, I would expect them to be the scenario with

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090840#comment-13090840 ] nkeywal commented on HBASE-4195: With the current implementation, it can fails in

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098944#comment-13098944 ] nkeywal commented on HBASE-4195: Synthesis: - the patch on the test case itself helps to

[jira] [Commented] (HBASE-4188) Make in-memory table scanning faster, part2 (continuation of hbase-1938)

[ https://issues.apache.org/jira/browse/HBASE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098948#comment-13098948 ] nkeywal commented on HBASE-4188: See HBASE-4195. It's the same test. Make in-memory

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100139#comment-13100139 ] nkeywal commented on HBASE-4195: @stack: yes I am ok with all your points. Thanks! Some

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100988#comment-13100988 ] nkeywal commented on HBASE-4195: Ok, will do (likely this week end). Do you mind if I do a

[jira] [Updated] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4195: --- Attachment: 20110915_4195_4188_MemStore.patch Patch for 4195 and 4188, taking in account all the points

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105916#comment-13105916 ] nkeywal commented on HBASE-4195: I am going to check. Possible inconsistency in a

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105925#comment-13105925 ] nkeywal commented on HBASE-4195: Yes, it's because I removed a field in MemStore (the

[jira] [Updated] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4195: --- Release Note: This fixes the regression (identified by a random failure of test

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106516#comment-13106516 ] nkeywal commented on HBASE-4195: Note that I am currently running the full unit test and

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106627#comment-13106627 ] nkeywal commented on HBASE-4195: Same here, I got one failure with TestGetRowVersions, but

[jira] [Work started] (HBASE-4188) Make in-memory table scanning faster, part2 (continuation of hbase-1938)

[ https://issues.apache.org/jira/browse/HBASE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-4188 started by nkeywal. Make in-memory table scanning faster, part2 (continuation of hbase-1938)

[jira] [Commented] (HBASE-4188) Make in-memory table scanning faster, part2 (continuation of hbase-1938)

[ https://issues.apache.org/jira/browse/HBASE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106634#comment-13106634 ] nkeywal commented on HBASE-4188: Patch for this jira bug is included in HBASE-4195. Make

[jira] [Commented] (HBASE-4195) Possible inconsistency in a memstore read after a reseek, possible performance improvement

[ https://issues.apache.org/jira/browse/HBASE-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106737#comment-13106737 ] nkeywal commented on HBASE-4195: Ok, thank you. The remaining points I saw in 4195-v2.txt

[jira] [Updated] (HBASE-4468) Wrong ressource name in an error massage: webapps instead of hbase-webapps

[ https://issues.apache.org/jira/browse/HBASE-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4468: --- Attachment: 20110923_4468_InfoServer.patch the patch for the fix... Wrong ressource name in an error

[jira] [Updated] (HBASE-4468) Wrong resource name in an error massage: webapps instead of hbase-webapps

[ https://issues.apache.org/jira/browse/HBASE-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4468: --- Description: org.apache.hadoop.hbase.util.InfoServer loads a resource in 'hbase-webapps' but displays a

<    8   9   10   11   12   13