Bug 1329410 - Consider backporting 'crypto/aes: dedicated asm version of AES-GCM' to go 1.4
Summary: Consider backporting 'crypto/aes: dedicated asm version of AES-GCM' to go 1.4
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: golang
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Čajka
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 20:42 UTC by Andy Goldstein
Modified: 2016-05-19 13:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 13:04:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

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?


Note You need to log in before you can comment on or make changes to this bug.