[
https://issues.apache.org/jira/browse/PHOENIX-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana resolved PHOENIX-8004.
------------------------------------
Resolution: Fixed
> Use BlockingWaitStrategy for the replication-log Disruptor
> ----------------------------------------------------------
>
> Key: PHOENIX-8004
> URL: https://issues.apache.org/jira/browse/PHOENIX-8004
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Tanuj Khurana
> Assignee: Tanuj Khurana
> Priority: Major
>
> The ReplicationLogGroup Disruptor was created with YieldingWaitStrategy,
> which busy-spins/yields and pins a CPU core per HA group even when the ring
> buffer is idle. Switch to BlockingWaitStrategy, which parks the consumer when
> the ring is empty (0 CPU when idle). This matches HBase's own WAL Disruptor
> (FSHLog), which uses BlockingWaitStrategy because the HDFS append/sync work
> dwarfs any wakeup latency, so spinning makes no sense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
