Public bug reported:
When using the copy_from option, readers and writers can have different speeds
to respectively read and write.
A reader can timeout if the connection has been opened for too long without
getting any heartbeat.
This is happening if the writer is slower than the reader. A reader will have
to wait for the writer to process all the bits sent before
getting the next chunk. If this time to process the bits is too long the reader
will timeout.
Consequently, the writer should be able to control the size of the chunks that
needs to be read in order to be able to write fast enough.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1336167
Title:
Chunksize should be configurable when using copy_from
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
When using the copy_from option, readers and writers can have different
speeds to respectively read and write.
A reader can timeout if the connection has been opened for too long without
getting any heartbeat.
This is happening if the writer is slower than the reader. A reader will have
to wait for the writer to process all the bits sent before
getting the next chunk. If this time to process the bits is too long the
reader will timeout.
Consequently, the writer should be able to control the size of the chunks
that needs to be read in order to be able to write fast enough.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1336167/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
