IBP: HTTP pipelining is turned on by default for apt
Bug #1470468 reported by
Alexander Gordeev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Evgeny Konstantinov | ||
6.1.x |
Won't Fix
|
High
|
Fuel Documentation Team | ||
7.0.x |
Won't Fix
|
Undecided
|
Fuel Documentation Team | ||
8.0.x |
Won't Fix
|
Medium
|
Fuel Documentation Team | ||
Future |
Won't Fix
|
Undecided
|
Fuel Documentation Team | ||
Mitaka |
Won't Fix
|
High
|
Evgeny Konstantinov |
Bug Description
HTTP pipelining is broken due to a bug in recent gateway firmware https:/
It causes to slow down http connection speed extremely (eg. to 12kbps even on 300M uplink), thus making impossible:
1) to build ubuntu image and to fit within 1h timeout (it could be worked around by creating local mirror via fuel-createmirror script)
2) to deploy cluster. As granular tasks are using apt tools too. They were failed by timeout too.
In order to disable pipelining, we should add the following settings to apt.conf.d
echo "Acquire:
echo "Acquire:
Changed in fuel: | |
milestone: | none → 7.0 |
Changed in fuel: | |
assignee: | Fuel provisioning team (fuel-provisioning) → Aleksandr Gordeev (a-gordeev) |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → New |
no longer affects: | fuel/7.0.x |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: docs |
tags: | added: area-docs |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
status: | Confirmed → New |
Changed in fuel: | |
status: | New → Confirmed |
tags: | removed: need-info |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
according to https:/ /en.wikipedia. org/wiki/ HTTP_pipelining
> The pipelining of requests results in a dramatic improvement in the loading times of HTML pages, especially over high latency connections such as satellite Internet connections. The speedup is less apparent on broadband connections, as the limitation of HTTP 1.1 still applies
> Out of all the major browsers, only Opera based on Presto layout engine had a fully working implementation that was enabled by default. In all other browsers HTTP pipelining is disabled or not implemented.
It sounds like, HTTP pipelining could be disabled without any harm as nobody uses it actually. Only small amount of HTTP related software has enabled it by default.