phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3061) IndexTool marks index as ACTIVE and exit 0 even if bulkload has error
Date Tue, 12 Jul 2016 17:49:20 GMT

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

Ankit Singhal commented on PHOENIX-3061:
----------------------------------------

may be you can try adding following option in your JAVA_OPTS
{code}
-Xmx2000m -XX:MaxPermSize=256m
{code}

Or, you can run directly from maven "mvn clean verify -Dit.test=IndexToolIT"



> IndexTool marks index as ACTIVE and exit 0 even if bulkload has error
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-3061
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3061
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.7.0
>            Reporter: Tongzhou Wang
>              Labels: easyfix
>             Fix For: 4.8.0
>
>
> In `IndexTool`, the job exits with code 0 and marks the index table as ACTIVE even though
MapReduce had error.
> See: https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java#L246-L256



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

Mime
View raw message