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.
Clones were seen to be taking a *really* long time. When I strace git (git-remote-https as it ends up being) I saw
---
$ git clone https://git.openstack.org/openstack-infra/system-config
...
4606 1435711642.024680 recvfrom(3, "\27\3\1\0 ", 5, 0, NULL, NULL) = 5
4606 1435711642.024715 recvfrom(3, "H\325\v>8\236A\277;\250K\365\33$W\1\302,M\23\\\ro\212%\321\335\6\357T\326\365", 32, 0, NULL, NULL) = 32
4606 1435711642.024791 select(0, [], [], [], {0, 50000}) = 0 (Timeout)
4606 1435711642.075059 poll([{fd=3, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 1 ([{fd=3, revents=POLLIN|POLLRDNORM}])
4606 1435711642.075166 recvfrom(3, "\27\3\1\0`", 5, 0, NULL, NULL) = 5
4606 1435711642.075210 recvfrom(3, "=\232\353\276@@\6\2\221wX\225\30\262\221\204\361\251M)\244\3602;\354\3674S\2776\233&"..., 96, 0, NULL, NULL) = 96
4606 1435711642.075306 poll([{fd=3, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 1 ([{fd=3, revents=POLLIN|POLLRDNORM}])
4606 1435711642.075346 recvfrom(3, "\27\3\1\0 ", 5, 0, NULL, NULL) = 5
4606 1435711642.075379 recvfrom(3, "\370\300\\\373\250N\375\30n]\205\371\16\372L\373\36;]W\237L\214\364\325\374\234\301^\237\31\5", 32, 0, NULL, NULL) = 32
4606 1435711642.075437 select(0, [], [], [], {0, 50000}) = 0 (Timeout)
---
I didn't wait for it to finish because apparently it ends up taking about 40 minutes.
Comparing this to a "bare" curl call for the same thing, i.e.
---
$ curl -o /dev/null -H 'Pragma: no-cache'-v https://git.openstack.org/openstack-infra/system-config/info/refs?service=git-upload-pack
---
it goes *way* faster, a few seconds. The strace there looks *almost* the same, but the telling difference is the lack of select() calls
---
4679 1435711687.733287 recvfrom(3, "\27\3\1\0 ", 5, 0, NULL, NULL) = 5
4679 1435711687.733319 recvfrom(3, "<~\t$D+\353\245\341\223\303x\374\232\343+aMd\363\200|\307R\3m\211,i\22\336\\", 32, 0, NULL, NULL) = 32
4679 1435711687.733379 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
4679 1435711687.733427 poll([{fd=3, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 1 ([{fd=3, revents=POLLIN|POLLRDNORM}])
4679 1435711687.733459 poll([{fd=3, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 1 ([{fd=3, revents=POLLIN|POLLRDNORM}])
4679 1435711687.733493 recvfrom(3, "\27\3\1\0 ", 5, 0, NULL, NULL) = 5
4679 1435711687.733524 recvfrom(3, "\275\20\200[\225\232\245\374n\24)\361\20\312\204\375\377T\227\220\315\\\344\3211\344^\251\266I\216\237", 32, 0, NULL, NULL) = 32
4679 1435711687.733579 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...}) = 0
4679 1435711687.733627 poll([{fd=3, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 1000) = 1 ([{fd=3, revents=POLLIN|POLLRDNORM}])
4679 1435711687.733659 poll([{fd=3, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 1 ([{fd=3, revents=POLLIN|POLLRDNORM}])
---
It was also noticed that 1.8 git doesn't do this. So I went digging through git to see what might have changed in this respect. I found [1] (Use curl_multi_fdset to select on curl fds instead of just sleeping) which seemed to describe the exact issue. So I applied this to a local build and things seem to work much better, the clone happens as quickly as with git://
This is a small change but it makes a big difference in clone time over https, so I think it should be considered.
Will attach patch & packages I built for testing if interested
---
[root@cloud-server-01 test]# yum info git
Installed Packages
Name : git
Arch : x86_64
Version : 1.7.1
Release : 3.el6_4.1
Size : 15 M
Repo : installed
From repo : base
---
[1] https://git.kernel.org/cgit/git/git.git/commit/?id=6f9dd67ffea3e86276a73e522ce1186a99bbe65d
(In reply to pstodulk from comment #5)
> Is it suitable for z-stream? Otherwise it could be fixed in rhel-6.8.
yeah, i'm not sure; I guess it depends if anyone else notices. This might be due to a combination of the upstream repo (15200 refs, which might be a lot, I'm not sure ... this comes from gerrit reviews in the repo) and recent changes in the upstream git setup which maybe doesn't help.
I think you can probably switch to git:// if your remote supports it, and you're not behind a firewall, etc.
Just to convince myself a little bit more on this, I ran the openstack CI job that was failing with the modified packages via [1] and, after about 10 runs it has passed them all.
[1] https://review.openstack.org/#/c/198177/
Awesome job Ian. I applied your patchset locally and also seen the performance improvement. Thanks for working on this while I was lounging on vacation.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0640.html