Member since
01-12-2017
18
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2940 | 01-25-2017 11:57 AM |
07-31-2020
05:37 AM
1 Kudo
Thanks, Restart also worked for me
... View more
01-26-2017
08:16 AM
I've set-up hive.prewarm.enabled=true and it did not improve the slow latency to start and initialize executors. It still takes about 15seconds to initialize things. Any idea ?
... View more
01-25-2017
12:03 PM
You can search for 'heap size' in Service Monitor and Host Monitor's configuration page. Make sure they are restarted after you save your configuration changes.
... View more
01-25-2017
11:57 AM
I am asking if your Spark service is Spark2 or not? Cloudera Manager is not supporting directly configuring Hive to depend on Spark2 yet. So you might want to try using 'Spark1' and see.
... View more
01-12-2017
03:16 PM
@saranvisaThis health check result indicates that NodeManager is not getting enough heap space compared to its workload. Typically when workload grows in the cluster and thus the java daemon needs more heap, you need to give more heap to the Role. You could: 1. Increase the heap given to Node Manager through Node Manager's configuration page.('Java Heap Size of NodeManager in Bytes') 2. Alternatively, though not recommended, you could tune the threshold you found to tolerate higher GC ratio for Node Manager. I would recommend you go to the specific Node Manager's role instance page in Cloudera Manager, browse through the charts available for Node Manager, there would be a chart named 'JVM heap memory usage' telling you the heap consumption of the particular Node Manager. Then you can have a better idea of how much memory the Role is using and potentially increase the heap given to it to a higher value.
... View more