From ebb10d445ea1550bbbf23f8da4b0a65b382dc226 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EB=B0=95=EC=A2=85=ED=95=98?= Date: Sun, 7 Dec 2025 22:56:26 +0900 Subject: [PATCH 1/4] Add readable names for mapSendOptions in cluster-howto --- webapps/docs/cluster-howto.xml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/webapps/docs/cluster-howto.xml b/webapps/docs/cluster-howto.xml index cc753422e19f..ec0013837188 100644 --- a/webapps/docs/cluster-howto.xml +++ b/webapps/docs/cluster-howto.xml @@ -238,6 +238,19 @@ should be completed:

replication yields shorter request times, and synchronous replication guarantees the session to be replicated before the request returns.

+

+ In addition to channelSendOptions, the backup manager's + mapSendOptions attribute uses the same send-option flag + mechanism. This attribute controls how the replicated map within the + BackupManager sends its messages during session backup + operations. + + Just like channelSendOptions, the value may be specified + either as an integer bitmask (e.g. 6) or using the + human-readable option names (e.g. "sync,use_ack"), with + multiple names separated by commas. The same option names and flag + combinations apply to both attributes. +

From a9dccbfd82cf09393c3b181e1a8432a7c51384bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EB=B0=95=EC=A2=85=ED=95=98?= Date: Sun, 7 Dec 2025 22:56:39 +0900 Subject: [PATCH 2/4] Add readable names for mapSendOptions in cluster-manager --- webapps/docs/config/cluster-manager.xml | 43 +++++++++++++++++++++---- 1 file changed, 37 insertions(+), 6 deletions(-) diff --git a/webapps/docs/config/cluster-manager.xml b/webapps/docs/config/cluster-manager.xml index 6197baa47a9f..fd08e1049b0a 100644 --- a/webapps/docs/config/cluster-manager.xml +++ b/webapps/docs/config/cluster-manager.xml @@ -227,12 +227,43 @@ - The backup manager uses a replicated map, this map is sending and - receiving messages. You can setup the flag for how this map is sending - messages, the default value is 6(synchronous).
- Note that if you use asynchronous messaging it is possible for update - messages for a session to be processed by the receiving node in a - different order to the order in which they were sent. +

+ The backup manager uses a replicated map. This map sends and receives + messages internally. You can configure the flag that controls how this + map sends messages. The default value is 6 (synchronous).
+ Note that if you use asynchronous messaging it is possible for update + messages for a session to be processed by the receiving node in a + different order to the order in which they were sent. +

+ +

+ The value may be specified either as an integer flag or using the + human-readable option names. These names are translated to their integer + values on startup. +

+ +

Some of the values are:
+ Channel.SEND_OPTIONS_SYNCHRONIZED_ACK = 0x0004
+ Channel.SEND_OPTIONS_ASYNCHRONOUS = 0x0008
+ Channel.SEND_OPTIONS_USE_ACK = 0x0002
+ Therefore, the default 6 corresponds to + sync,use_ack (4 + 2). +

+ +

+ Examples:
+ mapSendOptions="6" / mapSendOptions="sync,use_ack"
+ mapSendOptions="8" / mapSendOptions="async"
+ mapSendOptions="2" / mapSendOptions="use_ack" +

+ +

+ The valid option names are the same as for channelSendOptions: + "asynchronous" (alias "async"), "byte_message" (alias "byte"), + "multicast", "secure", "synchronized_ack" (alias "sync"), "udp", + "use_ack". Multiple names may be comma-separated, e.g. + "async,multicast". +

The maximum number of active sessions that will be created by this From d0c322d87bb2888b37c479269b6b56b941b09b30 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EB=B0=95=EC=A2=85=ED=95=98?= Date: Sun, 7 Dec 2025 22:56:47 +0900 Subject: [PATCH 3/4] Add readable names for mapSendOptions in cluster-valve --- webapps/docs/config/cluster-valve.xml | 32 ++++++++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) diff --git a/webapps/docs/config/cluster-valve.xml b/webapps/docs/config/cluster-valve.xml index c353053afb6f..f1998365a727 100644 --- a/webapps/docs/config/cluster-valve.xml +++ b/webapps/docs/config/cluster-valve.xml @@ -131,7 +131,37 @@ map sends messages. The default value is 6 (synchronous). Note that if you use asynchronous messaging it is possible for update messages to be processed by the receiving node in a different order to - the order in which they were sent.

