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

VHDS subscription could refer a destructed init manager #9254

Closed
lambdai opened this issue Dec 6, 2019 · 7 comments
Closed

VHDS subscription could refer a destructed init manager #9254

lambdai opened this issue Dec 6, 2019 · 7 comments
Assignees
Labels
area/xds bug no stalebot Disables stalebot from closing an issue
Milestone

Comments

@lambdai
Copy link
Contributor

lambdai commented Dec 6, 2019

Description:

Brainstormed in my PR #9209 but then I realize the issue is there before.
#7617

The background is RdsRouteConfigSubscription has been shared by multiple providers across listeners.
Upon subscription construction the subscription keep a reference to the Init::Manager provided by the listener.
If the RDS config has VHDS field, VHDS subscription will be created and that Init::Manager reference will be dereferenced.
Since subscription is shared across listeners, the above Init::Manager might be already destructed with the initial listener.

Boom.

@stevenzzzz
Copy link
Contributor

This is a similar problem as RDS in the scope of SRDS, where a new subscription might be created exceed listenerImpl life-span. I think we can fix it by depending on a noop init manager when we detect that the listener is gone. it's kinda of an addition to the #7617, we can probably solve both in one shot.

@dio dio added the area/xds label Dec 9, 2019
@lambdai
Copy link
Contributor Author

lambdai commented Dec 12, 2019

Agree. Need to find another signal to indicate init_manager is not required.

@stale
Copy link

stale bot commented Jan 11, 2020

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Jan 11, 2020
@stale
Copy link

stale bot commented Jan 19, 2020

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Jan 19, 2020
@mattklein123 mattklein123 reopened this Jan 19, 2020
@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Jan 19, 2020
@mattklein123 mattklein123 added bug stale stalebot believes this issue/PR has not been touched recently labels Jan 19, 2020
@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Jan 19, 2020
@mattklein123 mattklein123 added no stalebot Disables stalebot from closing an issue stale stalebot believes this issue/PR has not been touched recently labels Jan 19, 2020
@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Jan 19, 2020
@mattklein123 mattklein123 added this to the 1.14.0 milestone Jan 19, 2020
@stevenzzzz
Copy link
Contributor

stevenzzzz commented Jan 19, 2020 via email

@stevenzzzz
Copy link
Contributor

I believe this is fixed by #9779, in RDS onConfigUpdate a local init-manager is used instead of listener's init_manager_ in VHDS's subscription creation.

@stevenzzzz
Copy link
Contributor

apparently I can't close it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/xds bug no stalebot Disables stalebot from closing an issue
Projects
None yet
Development

No branches or pull requests

4 participants