CDH Hiveserver2 abnormal output

this link:

http://blog.csdn.net/gklifg/article/details/50418109、http://blog.csdn.net/levy_cui/article/details/53992402、http://blog.csdn.net/lulynn/article/ Details / 46455097。

In the process of using the CDH cluster, the problem is that Hiveserver2 has just started and the client has abnormally terminated after visiting the client.

1. Process Analysis:

See the above three blogs, and use JSTAT to monitor. The following prompt will appear:

ced329a82403658246d9cd6850a17f67

When the Hiveserver2 red box was killed;

During CDH monitoring, this is called an Outefmemory:

807f61d267218162b54b6644c95a5b19

add7cc1f12d31e7d904b05dfc0b65b27

2. Temporarily resolved:

The prompt appears here, indicating that the memory is not enough, the memory is increasing, and the tuning content is as follows:

f51fd4f7690862b006c43ec75e505e10

The initial configuration is as follows:

6be80419724a2f0c707997b2284a3e6a

Currently use JSTAT Monitor and you can find:

340e0f8aac7d5ac1ac13be5232e14c8d

5ce6491df7cc16da2a455a1dcd758a93

99936a2ba6412fb846532ec6923624ea

f9baea19f7156f359cb33cd7c8320495

d6d0a5dd880151b372e11e6b9cb66668

84db1b8b5fb9c183f973b85fc6c458aa

You can see from the data above:

1. The memory will be swapped between S0 and S1. When Hiveserver2 exits for the first time, it finds that S0 and S1 are 100%. At the same time, full GC is executed multiple times to cause memory overflow;

2. When the parameters are modified, the new generation GC is not often found. After each YGC, the utilization share in the E region will decrease;

3. Increasing the area of ​​occupation. When full GC occurs, the O region can be cleared, so the fraction will decrease;

Share, grow, be happy

Popular and down to earth

Please enter the blog address: http://blog.csdn.net/fansy1990

Leave a Comment