You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2007/12/18 04:11:43 UTC
[jira] Created: (HADOOP-2451) [hbase] End key is incorrectly
assigned in many region splits
[hbase] End key is incorrectly assigned in many region splits
-------------------------------------------------------------
Key: HADOOP-2451
URL: https://issues.apache.org/jira/browse/HADOOP-2451
Project: Hadoop
Issue Type: Bug
Components: contrib/hbase
Affects Versions: 0.16.0
Reporter: Jim Kellerman
Assignee: Jim Kellerman
Priority: Critical
Fix For: 0.16.0
When a region is split, the new child region for the upper half of the key range is always assigned as null (meaning end of table). If splits only happen at the end of the table, this is harmless. However under a random write load, an inner region is just as likely to split.
This would explain why we have seen cases where after a split, there are multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2451) [hbase] End key is incorrectly
assigned in many region splits
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman updated HADOOP-2451:
----------------------------------
Status: Patch Available (was: Open)
> [hbase] End key is incorrectly assigned in many region splits
> -------------------------------------------------------------
>
> Key: HADOOP-2451
> URL: https://issues.apache.org/jira/browse/HADOOP-2451
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.16.0
>
> Attachments: patch.txt
>
>
> When a region is split, the new child region for the upper half of the key range is always assigned as null (meaning end of table). If splits only happen at the end of the table, this is harmless. However under a random write load, an inner region is just as likely to split.
> This would explain why we have seen cases where after a split, there are multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2451) [hbase] End key is incorrectly
assigned in many region splits
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman updated HADOOP-2451:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Tests passed. Committed.
> [hbase] End key is incorrectly assigned in many region splits
> -------------------------------------------------------------
>
> Key: HADOOP-2451
> URL: https://issues.apache.org/jira/browse/HADOOP-2451
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.16.0
>
> Attachments: patch.txt
>
>
> When a region is split, the new child region for the upper half of the key range is always assigned as null (meaning end of table). If splits only happen at the end of the table, this is harmless. However under a random write load, an inner region is just as likely to split.
> This would explain why we have seen cases where after a split, there are multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2451) [hbase] End key is incorrectly
assigned in many region splits
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman updated HADOOP-2451:
----------------------------------
Attachment: patch.txt
> [hbase] End key is incorrectly assigned in many region splits
> -------------------------------------------------------------
>
> Key: HADOOP-2451
> URL: https://issues.apache.org/jira/browse/HADOOP-2451
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.16.0
>
> Attachments: patch.txt
>
>
> When a region is split, the new child region for the upper half of the key range is always assigned as null (meaning end of table). If splits only happen at the end of the table, this is harmless. However under a random write load, an inner region is just as likely to split.
> This would explain why we have seen cases where after a split, there are multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2451) [hbase] End key is incorrectly
assigned in many region splits
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552737 ]
Hudson commented on HADOOP-2451:
--------------------------------
Integrated in Hadoop-Nightly #337 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/337/])
> [hbase] End key is incorrectly assigned in many region splits
> -------------------------------------------------------------
>
> Key: HADOOP-2451
> URL: https://issues.apache.org/jira/browse/HADOOP-2451
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.16.0
>
> Attachments: patch.txt
>
>
> When a region is split, the new child region for the upper half of the key range is always assigned as null (meaning end of table). If splits only happen at the end of the table, this is harmless. However under a random write load, an inner region is just as likely to split.
> This would explain why we have seen cases where after a split, there are multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2451) [hbase] End key is incorrectly
assigned in many region splits
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552638 ]
Hadoop QA commented on HADOOP-2451:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12371841/patch.txt
against trunk revision r604999.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1378/console
This message is automatically generated.
> [hbase] End key is incorrectly assigned in many region splits
> -------------------------------------------------------------
>
> Key: HADOOP-2451
> URL: https://issues.apache.org/jira/browse/HADOOP-2451
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.16.0
>
> Attachments: patch.txt
>
>
> When a region is split, the new child region for the upper half of the key range is always assigned as null (meaning end of table). If splits only happen at the end of the table, this is harmless. However under a random write load, an inner region is just as likely to split.
> This would explain why we have seen cases where after a split, there are multiple regions whose end key is the end of the table (null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.