remove JobUpdater from Tier0 configuration #4064
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
@ticoann , the only thing the JobUpdater does is to check for and apply RequestManager priority changes in the agent, right ? |
Contributor
That is correct. |
Member
Author
|
Ok, in that case it's not needed in the Tier0. |
hufnagel
added a commit
that referenced
this pull request
Feb 24, 2014
remove JobUpdater from Tier0 configuration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the subject says, this patch removes the JobUpdater component from the Tier0 configuration. It doesn't work in a Tier0 environment as we don't have a RequestManager.