Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DNS resolution failures in Raft when binding to hostnames #313

Closed
bmatican opened this issue May 30, 2018 · 1 comment
Closed

DNS resolution failures in Raft when binding to hostnames #313

bmatican opened this issue May 30, 2018 · 1 comment
Assignees
@spolitov
Labels
kind/enhancement This is an enhancement of an existing feature

Comments

@bmatican
Copy link
Contributor

As per later findings in #128, we discovered some issues in the Raft flow after adding better control over DNS resolution. In particular, Raft was failing to generate Peer objects, which would fail bookkeeping and ultimately break a part of the protocol. This is most easily visible when we remove a node and its DNS entry, such that internal DNS resolution breaks.
@bmatican bmatican added kind/enhancement This is an enhancement of an existing feature in progress labels May 30, 2018
mbautin pushed a commit that referenced this issue Jun 6, 2018
@spolitov @mbautin
ENG-3282: #313: Use HostPort in Proxy instead of Endpoint
0ffbaaa 
Summary:
Use HostPort when creating Proxy.
So instead of preresolve endpoint before creating Proxy,
we could resolve it lazily.

Test Plan: Jenkins

Reviewers: mikhail, bogdan

Reviewed By: bogdan

Subscribers: kannan, hector, ybase, bharat

Differential Revision: https://phabricator.dev.yugabyte.com/D4901
@spolitov
Copy link
Contributor

spolitov commented Jun 9, 2018

Fixed

@spolitov spolitov closed this as completed Jun 9, 2018
mbautin pushed a commit that referenced this issue Jul 11, 2019
@spolitov @mbautin
This commit provides additional functionality that is logically relat…
da3534c 
…ed to the

earlier commit 0ffbaaa

Original commit message:

ENG-3282: #313: Use HostPort in Proxy instead of Endpoint

Summary:
Use HostPort when creating Proxy.
So instead of preresolve endpoint before creating Proxy,
we could resolve it lazily.

Test Plan: Jenkins

Reviewers: mikhail, bogdan

Reviewed By: bogdan

Subscribers: kannan, hector, ybase, bharat

Differential Revision: https://phabricator.dev.yugabyte.com/D4901
mbautin pushed a commit to mbautin/yugabyte-db that referenced this issue Jul 16, 2019
@spolitov
ENG-3282: yugabyte#313: Use HostPort in Proxy instead of Endpoint
4c620e9 
Summary:
Use HostPort when creating Proxy.
So instead of preresolve endpoint before creating Proxy,
we could resolve it lazily.

Test Plan: Jenkins

Reviewers: mikhail, bogdan

Reviewed By: bogdan

Subscribers: kannan, hector, ybase, bharat

Differential Revision: https://phabricator.dev.yugabyte.com/D4901

Note:
This commit provides additional functionality that is logically related to
the earlier commit yugabyte@0ffbaaa
and supersedes the commit yugabyte@da3534c
jasonyb pushed a commit that referenced this issue Jun 11, 2024
@Naeem-Akhter
Merge pull request #313 from ibrarahmad/PG-552
4f281a8 
PG-552: Remove unnecessary columns from PostgreSQL 11 and 12 views.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spolitov spolitov

Labels
kind/enhancement This is an enhancement of an existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bmatican @spolitov