Bug 1329410

Summary: Consider backporting 'crypto/aes: dedicated asm version of AES-GCM' to go 1.4
Product: Red Hat Enterprise Linux 7 Reporter: Andy Goldstein <agoldste>
Component: golangAssignee: Jakub Čajka <jcajka>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: ccoleman, eparis
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 13:04:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Andy Goldstein 2016-04-21 20:42:48 UTC 
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?