| Summary: | better thread selector | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Ian Rogers <ian.rogers> |
| Component: | io-threads | Assignee: | Shehjar Tikoo <shehjart> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.0.3 | CC: | amarts, gluster-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |
> > > Can this be scheduled to be done please? A simple round-robin - just > incremement a counter - should be more likely to pick an available worker. This has been fixed as part of bug 762315 in mainline and would be available in 3.1 release. *** This bug has been marked as a duplicate of bug 583 *** |
xlators/performance/io-threads/src/io-threads.c contains the comment /* Decide which thread will service the request. * FIXME: This should change into some form of load-balancing. * */ rand = random (); Can this be scheduled to be done please? A simple round-robin - just incremement a counter - should be more likely to pick an available worker.