hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Vimont (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14879) maven archetype: mapreduce application
Date Wed, 11 May 2016 07:34:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279717#comment-15279717
] 

Daniel Vimont commented on HBASE-14879:
---------------------------------------

I am looking further at the output containing the various ERROR messages, and also looking
at the HBase source code (AssignmentManager, TableStateManager, MetaTableAccessor) that is
behind the ERROR message generation.

In the course of the mapreduce-job test processing, TableStateManager#isTableState is called
from the AssignmentManager class to find out whether a table is in a state of DISABLED or
DISABLING. Apparently, in the case of these tables, their status cannot be determined by MetaTableAccessor,
so a TableNotFoundException is thrown which is caught and results in the ERROR message being
outputted. However, on the subsequent lines of output, we see the tables being found and managed
without a problem.

For example, here is one of the ERROR messages:
{code}
2016-05-11 14:51:11,849 ERROR [B.defaultRpcServer.handler=17,queue=2,port=60857] master.TableStateManager:
Unable to get table testCopyTable1 state
org.apache.hadoop.hbase.TableNotFoundException: testCopyTable1
{code}
The very next line is an INFO message, showing that the table has been ENABLED:
{code}
2016-05-11 14:51:11,855 INFO  [ProcedureExecutor-3] hbase.MetaTableAccessor: Updated table
testCopyTable1 state to ENABLED in META
{code}
Owing to the fact that all test procedures in the mapreduce-job project are succeeding, it
seems likely to me that the ERROR messages do not signal any problem in the mapreduce-job
code or the test code that is executing it; they may signal a problem in AssignmentManager/TableStateManager/MetaTableAccessor
processing (in that the states of apparently-existing tables seem to not be accessible or
are failing to be looked up effectively).


> maven archetype: mapreduce application
> --------------------------------------
>
>                 Key: HBASE-14879
>                 URL: https://issues.apache.org/jira/browse/HBASE-14879
>             Project: HBase
>          Issue Type: Sub-task
>          Components: build, Usability
>            Reporter: Nick Dimiduk
>            Assignee: Daniel Vimont
>              Labels: beginner
>         Attachments: HBASE-14879-v1.patch, HBASE-14879-v2.patch, archetype_mr_prototype.zip
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message