Pivotal Knowledge Base

Follow

GPMON Session stays idle after Disabling GPPERFMON

Environment

 Product  Version
 Pivotal Greenplum  4.3.8.x
 OS  RHEL 6.x

Symptom

gpperfmon is disabled (config gp_enable_gpperfmon=off across the cluster), but gpmon connection (gpmon was either querying or inserting data, and now the session is idling) still exists in each segment:

ps -ef |grep gpmon
[sdw6] gpadmin  337815 337561  0 13:07 ?        00:00:00 postgres: port 40000, gpmon auoedwi 172.28.8.250(13647) con4 seg8 idle                                                         
[sdw6] gpadmin  337817 337562  0 13:07 ?        00:00:00 postgres: port 40001, gpmon auoedwi 172.28.8.250(24053) con4 seg9 idle                                                         
[sdw6] gpadmin  337819 337557  0 13:07 ?        00:00:00 postgres: port 40002, gpmon auoedwi 172.28.8.250(65286) con4 seg10 idle                                                        
[sdw6] gpadmin  337821 337566  0 13:07 ?        00:00:00 postgres: port 40003, gpmon auoedwi 172.28.8.250(43131) con4 seg11 idle                                                        
[sdw6] gpadmin  337823 337569  0 13:07 ?        00:00:00 postgres: port 40004, gpmon auoedwi 172.28.8.250(33394) con4 seg12 idle                                                        
[sdw6] gpadmin  337825 337564  0 13:07 ?        00:00:00 postgres: port 40005, gpmon auoedwi 172.28.8.250(28368) con4 seg13 idle                                                        
[sdw6] gpadmin  337827 337571  0 13:07 ?        00:00:00 postgres: port 40006, gpmon auoedwi 172.28.8.250(41776) con4 seg14 idle                                                        
[sdw6] gpadmin  337829 337570  0 13:07 ?        00:00:00 postgres: port 40007, gpmon auoedwi 172.28.8.250(22826) con4 seg15 idle                                                        
[sdw7] gpadmin  337831 337576  0 13:07 ?        00:00:00 postgres: port 40000, gpmon auoedwi 172.28.8.250(45381) con4 seg16 idle                                                        
[sdw7] gpadmin  337833 337564  0 13:07 ?        00:00:00 postgres: port 40001, gpmon auoedwi 172.28.8.250(55810) con4 seg17 idle                                                        
[sdw7] gpadmin  337835 337566  0 13:07 ?        00:00:00 postgres: port 40002, gpmon auoedwi 172.28.8.250(3578) con4 seg18 idle                                                         
[sdw7] gpadmin  337837 337563  0 13:07 ?        00:00:00 postgres: port 40003, gpmon auoedwi 172.28.8.250(46330) con4 seg19 idle                                                        
[sdw7] gpadmin  337839 337568  0 13:07 ?        00:00:00 postgres: port 40004, gpmon auoedwi 172.28.8.250(58322) con4 seg20 idle                                                        
[sdw7] gpadmin  337841 337562  0 13:07 ?        00:00:00 postgres: port 40005, gpmon auoedwi 172.28.8.250(37715) con4 seg21 idle                                                        
[sdw7] gpadmin  337843 337571  0 13:07 ?        00:00:00 postgres: port 40006, gpmon auoedwi 172.28.8.250(11842) con4 seg22 idle                                                        
[sdw7] gpadmin  337845 337565  0 13:07 ?        00:00:00 postgres: port 40007, gpmon auoedwi 172.28.8.250(36830) con4 seg23 idle 

Resolution 

To solve this issue, kindly please do a stop and then a start instead of using gpstop -r (restart directly). 

Comments

Powered by Zendesk