disableOverrideElasticsearchClusterServiceLogger

General
, , , , , ,
1

In the list of Resolved Issues for Reporting in both 8.8.4 and 23.1 it lists the following information

After update, system slowness was seen during startup. This was traced to the the behavior of logger “org.elasticsearch.cluster.service.ClusterService” being changed to log all entries. Disabling it or resetting it to “Error” still resulted in DEBUG and TRACE entries in the log. To resolve this, the logging has been made configurable with the setting “disableOverrideElasticsearchClusterServiceLogger”. The default value is false.

My question is where is this setting? I have a system running 23.1.2 and cannot find this setting any where.

Thanks
Craig

2

I’ve raised incident INC-B22156 for this as I have found no information about it and its causing quota issues for our logging platform.

3

@CraigA52

Add below setting to your prconfig to disable the cluster service logging (which is enabled by default)

4

@PhilipShannon Thanks for this, can this be applied as a DSS as well? Where is the documentation for this?

Thanks
Craig

5

@CraigA52 I think it should work as DSS too, my guess for the Owning Ruleset = Pega-SearchEngine

I am not sure why this hasn’t been documented yet, will try to get more details or at least attempt to get it added to the official documentation

6

@PhilipShannon I tried adding as DSS but initially didn’t work. Then as I got information back from my incident I was told it had to be prconfig and that the log category should also exist.

So I added the log category as well but still didn’t work.

With it being a prconfig setting I added the DSS prconfig/indexing/distributed/disableOverrideElasticsearchClusterServiceLogger/default under Pega-Engine and this has worked.

Thanks
Craig

7

@CraigA52 Thanks for posting back here with what setting works, Craig.