No reason to prevent rediscovery for 10s by default
Signed-off-by: Erik Boasson <eb@ilities.com>
This commit is contained in:
parent
fa7999c5d8
commit
4447fb87ee
4 changed files with 4 additions and 4 deletions
|
@ -1349,7 +1349,7 @@ is therefore recommended to set it to at least several seconds.
|
|||
Valid values are finite durations with an explicit unit or the keyword
|
||||
'inf' for infinity. Recognised units: ns, us, ms, s, min, hr, day.
|
||||
|
||||
The default value is: "10s".
|
||||
The default value is: "0s".
|
||||
|
||||
|
||||
#### //CycloneDDS/Domain/Internal/RediscoveryBlacklistDuration[@enforce]
|
||||
|
|
|
@ -1113,7 +1113,7 @@ is therefore recommended to set it to at least several seconds.</p>
|
|||
|
||||
<p>Valid values are finite durations with an explicit unit or the keyword
|
||||
'inf' for infinity. Recognised units: ns, us, ms, s, min, hr,
|
||||
day.</p><p>The default value is: "10s".</p>""" ] ]
|
||||
day.</p><p>The default value is: "0s".</p>""" ] ]
|
||||
element RediscoveryBlacklistDuration {
|
||||
[ a:documentation [ xml:lang="en" """
|
||||
<p>This attribute controls whether the configured time during which
|
||||
|
|
|
@ -1475,7 +1475,7 @@ is therefore recommended to set it to at least several seconds.</p>
|
|||
|
||||
<p>Valid values are finite durations with an explicit unit or the keyword
|
||||
'inf' for infinity. Recognised units: ns, us, ms, s, min, hr,
|
||||
day.</p><p>The default value is: &quot;10s&quot;.</p></xs:documentation>
|
||||
day.</p><p>The default value is: &quot;0s&quot;.</p></xs:documentation>
|
||||
</xs:annotation>
|
||||
<xs:complexType>
|
||||
<xs:simpleContent>
|
||||
|
|
|
@ -728,7 +728,7 @@ static const struct cfgelem internal_cfgelems[] = {
|
|||
BLURB("<p>Do not use.</p>") },
|
||||
{ LEAF("SendAsync"), 1, "false", ABSOFF(xpack_send_async), 0, uf_boolean, 0, pf_boolean,
|
||||
BLURB("<p>This element controls whether the actual sending of packets occurs on the same thread that prepares them, or is done asynchronously by another thread.</p>") },
|
||||
{ LEAF_W_ATTRS("RediscoveryBlacklistDuration", rediscovery_blacklist_duration_attrs), 1, "10s", ABSOFF(prune_deleted_ppant.delay), 0, uf_duration_inf, 0, pf_duration,
|
||||
{ LEAF_W_ATTRS("RediscoveryBlacklistDuration", rediscovery_blacklist_duration_attrs), 1, "0s", ABSOFF(prune_deleted_ppant.delay), 0, uf_duration_inf, 0, pf_duration,
|
||||
BLURB("<p>This element controls for how long a remote participant that was previously deleted will remain on a blacklist to prevent rediscovery, giving the software on a node time to perform any cleanup actions it needs to do. To some extent this delay is required internally by DDSI2E, but in the default configuration with the 'enforce' attribute set to false, DDSI2E will reallow rediscovery as soon as it has cleared its internal administration. Setting it to too small a value may result in the entry being pruned from the blacklist before DDSI2E is ready, it is therefore recommended to set it to at least several seconds.</p>") },
|
||||
{ LEAF_W_ATTRS("MultipleReceiveThreads", multiple_recv_threads_attrs), 1, "default", ABSOFF(multiple_recv_threads), 0, uf_boolean_default, 0, pf_boolean_default,
|
||||
BLURB("<p>This element controls whether all traffic is handled by a single receive thread (false) or whether multiple receive threads may be used to improve latency (true). By default it is disabled on Windows because it appears that one cannot count on being able to send packets to oneself, which is necessary to stop the thread during shutdown. Currently multiple receive threads are only used for connectionless transport (e.g., UDP) and ManySocketsMode not set to single (the default).</p>") },
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue