Author: jxue
Date: Sun May 31 05:18:39 2026
New Revision: 1934806
Log:
Site checkin for project Apache Helix :: Website
Modified:
helix/site-content/2.0.0-docs/releasenotes/release-2.0.0.html
Modified: helix/site-content/2.0.0-docs/releasenotes/release-2.0.0.html
==============================================================================
--- helix/site-content/2.0.0-docs/releasenotes/release-2.0.0.html Sun May
31 05:13:21 2026 (r1934805)
+++ helix/site-content/2.0.0-docs/releasenotes/release-2.0.0.html Sun May
31 05:18:39 2026 (r1934806)
@@ -154,12 +154,22 @@
<h3 id="Major_Features">Major Features</h3>
<section>
<h4 id="Helix_Gateway_Service">Helix Gateway Service</h4>
- <p>The Helix Gateway service is a new gRPC-based communication mechanism
that replaces the traditional state transition message approach for participant
communication. Key benefits include:</p>
+ <p>The Helix Gateway service is a new gRPC-based communication mechanism
that replaces the traditional state transition message approach for participant
communication. Instead of the controller pushing state transition messages to
participants, the Gateway service enables a pull-based model where participants
actively report their current state.</p>
+ <p>How it works:</p>
<ul>
- <li>Improved Performance: Participants report their shards' current state
directly to the gateway, eliminating the need for state transition
messages</li>
+ <li>Participants establish a bidirectional gRPC stream to the Gateway
service and report their shard states on connection and when state changes
occur</li>
+ <li>The Gateway service processes participant state updates and sends back
state change requests (such as ADD_SHARD, DELETE_SHARD, CHANGE_ROLE) when
needed</li>
+ <li>The Gateway service maintains a local cache (GatewayCurrentStateCache)
of all participant states for efficient state tracking</li>
+ <li>The controller queries participant states through the Gateway rather
than sending direct messages, reducing network overhead and message queue
contention</li>
+ </ul>
+ </section>
+ <section>
+ <h4 id="Key_benefits">Key benefits</h4>
+ <ul>
+ <li>Improved Performance: Eliminates the need for persistent message
connections and reduces message queue contention</li>
<li>Simplified Architecture: Uses poll-mode channel for efficient state
synchronization</li>
- <li>Better Scalability: Gateway service handles participant state updates
with improved efficiency</li>
- <li>Enhanced Observability: Better tracking of participant state through
dedicated cache (GatewayCurrentStateCache)</li>
+ <li>Better Scalability: Supports larger clusters with reduced message
traffic</li>
+ <li>Enhanced Observability: Dedicated cache provides clearer insight into
cluster state</li>
</ul>
</section>
<section>
