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.

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

[ybase] Core dump occurring for k8s universes #5561

Closed
daniel-yb opened this issue Sep 1, 2020 · 0 comments
Closed

[ybase] Core dump occurring for k8s universes #5561

daniel-yb opened this issue Sep 1, 2020 · 0 comments
Assignees
Labels
area/docdb YugabyteDB core features

Comments

@daniel-yb
Copy link
Contributor

daniel-yb commented Sep 1, 2020

This looks like it might be related to DNS resolution from cache for k8s universes.

Core dump:
coreDump.txt

@daniel-yb daniel-yb added the area/docdb YugabyteDB core features label Sep 1, 2020
spolitov added a commit that referenced this issue Sep 7, 2020
Summary:
Async client initializer uses separate thread to perform it's job.
This thread does not have CDS attached, so it crashes in case of call to RPC thread pool.
Such call is possible when master resolution failed and such result already stored in DNS cache.

Test Plan: ybd --gtest_filter ClientTest.BadMasterAddress

Reviewers: timur

Reviewed By: timur

Subscribers: ybase

Differential Revision: https://phabricator.dev.yugabyte.com/D9326
@spolitov spolitov closed this as completed Sep 8, 2020
spolitov added a commit that referenced this issue Sep 9, 2020
Summary:
Async client initializer uses separate thread to perform it's job.
This thread does not have CDS attached, so it crashes in case of call to RPC thread pool.
Such call is possible when master resolution failed and such result already stored in DNS cache.

Test Plan:
ybd --gtest_filter ClientTest.BadMasterAddress
Jenkins: rebase: 2.1

Reviewers: timur

Reviewed By: timur

Subscribers: ybase

Differential Revision: https://phabricator.dev.yugabyte.com/D9333
spolitov added a commit that referenced this issue Sep 9, 2020
Summary:
Async client initializer uses separate thread to perform it's job.
This thread does not have CDS attached, so it crashes in case of call to RPC thread pool.
Such call is possible when master resolution failed and such result already stored in DNS cache.

Test Plan:
ybd --gtest_filter ClientTest.BadMasterAddress
Jenkins: rebase: 2.2

Reviewers: timur

Reviewed By: timur

Subscribers: ybase

Differential Revision: https://phabricator.dev.yugabyte.com/D9334
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features
Projects
None yet
Development

No branches or pull requests

2 participants