Skip to content

Initial take at non-resolved hostnames issue.#8777

Draft
yossigo wants to merge 1 commit into
redis:unstablefrom
yossigo:sentinel-non-resolved-hostnames
Draft

Initial take at non-resolved hostnames issue.#8777
yossigo wants to merge 1 commit into
redis:unstablefrom
yossigo:sentinel-non-resolved-hostnames

Conversation

@yossigo

@yossigo yossigo commented Apr 13, 2021

Copy link
Copy Markdown
Collaborator

When hostnames are used, it is possible that we'll need to internally
access an instance whose hostname is currently not resolved.

Potentially fixes #8540.

When hostnames are used, it is possible that we'll need to internally
access an instance whose hostname is currently not resolved.

Potentially fixes redis#8540.
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]Sentinel stuck with +sdown upon replica pod restart

2 participants