[
https://issues.apache.org/jira/browse/IGNITE-25612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-25612:
-----------------------------------------
Description:
It seems to me that the following diagnostic message is not enough to debug an
issue related to the long processing of watch events:
{noformat}
Watch event processing has been too long [duration=10026,
keys=[zone.assignments.pending.20_part_0,
zone.pending.change.trigger.20_part_0]]{noformat}
This is a tricky part to find out what the listener is, especially when there
are more than one listener.
was:It seems to me that the following diagnostic message is not enough to
debug an issue related to long processing watch events:
> Improve diagnostic message related to watch event processing
> ------------------------------------------------------------
>
> Key: IGNITE-25612
> URL: https://issues.apache.org/jira/browse/IGNITE-25612
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> It seems to me that the following diagnostic message is not enough to debug
> an issue related to the long processing of watch events:
> {noformat}
> Watch event processing has been too long [duration=10026,
> keys=[zone.assignments.pending.20_part_0,
> zone.pending.change.trigger.20_part_0]]{noformat}
> This is a tricky part to find out what the listener is, especially when there
> are more than one listener.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
