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 2009/06/17 18:42:07 UTC

[jira] Created: (HBASE-1533) [compactor] INFO org.apache.hadoop.hdfs.DFSClient: Could not obtain block blk_-2838183878654532516_9970 from any node: java.io.IOException: No live nodes contain current block

[compactor] INFO org.apache.hadoop.hdfs.DFSClient: Could not obtain block blk_-2838183878654532516_9970 from any node:  java.io.IOException: No live nodes contain current block
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: HBASE-1533
                 URL: https://issues.apache.org/jira/browse/HBASE-1533
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack
             Fix For: 0.20.0


I see this during bulk upload into TRUNK.  Happens often enough.  Odd is that its INFO level and the compaction seems to succeed.  Figure out whats going on here.  The log is disturbing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (HBASE-1533) [compactor] INFO org.apache.hadoop.hdfs.DFSClient: Could not obtain block blk_-2838183878654532516_9970 from any node: java.io.IOException: No live nodes contain current block

Posted by "stack (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725917#action_12725917 ] 

stack commented on HBASE-1533:
------------------------------

I ran big upload and don't see these any more once I'd applied 4681.

> [compactor] INFO org.apache.hadoop.hdfs.DFSClient: Could not obtain block blk_-2838183878654532516_9970 from any node:  java.io.IOException: No live nodes contain current block
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1533
>                 URL: https://issues.apache.org/jira/browse/HBASE-1533
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.20.0
>
>
> I see this during bulk upload into TRUNK.  Happens often enough.  Odd is that its INFO level and the compaction seems to succeed.  Figure out whats going on here.  The log is disturbing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (HBASE-1533) [compactor] INFO org.apache.hadoop.hdfs.DFSClient: Could not obtain block blk_-2838183878654532516_9970 from any node: java.io.IOException: No live nodes contain current block

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-1533.
--------------------------

    Resolution: Invalid

This is me running an HADOOP that didn't have 4681 applied.  Resolving as 'invalid'.

> [compactor] INFO org.apache.hadoop.hdfs.DFSClient: Could not obtain block blk_-2838183878654532516_9970 from any node:  java.io.IOException: No live nodes contain current block
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1533
>                 URL: https://issues.apache.org/jira/browse/HBASE-1533
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.20.0
>
>
> I see this during bulk upload into TRUNK.  Happens often enough.  Odd is that its INFO level and the compaction seems to succeed.  Figure out whats going on here.  The log is disturbing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.