Bug 163681
Summary: | asyncore.poll3 runs longer than timeout under heavy io load | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Andre Schubert <andre> |
Component: | python | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-06 21:13:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andre Schubert
2005-07-20 08:53:05 UTC
Sorry it took so long to get to this bug report. Can you please attach an strace of the process while it's under heavy I/O and poll3 fails? I'd be curious what lower-level system call it uses. Sorry too for the late answer. I think we haved solved this problem. After several weeks of testing we have rewritten our script which collects the informations asyncronously. The hangs were caused by the underlying write to disk, which is called directly after some data have arrived. The new script first collects all the data, and after that all the data is written completely out to the disk. After we have changed to this new implementation, we never saw a hang in a poll3 cycle. Sorry for the false alarm. |