You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Default to num_owners=2 when the persistent-user-sessions feature is disabled #40472
In the documentation we advised users who use volatile sessions, i.e. persistent-user-sessions feature is disabled, to explicitly configure num_owners > 1 to prevent data loss. However, by default num_owners=1 and changing this value requires users to provide a custom Infinispan .xml file.
Instead, we should automatically configure num_owners = 2 if the user has not explicitly configured this value and if no shared persistence store exists. This will prevent users accidentally providing an unsafe configuration with volatile sessions.
changed the title [-]Prevent num_owners=1 when the persistent-user-sessions feature is disabled[/-][+]Default to num_owners=2 when the persistent-user-sessions feature is disabled[/+]on Jun 13, 2025
@ryanemerson, @mhajas, @pruivo - I would like to see this change backported to 26.2 as we're about to support RHBK 26.2 for another 10 months, and not everyone has migrated yet.
Happy to hear your thoughts in favor or against this suggestion, or if you are neutral.
Adding the backport label while we discuss this one.
I think it makes sense from a RHBK perspective. It will result in a change of behaviour for upstream 26.2 users, so if anybody has (incorrectly) relied on num_owners=1, they might be in for a surprise with the next patch release.
Activity
[-]Prevent num_owners=1 when the persistent-user-sessions feature is disabled[/-][+]Default to num_owners=2 when the persistent-user-sessions feature is disabled[/+]Default to num_owners=2 when the persistent-user-sessions feature is …
Default to num_owners=2 when the persistent-user-sessions feature is …
ahus1 commentedon Jun 16, 2025
@ryanemerson, @mhajas, @pruivo - I would like to see this change backported to 26.2 as we're about to support RHBK 26.2 for another 10 months, and not everyone has migrated yet.
Happy to hear your thoughts in favor or against this suggestion, or if you are neutral.
Adding the backport label while we discuss this one.
Similar to #40483 which is a follow-up.
Default to num_owners=2 when the persistent-user-sessions feature is …
pruivo commentedon Jun 16, 2025
@ahus1 +1
ryanemerson commentedon Jun 16, 2025
+ .5 🙂
I think it makes sense from a RHBK perspective. It will result in a change of behaviour for upstream 26.2 users, so if anybody has (incorrectly) relied on num_owners=1, they might be in for a surprise with the next patch release.
ahus1 commentedon Jun 17, 2025
@ryanemerson - as discussed in our team meeting yesterday, please create a backport. Thanks!
Default to num_owners=2 when the persistent-user-sessions feature is …
Default to num_owners=2 when the persistent-user-sessions feature is …
Default to num_owners=2 when the persistent-user-sessions feature is …