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.
Description of problem: etcd is unable to add a new member to the cluster when its database is large (~700MB) when compiled with go 1.4.2.
Version-Release number of selected component (if applicable): etcd 2.2.5 + golang 1.4.2.
How reproducible: 100%
Steps to Reproduce:
1. Start up the first member in an etcd cluster with a large database
2. Try to add a second member
Actual results: i/o timeout errors in the first member, EOF errors in the second member trying to sync the database snapshot
Expected results: no errors
Additional info:
I cherry-picked https://github.com/golang/go/commit/50e657fb and https://github.com/golang/go/commit/efeeee3 to go1.4.2, built go, built etcd, and reran my test, and it appears to have solved the problem. I didn't run exhaustive or extensive tests; it's possible these patches are not sufficient, but they certainly make a significant improvement.
Please contact me for where to get the 700MB database and for steps to reproduce.
Would back porting these patches (and possibly others, if necessary) be a possibility to go 1.4.2?