Impala Daemons Error

[#1]

I have 5 datanode where impala-demons was installed and in all it shows me this error:

**************************************************************************************

log4j:ERROR Could not instantiate appender named "redactorForRootLogger".
E0426 13:25:49.818779 12933 RequestPoolService.java:257] Unable to stop AllocationFileLoaderService after failed start.
Java exception follows:
java.lang.IllegalStateException
at com.google.common.base.Preconditions.checkState(Preconditions.java:492)
at org.apache.impala.util.FileWatchService.stop(FileWatchService.java:136)
at org.apache.impala.util.RequestPoolService.stopInternal(RequestPoolService.java:281)
at org.apache.impala.util.RequestPoolService.start(RequestPoolService.java:255)
F0426 13:25:49.820109 12933 request-pool-service.cc:148] RuntimeException: org.apache.impala.yarn.server.resourcemanager.schedule$
CAUSED BY: AllocationConfigurationException: Could get past last queue placement rule without assigning
. Impalad exiting.

**************************************************************************************

*platform=CDP Private Cloud 7.1.5

What tasks can I do to solve this error?

Thanking this community for the support they can give me.

[#2]

No, values by default..

[#3]

Have you upgraded from CDH to CDP or it is a fresh installation?

Thanks

Megh

[#4]

it is a fresh installation.

[#5 · Accepted solution]

Okay, so here is my suggestion.

1. Check what is the type of scheduler in your YARN config
2. If it is Fair Scheduler, change it to Capacity Scheduler, restart the services and observe whether the error with Impala is gone.
3. In case it is Fair Scheduler and changing the scheduler is not something you want to do, then configure Queue placement policies as shown here, Restart the services and observe whether the errors in Impala have gone.

Thanks,

Megh

[#6]

1) Check what is the type of scheduler in your YARN config

     * By Default CDP PvC Base 7.x uses "Capacity Scheduler"

2) If it is Fair Scheduler, change it to Capacity Scheduler, restart the services and observe whether the error with Impala is gone.

     * did not apply

3) In case it is Fair Scheduler and changing the scheduler is not something you want to do, then configure Queue placement policies as shown here, Restart the services and observe whether the errors in Impala have gone.

        3.1) In all Data Nodes, in configuration apply this configuration

                (Queue placement policies):

                Impala Daemon Fair Scheduler Advanced Configuration Snippet (Safety Valve)

                Configuration Snippet (Safety Valve)

************************add this xml code===>

<?xml version="1.0"?>
<allocations>
<queue name="root">
<minResources>10000 mb,0vcores</minResources>
<maxResources>90000 mb,0vcores</maxResources>
<maxRunningApps>50</maxRunningApps>
<weight>2.0</weight>
<schedulingPolicy>fair</schedulingPolicy>
<queue name="default">
<aclSubmitApps>root</aclSubmitApps>
<minResources>5000 mb,0vcores</minResources>
</queue>
</queue>

<user name="root">
<maxRunningApps>30</maxRunningApps>
</user>
<userMaxAppsDefault>5</userMaxAppsDefault>

<queuePlacementPolicy>
<rule name="specified" />
<rule name="primaryGroup" create="false" />
<rule name="default" />
</queuePlacementPolicy>
</allocations>

************************add this xml code===>

Thank!!!  you very much for your support @vidanimegh