Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 918714

Summary:	[RFE] Replication - make timeout for protocol shutdown configurable
Product:	Red Hat Enterprise Linux 7	Reporter:	Nathan Kinder <nkinder>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.0	CC:	jgalipea, mkubik, mreynolds, nhosoi
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.1.2-1.el7	Doc Type:	Enhancement
Doc Text:	Cause: The hard-coded replication protocol timeout was too long(20 minutes). Consequence: The server can appear to be hung. Change: The default timeout is now 2 minutes, and it can also be configured. Result: The replication protocol does not get stuck in a very long timeout, and/or timeouts when expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 10:49:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1038639, 1042855
Bug Blocks:

Description Nathan Kinder 2013-03-06 18:16:44 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/558

When attempting to "stop" the protocol, usually during a server shutdown, the timeout value is set to 20 minutes.  If replication is busy it can appear that the server is hung.  The default timeout should be not be 20 minutes, and it should be configurable.

Comment 1 Rich Megginson 2013-10-01 23:26:14 UTC

moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.

Comment 4 Sankar Ramalingam 2014-01-17 13:42:24 UTC

Build tested - 389-ds-base-1.3.1.6-14.el7.x86_64
Automation run date - 01/16

All test cases in mmrepl/accept for replica_timeout are passing. Hence, marking the bug as Verified.

Comment 5 Ludek Smid 2014-06-13 10:49:06 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.