You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barry Oglesby (JIRA)" <ji...@apache.org> on 2019/07/11 22:30:00 UTC
[jira] [Commented] (GEODE-6933) Gateway sender alert-threshold not
working
[ https://issues.apache.org/jira/browse/GEODE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883376#comment-16883376 ]
Barry Oglesby commented on GEODE-6933:
--------------------------------------
The AbstractGatewaySenderEventProcessor handleSuccessfulBatchDispatch is the only place the warning is logged. That method is only called in the case of a GatewaySenderEventCallbackDispatcher (which is the AsyncEventQueue dispatcher).
Its not called in AbstractGatewaySenderEventProcessor handleSuccessBatchAck which is the GatewaySenderEventRemoteDispatcher case. The GatewaySenderEventRemoteDispatcher is used by the GatewaySender or wan case.
Further, the alert-threshold is only supported:
- in the gateway-sender in the xsd
- in the create gateway-sender gfsh
So, its not even configurable on an AsyncEventQueue. If I hack AbstractGatewaySender and set alertThreshold > 0, I can see a warning in the AsyncEventQueue case:
{noformat}
[warn 2019/07/11 15:20:38.531 PDT <Event Processor for GatewaySender_AsyncEventQueue_db.0> tid=0x36] CREATE event for region=/data key=TradeKey[id=0] value=Trade[id=0; ...] was in the queue for 10124 milliseconds
{noformat}
AbstractGatewaySenderEventProcessor handleSuccessBatchAck should be changed to log the warning just like AbstractGatewaySenderEventProcessor handleSuccessBatchAck does.
And either AsyncEventQueue should be modified to support alert-threshold or the warning code should be removed from AbstractGatewaySenderEventProcessor handleSuccessfulBatchDispatch.
> Gateway sender alert-threshold not working
> ------------------------------------------
>
> Key: GEODE-6933
> URL: https://issues.apache.org/jira/browse/GEODE-6933
> Project: Geode
> Issue Type: Bug
> Components: wan
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Major
>
> When alert-threshold function is activated in gateway senders (set alert-threshold to non zero value),
> event is never raised, for entries which are in queue longer than alert-threshold value.
>
> Printout from logs:
> Monitor = GatewaySenderMXBeanMonitor descriptor = eventsExceedingAlertThreshold And value = 0
>
> It seams that reporting of events which exceed alert threshold (class AbstractGatewaySenderEventProcessor), is working only if dispatcher is instance of GatewaySenderEventCallbackDispatcher.
> With deeper analysis, I got to conclusion that for GatewaySender - dispatcher is instance of {color:#629755}GatewaySenderEventRemoteDispatcher.{color}
> {color:#ff0000}So this function is only working for {color}{color:#808080}AsyncEventQueue, for which dispatcher is instance of GatewaySenderEventCallbackDispatcher.{color}
>
> {color:#808080}The other problem is that _getEventsExceedingAlertThreshold() method of_ _GatewaySenderMBean is always returning hardcoded value (0)._{color}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)