You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/07/26 03:25:31 UTC
[jira] Created: (HBASE-778) Handler code for missing 'data' files
failing
Handler code for missing 'data' files failing
---------------------------------------------
Key: HBASE-778
URL: https://issues.apache.org/jira/browse/HBASE-778
Project: Hadoop HBase
Issue Type: Bug
Reporter: stack
Priority: Blocker
Fix For: 0.2.0
Attachments: empty.patch
Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-778:
------------------------
Fix Version/s: (was: 0.2.0)
Moving out of 0.2.0. HBASE-766 was the real issue.
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: empty-v2.patch, empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617125#action_12617125 ]
stack commented on HBASE-778:
-----------------------------
Unit tests fail. Dig in why.
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
> Fix For: 0.2.0
>
> Attachments: empty-v2.patch, empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-778:
------------------------
Attachment: empty-v2.patch
Better patch. Here is guts of change:
{code}
private boolean isEmptyFile(final Path f)
throws IOException {
- return this.fs.exists(f) &&
- this.fs.getFileStatus(f).getLen() == 0;
+ return !this.fs.exists(f) || this.fs.getFileStatus(f).getLen() == 0;
{code}
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
> Fix For: 0.2.0
>
> Attachments: empty-v2.patch, empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-778:
------------------------
Attachment: empty.patch
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
> Fix For: 0.2.0
>
> Attachments: empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-778.
-------------------------
Resolution: Invalid
I applied patch anyways and it fails in TestHRegion and TestSplit. I'm guessing its because patch changes meaning of isEmptyFile. Bad idea. Resolving as invalid with HBASE-766 as real issue.
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: empty-v2.patch, empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman reassigned HBASE-778:
-----------------------------------
Assignee: stack
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.2.0
>
> Attachments: empty-v2.patch, empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-778) Handler code for missing 'data' files
failing
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-778:
------------------------
Priority: Major (was: Blocker)
Not a blocker. Knocking it down to 'major'. The reopened HBASE-766 is the real cause of the FNFE we've been seeing.
> Handler code for missing 'data' files failing
> ---------------------------------------------
>
> Key: HBASE-778
> URL: https://issues.apache.org/jira/browse/HBASE-778
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.2.0
>
> Attachments: empty-v2.patch, empty.patch
>
>
> Renaud Delbri up on the list and Jon Gray just now ran into issue where getting length of an HSF inside in the HStore constructor failed with FNFE. Test of length is done after supposed tests that file exists so odd.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.