[FTS-894] Reevaluate and refactor configuration, optimizer and scheduler Created: 14/Feb/17 Updated: 27/Jul/17 Resolved: 15/May/17 |
|
| Status: | Closed |
| Project: | FTS |
| Component/s: | MySQL, Server |
| Affects Version/s: | None |
| Fix Version/s: | fts 3.7.0 |
| Security Level: | Public Data (This ticket is visible to anyone on the internet and will be indexed by search engines) |
| Type: | Epic | Priority: | Minor |
| Reporter: | Alejandro Alvarez Ayllon (Inactive) | Assignee: | Alejandro Alvarez Ayllon (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Epic Name: | Configuration refactor | ||||||||||||||||||||||||||||||||||||||||||||
| Component Watchers: | |||||||||||||||||||||||||||||||||||||||||||||
| Actual Start: | |||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Need to reevaluate and refactor the way the configuration, scheduler and optimizer interact. For instance, I find confusing some checks on t_link_config when scheduling, because it disables the optimizer, but doesn't override with a number of actives. In my opinion, scheduling should only be affected by the optimizer and the absolute storage limit (since one storage may be part of more than one link running). All configuration related to number of actives and the like, should affect the optimizer. If the optimizer is disabled, leave the chosen value as is. Other parameters may still be of use outside the optimizer (i.e. udt, ipv6...) |
| Comments |
| Comment by GitLab service [ 12/May/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts-monitoring: |
| Comment by GitLab service [ 12/May/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts-monitoring: |
| Comment by GitLab service [ 12/May/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts-monitoring: |
| Comment by GitLab service [ 15/May/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a merge request of fts/fts-monitoring: |
| Comment by GitLab service [ 15/May/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts-monitoring: |
| Comment by Clockwork Droid [ 12/Jun/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |
| Comment by Clockwork Droid [ 27/Jul/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |
| Comment by Clockwork Droid [ 27/Jul/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |
| Comment by Clockwork Droid [ 27/Jul/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |
| Comment by Clockwork Droid [ 27/Jul/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |
| Comment by Clockwork Droid [ 27/Jul/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |
| Comment by Clockwork Droid [ 27/Jul/17 ] |
|
Alejandro Alvarez Ayllon mentioned this issue in a commit of fts/fts3: |