Bug 762134 (GLUSTER-402)
| Summary: | [ 3.0.0pre1 ] siege aborts when run over Apache loaded via booster | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Anush Shetty <anush> |
| Component: | booster | Assignee: | Shehjar Tikoo <shehjart> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | gluster-bugs, raghavendra, vijay |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 762118 | ||
I was not able to reproduce the bug with latest codebase from master. Though I had observed this bug some time back, with latest code this is not reproducible. |
I copied /usr and ran siege on the mount point. Siege aborted after a while. This happens only when apache is loaded via booster. warning: socket: 1105209664 select timed out: Connection timed out done. siege aborted due to excessive socket failure; you can change the failure threshold in $HOME/.siegerc Transactions: 33550 hits Availability: 97.03 % Elapsed time: 1985.61 secs Data transferred: 3872.36 MB Response time: 0.34 secs Transaction rate: 16.90 trans/sec Throughput: 1.95 MB/sec Concurrency: 5.73 Successful transactions: 32917 Failed transactions: 1026 Longest transaction: 27.89 Shortest transaction: 0.00