-
Notifications
You must be signed in to change notification settings - Fork 103
Issue 6301 - Fix long delay when setting replication agreement with dsconf #6303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…dsconf Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: 389ds#6301 Reviewed by: ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good except a minor point
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as well
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
…dsconf (#6303) Bug Description: When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI. Fix Description: The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after. Fixes: #6301 Reviewed by: @progier389 @tbordaz (Thank you!)
|
a9cbacd..2cf519d 389-ds-base-3.0 -> 389-ds-base-3.0 |
Bug Description:
When creating a replication agreement using dsconf, the command line would get stuck for approximately 65 seconds. This delay did not occur when creating and initializing the agreement through the WebUI.
Fix Description:
The fix implements an "atomic" approach by performing the initialization at the point of agreement creation entry, rather than as a separate step immediately after.
Fixes: #6301
Reviewed by: ?