This is an automated email from the ASF dual-hosted git repository.

fanningpj pushed a commit to branch 1.3.x
in repository https://gitbox.apache.org/repos/asf/pekko.git


The following commit(s) were added to refs/heads/1.3.x by this push:
     new 538641fbb4 update doc for write-response-global-order (#2437) (#2438)
538641fbb4 is described below

commit 538641fbb44a9b0d84806f1dda8b64e39ded27df
Author: PJ Fanning <[email protected]>
AuthorDate: Fri Nov 7 18:50:03 2025 +0100

    update doc for write-response-global-order (#2437) (#2438)
---
 persistence/src/main/resources/reference.conf | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/persistence/src/main/resources/reference.conf 
b/persistence/src/main/resources/reference.conf
index e3f3694267..8c7bbcd559 100644
--- a/persistence/src/main/resources/reference.conf
+++ b/persistence/src/main/resources/reference.conf
@@ -155,15 +155,19 @@ pekko.persistence {
       # Controls whether the journal plugin sends back write responses in the 
same order
       # as it received requests.
       #
-      # Originally Akka-Persistence implementation rearranged responses to 
match the request order.
-      # But this feature wasn't guaranteed by the Akka's test suite, and 
nothing in Akka itself relied on it.
+      # Originally, Akka and Pekko Persistence implementations rearranged 
responses to match the
+      # request order. But this feature wasn't guaranteed by the test suite, 
and nothing in the
+      # internals relied on it.
       #
       # As this ordering is global, slow write requests for some entities can 
stall writes for all,
       # which can cause latency issues under load.
       #
-      # The old behaviour is still enabled by default ("on"). After more 
testing on existing applications,
-      # the default might be switched to "off", and eventually this option 
might be removed altogeter, leaving
-      # "off" the only behaviour available.
+      # When this setting is "off", the journal plugin is allowed to send back 
write responses
+      # in any order. This can improve throughput and reduce latency under 
load.
+      # When using "off", changes to the dispatcher configuration of the 
journal plugin
+      # can lead to an increased number of out-of-order responses.
+      #
+      # The old behavior is still enabled by default ("on").
       write-response-global-order = on
     }
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to