[LOG4J2-2858] More flexible configuration of WaitStrategy of Disruptor

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.13.3
• Fix Version/s: 2.14.0
• Component/s: Configuration
• Assignee: Unassigned
• Reporter: Stepan Gorban
• Created: 28/May/20 16:07
• Updated: 11/Apr/22 07:55
• Resolved: 16/Jul/20 21:08

Description

I have realized that there is garbage generated from the following stack trace:

AbstractQueuedSynchronizer$Node java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter() 
long util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(long)
long com.lmax.disruptor.TimeoutBlockingWaitStrategy.waitFor(long, Sequence, Sequence, SequenceBarrier)
long com.lmax.disruptor.ProcessingSequenceBarrier.waitFor(long)
void com.lmax.disruptor.BatchEventProcessor.processEvents()
void com.lmax.disruptor.BatchEventProcessor.run()
void java.lang.Thread.run()

Thus, I would like to use some other wait strategy. However there are only few possibilities. I would prefer to use SleepingWaitStrategy with custom parameters. But there is no such option:

case "SLEEP":
return new SleepingWaitStrategy();
case "YIELD":
return new YieldingWaitStrategy();
case "BLOCK":
return new BlockingWaitStrategy();
case "BUSYSPIN":
return new BusySpinWaitStrategy();
case "TIMEOUT":
return new TimeoutBlockingWaitStrategy(timeoutMillis, TimeUnit.MILLISECONDS);
default:
return new TimeoutBlockingWaitStrategy(timeoutMillis, TimeUnit.MILLISECONDS);

 

The key goal is to log messages with weak requirements on logging latency, BUT in the JVM with low-latency code.

Issue Links

• is related to: LOG4J2-3472 Allow configuration of custom Disruptor WaitStrategy