+ the order in which they were sent. +

+ +

+ The value may be specified either as an integer flag or using the + human-readable option names. These names are translated to their integer + values on startup. +

+ +

Some of the values are:
+ Channel.SEND_OPTIONS_SYNCHRONIZED_ACK = 0x0004
+ Channel.SEND_OPTIONS_ASYNCHRONOUS = 0x0008
+ Channel.SEND_OPTIONS_USE_ACK = 0x0002
+ Therefore, the default 6 corresponds to + sync,use_ack (4 + 2). +

+ +

+ Examples:
+ mapSendOptions="6" / mapSendOptions="sync,use_ack"
+ mapSendOptions="8" / mapSendOptions="async"
+ mapSendOptions="2" / mapSendOptions="use_ack" +

+ +

+ The valid option names are the same as for channelSendOptions: + "asynchronous" (alias "async"), "byte_message" (alias "byte"), + "multicast", "secure", "synchronized_ack" (alias "sync"), "udp", + "use_ack". Multiple names may be comma-separated, e.g. + "async,multicast". +

Default false. Flag to determine whether each request needs to be From ba28568f01e95c9ffc7926108998361ae38cc9b4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EB=B0=95=EC=A2=85=ED=95=98?= Date: Mon, 29 Dec 2025 15:50:44 +0900 Subject: [PATCH 4/4] Fix xml format to fit the convention --- webapps/docs/cluster-howto.xml | 1 - webapps/docs/config/cluster-manager.xml | 3 ++- webapps/docs/config/cluster-valve.xml | 23 +++++++++++++---------- 3 files changed, 15 insertions(+), 12 deletions(-) diff --git a/webapps/docs/cluster-howto.xml b/webapps/docs/cluster-howto.xml index ec0013837188..cbab6fddc798 100644 --- a/webapps/docs/cluster-howto.xml +++ b/webapps/docs/cluster-howto.xml @@ -244,7 +244,6 @@ should be completed:

mechanism. This attribute controls how the replicated map within the BackupManager sends its messages during session backup operations. - Just like channelSendOptions, the value may be specified either as an integer bitmask (e.g. 6) or using the human-readable option names (e.g. "sync,use_ack"), with diff --git a/webapps/docs/config/cluster-manager.xml b/webapps/docs/config/cluster-manager.xml index fd08e1049b0a..dc9279363295 100644 --- a/webapps/docs/config/cluster-manager.xml +++ b/webapps/docs/config/cluster-manager.xml @@ -252,7 +252,8 @@

Examples:
- mapSendOptions="6" / mapSendOptions="sync,use_ack"
+ mapSendOptions="6" / + mapSendOptions="sync,use_ack"
mapSendOptions="8" / mapSendOptions="async"
mapSendOptions="2" / mapSendOptions="use_ack"

diff --git a/webapps/docs/config/cluster-valve.xml b/webapps/docs/config/cluster-valve.xml index f1998365a727..2cdf68d40ae7 100644 --- a/webapps/docs/config/cluster-valve.xml +++ b/webapps/docs/config/cluster-valve.xml @@ -136,8 +136,8 @@

The value may be specified either as an integer flag or using the - human-readable option names. These names are translated to their integer - values on startup. + human-readable option names. These names are translated to their + integer values on startup.

Some of the values are:
@@ -150,17 +150,20 @@

Examples:
- mapSendOptions="6" / mapSendOptions="sync,use_ack"
- mapSendOptions="8" / mapSendOptions="async"
- mapSendOptions="2" / mapSendOptions="use_ack" + mapSendOptions="6" / + mapSendOptions="sync,use_ack"
+ mapSendOptions="8" / + mapSendOptions="async"
+ mapSendOptions="2" / + mapSendOptions="use_ack"

- The valid option names are the same as for channelSendOptions: - "asynchronous" (alias "async"), "byte_message" (alias "byte"), - "multicast", "secure", "synchronized_ack" (alias "sync"), "udp", - "use_ack". Multiple names may be comma-separated, e.g. - "async,multicast". + The valid option names are the same as for + channelSendOptions: "asynchronous" (alias "async"), + "byte_message" (alias "byte"), "multicast", "secure", + "synchronized_ack" (alias "sync"), "udp", "use_ack". Multiple names + may be comma-separated, e.g. "async,multicast".