You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/12/05 23:50:00 UTC
[jira] [Resolved] (IMPALA-5958) Remove duplication of 'yarn-extras'
AllocationFileLoaderService
[ https://issues.apache.org/jira/browse/IMPALA-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-5958.
-----------------------------------
Resolution: Later
I don't think the code cleanup is worth tracking as a open JIRA
> Remove duplication of 'yarn-extras' AllocationFileLoaderService
> ---------------------------------------------------------------
>
> Key: IMPALA-5958
> URL: https://issues.apache.org/jira/browse/IMPALA-5958
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 2.11.0
> Reporter: Matthew Jacobs
> Priority: Trivial
> Labels: admission-control, ramp-up
>
> In IMPALA-5920, some Yarn code that is used by Impala admission control is brought into the Impala codebase.
> In the code review, [~zamsden] pointed out that the AllocationFileLoaderService thread for monitoring the fair-scheduler.xml file for changes could be removed if the RequestPoolService used the impala.util.FileWatcherService. See https://gerrit.cloudera.org/#/c/8035/4/common/yarn-extras/src/main/java/org/apache/impala/yarn/server/resourcemanager/scheduler/fair/AllocationFileLoaderService.java@103
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org