Skip to content

Support upgrade backend w/o rebooting agents #3072

@wu-sheng

Description

@wu-sheng

Support upgrade backend w/o rebooting agents

2019 - 07 - 14

Background

SkyWalking backend version upgrade usually includes persistence structure changes, due to performance improvements or new feature added. But, today, SkyWalking agent caches service id, service instance id, and endpoint mapping cache, all of these caches are designed for reducing network/storage payload/cost. So these have to be kept.
But, we realized the agents rebooting is a challenge to most end users. Because rebooting agents mean rebooting business applications, which is a limited operation in the OPS team.

Design doc

https://docs.google.com/document/d/1mlOmydJyICuqwGveem260dJEWxAE-ssMOy8gzXm33Yo/edit?usp=sharing

Committer

@kezhenxu94

Reviewer team

@wu-sheng @ascrutae @peng-yongsheng and others who have interests.

Metadata

Metadata

Assignees

Labels

agentLanguage agent related.backendOAP backend related.core featureCore and important feature. Sometimes, break backwards compatibility.featureNew feature

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions