Skip to content

Conversation

@hansenmc
Copy link
Member

Currently, XCC resolves the IP of a host when instantiated and it remains static. This can be problematic for proxies that have a dynamic set of nodes backing it, such as Amazon ALB or ELB. If a proxy node is removed from the pool, then a long-running job can encounter errors when that IP goes dark.

Instantiating a new ContentSource will resolve the IP again, and should help keeping the jobs from stalling our or failing.

…us some minor edits for code formatting and whatnot.
…rent than the current ContentSource

- Add option CONTENT-SOURCE-RENEW to allow users to configure whether to create a fresh ContentSource onError
@hansenmc
Copy link
Member Author

@bbandlamudi as discussed, changed to only swap ContentSource if IP has changed, and to have an option to enable/disable the behavior (but have it enabled by default).

@hansenmc hansenmc merged commit fbf7279 into development Mar 28, 2022
@hansenmc hansenmc deleted the contentSourceRefresh branch March 28, 2022 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants