Noisy logging of 'is-executing': true checks against long running operations

[sertugkaya]

Let's say, with 3 nodes, submit 450 callables to a ExecutorService with default config. These callables have 30 sec sleep, so after they are submitted and future.get is called, there is excessive logging of:

WARNING: [192.168.2.233]:5701 [dev] [3.5.5] Asking if operation execution has been started: com.hazelcast.spi.impl.operationservice.impl.IsStillRunningService$InvokeIsStillRunningOperationRunnable@47d30050
Jun 15, 2016 3:19:21 PM com.hazelcast.spi.impl.operationservice.impl.Invocation
WARNING: [192.168.2.233]:5701 [dev] [3.5.5] 'is-executing': true -> Invocation{ serviceName='hz:impl:executorService', op=com.hazelcast.executor.impl.operations.MemberCallableTaskOperation{identityHash=363968240, serviceName='null', partitionId=-1, callId=298, invocationTime=1465992932390, waitTimeout=-1, callTimeout=60000}, partitionId=-1, replicaIndex=0, tryCount=250, tryPauseMillis=500, invokeCount=1, callTimeout=60000, target=Address[192.168.2.233]:5703, backupsExpected=0, backupsCompleted=0}
Jun 15, 2016 3:19:22 PM com.hazelcast.spi.OperationService

In some cases, it causes hundred MB of logs to be created. This logging noise can be reduced to debug level since it basically saying "everything is alright".

[mdogan]

@sertugkaya: this mechanism is completely changed in 3.7. Are we going to have any other 3.6.x release?

[sertugkaya]

@mdogan In case we have one :) we have people complaining about this so I wanted to document it here.