Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.7.0
-
None
-
Severity 3 - Minor
-
Description
Issue Summary
Many topic service threads busy deduplicating the queue:
"hz.hazelcast.event-1" #130 daemon prio=5 os_prio=0 tid=0x00007efea052d000 nid=0x3596 runnable [0x00007efe92c3a000] java.lang.Thread.State: RUNNABLE at java.util.concurrent.LinkedBlockingQueue$LBQSpliterator.tryAdvance(LinkedBlockingQueue.java:950) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:499) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:486) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230) at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:516) at com.atlassian.stash.internal.topic.HazelcastTopicService$DefaultTopic.lambda$register$3(HazelcastTopicService.java:384) at com.atlassian.stash.internal.topic.HazelcastTopicService$DefaultTopic$$Lambda$708/1556634796.onMessage(Unknown Source) at com.hazelcast.topic.impl.TopicService.dispatchEvent(TopicService.java:136) at com.hazelcast.spi.impl.eventservice.impl.EventProcessor.process(EventProcessor.java:61) at com.hazelcast.spi.impl.eventservice.impl.RemoteEventProcessor.run(RemoteEventProcessor.java:47) at com.hazelcast.util.executor.StripedExecutor$Worker.process(StripedExecutor.java:226) at com.hazelcast.util.executor.StripedExecutor$Worker.run(StripedExecutor.java:209)
Workaround
Currently there is no known workaround for this behaviour. A workaround will be added here when available
Attachments
Issue Links
- is related to
-
BSERV-12025 Optimise Topic Service event deduplication
- Closed
- relates to
-
BBSDEV-21037 Loading...