[
https://issues.apache.org/jira/browse/PHOENIX-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395500#comment-15395500
]
Loknath Priyatham Teja Singamsetty commented on PHOENIX-3113:
--------------------------------------------------------------
ok.. looking into the reason. Surprisingly, on 4.x-HBase-0.98 jenkins build
https://builds.apache.org/view/All/job/Phoenix-4.x-HBase-0.98/1247/ the
IndexToolIT hasn't failed. Is there any order in which the integration/e2e
tests are run and will they be run in parallel?
{code}
Test Result (2 failures / +1)
org.apache.phoenix.end2end.index.AsyncImmutableIndexIT.testDeleteFromImmutable
org.apache.phoenix.end2end.index.AsyncIndexAutoBuildIT.testAsyncIndexAutoBuild
{code}
But on master build, 4 tests failed
https://builds.apache.org/job/Phoenix-master/1341/
{code}
Test Result (4 failures / +4)
org.apache.phoenix.end2end.IndexToolIT.testSecondaryIndex[transactional = true
, mutable = true , localIndex = false, directApi = false]
org.apache.phoenix.end2end.IndexToolIT.testSecondaryIndex[transactional = true
, mutable = true , localIndex = false, directApi = true]
org.apache.phoenix.end2end.index.AsyncImmutableIndexIT.testDeleteFromImmutable
org.apache.phoenix.end2end.index.AsyncIndexAutoBuildIT.testAsyncIndexAutoBuild
{code}
> Automatic build of async index will happen even if mapreduce.framework.name
> is not set in any configuration
> -----------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3113
> URL: https://issues.apache.org/jira/browse/PHOENIX-3113
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Loknath Priyatham Teja Singamsetty
> Priority: Blocker
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3113-v4.patch, PHOENIX-3113-v5.patch,
> PHOENIX-3113-v6.patch, PHOENIX-3113_test_wip.patch, phoenix-3113-v2.patch,
> phoenix-3113-v3.patch, phoenix-3113.patch
>
>
> As per below code, we are starting automatic build of async index even if
> mapreduce.framework.name is not set in any of the configuration(because
> conf.get(QueryServices.MAPRED_FRAMEWORK_NAME) will always return LOCAL as a
> default value).
> This may cause problem in the hbase cluster where mapreduce is not deployed
> or this configuration is not set or included in the classpath.
> {code}
> String hbaseClusterDistributedMode =
> conf.get(QueryServices.HBASE_CLUSTER_DISTRIBUTED_ATTRIB);
> String mapredFrameworkName =
> conf.get(QueryServices.MAPRED_FRAMEWORK_NAME);
> if ((hbaseClusterDistributedMode != null &&
> !hbaseClusterDistributedMode.equals(HBASE_CLUSTER_DISTRIBUTED_CONFIG)) ||
> (mapredFrameworkName != null &&
> !mapredFrameworkName.equals(MAPRED_FRAMEWORK_YARN_CONFIG)))
> {
> LOG.info("Enabling Async Index rebuilder");
> AsyncIndexRebuilderTask asyncIndexRebuilderTask = new
> AsyncIndexRebuilderTask(e.getEnvironment());
> // run async index rebuilder task every 10 secs to rebuild any
> newly created async indexes
> executor.scheduleAtFixedRate(asyncIndexRebuilderTask, 10000,
> rebuildIndexTimeInterval, TimeUnit.MILLISECONDS);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
