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 "stack (JIRA)" <ji...@apache.org> on 2007/12/12 08:11:43 UTC
[jira] Created: (HADOOP-2407) [hbase] Keeping MapFile.Reader open
is expensive: Part 2
[hbase] Keeping MapFile.Reader open is expensive: Part 2
--------------------------------------------------------
Key: HADOOP-2407
URL: https://issues.apache.org/jira/browse/HADOOP-2407
Project: Hadoop
Issue Type: Improvement
Components: contrib/hbase
Reporter: stack
Fix For: 0.16.0
In hbase, a mapfile.Reader can be opened and a long period of time may pass before any accesses are made against the file. It can also be the case that a MapFile will be opened and never accessed. For every open unaccessed MapFile -- i.e. next or a record at some offset hasn't been pulled -- we'll consume two sockets in datanode, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2407) [hbase] Keeping MapFile.Reader open
is expensive: Part 2
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-2407:
--------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed. Failure was in TestRegionServerExit, unrelated. Resolving.
> [hbase] Keeping MapFile.Reader open is expensive: Part 2
> --------------------------------------------------------
>
> Key: HADOOP-2407
> URL: https://issues.apache.org/jira/browse/HADOOP-2407
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: stack
> Fix For: 0.16.0
>
> Attachments: hsf.patch
>
>
> In hbase, a mapfile.Reader can be opened and a long period of time may pass before any accesses are made against the file. It can also be the case that a MapFile will be opened and never accessed. For every open unaccessed MapFile -- i.e. next or a record at some offset hasn't been pulled -- we'll consume two sockets in datanode, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2407) [hbase] Keeping MapFile.Reader open
is expensive: Part 2
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551481 ]
Hudson commented on HADOOP-2407:
--------------------------------
Integrated in Hadoop-Nightly #331 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/331/])
> [hbase] Keeping MapFile.Reader open is expensive: Part 2
> --------------------------------------------------------
>
> Key: HADOOP-2407
> URL: https://issues.apache.org/jira/browse/HADOOP-2407
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: stack
> Fix For: 0.16.0
>
> Attachments: hsf.patch
>
>
> In hbase, a mapfile.Reader can be opened and a long period of time may pass before any accesses are made against the file. It can also be the case that a MapFile will be opened and never accessed. For every open unaccessed MapFile -- i.e. next or a record at some offset hasn't been pulled -- we'll consume two sockets in datanode, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2407) [hbase] Keeping MapFile.Reader open
is expensive: Part 2
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-2407:
--------------------------
Attachment: hsf.patch
Force reading of MapFile index
> [hbase] Keeping MapFile.Reader open is expensive: Part 2
> --------------------------------------------------------
>
> Key: HADOOP-2407
> URL: https://issues.apache.org/jira/browse/HADOOP-2407
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: stack
> Fix For: 0.16.0
>
> Attachments: hsf.patch
>
>
> In hbase, a mapfile.Reader can be opened and a long period of time may pass before any accesses are made against the file. It can also be the case that a MapFile will be opened and never accessed. For every open unaccessed MapFile -- i.e. next or a record at some offset hasn't been pulled -- we'll consume two sockets in datanode, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-2407) [hbase] Keeping MapFile.Reader open
is expensive: Part 2
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HADOOP-2407:
--------------------------
Status: Patch Available (was: Open)
Passes tests locally.
> [hbase] Keeping MapFile.Reader open is expensive: Part 2
> --------------------------------------------------------
>
> Key: HADOOP-2407
> URL: https://issues.apache.org/jira/browse/HADOOP-2407
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: stack
> Fix For: 0.16.0
>
> Attachments: hsf.patch
>
>
> In hbase, a mapfile.Reader can be opened and a long period of time may pass before any accesses are made against the file. It can also be the case that a MapFile will be opened and never accessed. For every open unaccessed MapFile -- i.e. next or a record at some offset hasn't been pulled -- we'll consume two sockets in datanode, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-2407) [hbase] Keeping MapFile.Reader open
is expensive: Part 2
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550885 ]
Hadoop QA commented on HADOOP-2407:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12371488/hsf.patch
against trunk revision r603428.
@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 failed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1325/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1325/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1325/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1325/console
This message is automatically generated.
> [hbase] Keeping MapFile.Reader open is expensive: Part 2
> --------------------------------------------------------
>
> Key: HADOOP-2407
> URL: https://issues.apache.org/jira/browse/HADOOP-2407
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: stack
> Fix For: 0.16.0
>
> Attachments: hsf.patch
>
>
> In hbase, a mapfile.Reader can be opened and a long period of time may pass before any accesses are made against the file. It can also be the case that a MapFile will be opened and never accessed. For every open unaccessed MapFile -- i.e. next or a record at some offset hasn't been pulled -- we'll consume two sockets in datanode, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.