Reply inline. 凭窗观雨 <[email protected]>于2020年1月21日 周二上午10:15写道：
> Dear Skywalking Dev Team, > > > I have a question about the service instance and did not find answer in > docs, so have to email here for your help. > > > Let's take the case in the discussion > https://github.com/apache/skywalking/issues/3829 as example, does the > "service instance" stand for the instance on which the service is deployed > "physically", or it is a dummy terminology in Skywalking does not match the > "physical" instances? In agent case, no matter which language agent. It is the physical instance. In serivce mesh case, It represents a pod. > > > I.e. Does it means the Service A is deployed to 3 VM instances and Service > B is deployed to 2 VM instances, or there is NO guarantee of this? > In agent case, They are. > > If yes, does it require the DevOps team to maintain sequence number of the > deployed instances for Skywalking? Or Skywalking can get and maintain the > instance sequence itself, no need the extra work for DevOps team? > No, It is automatically. > > > Also imagining the Instance 2 of Service A was kicked > out automatically due to a serious issue, and registered back again > after is was fixed. In such case if the sequence is still "Instance 2", or > it will be assigned a new sequence like "Instance 4"? In default, It will be instance 4. But you could could set UUID manually, then it will keep in the same instance which uses this UUID first. In the next 7.0.0, you even could set instance name in UUID. > > > Much appreciate, > Patrick -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
