You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@skywalking.apache.org by 凭窗观雨 <59...@qq.com> on 2020/01/23 11:32:23 UTC

回复: Question about service instance

Thanks a lot for the reply. 

It is great that can get and maintain instance sequence automatically. Because from DevOps perspective, the instances management tends to be "stateless"&nbsp;, i.e. to ignore the differences between the individual intances. 



And could you pls tell me the instance management is in which module/class in source code? I'd like to learn more details about this great functionality.


Thanks &amp; Happy Spring Festival
Patrick

 


------------------&nbsp;原始邮件&nbsp;------------------
发件人:&nbsp;"Sheng Wu"<wusheng@apache.org&gt;;
发送时间:&nbsp;2020年1月21日(星期二) 晚上11:24
收件人:&nbsp;"dev"<dev@skywalking.apache.org&gt;;

主题:&nbsp;Re: Question about service instance



Reply inline.

凭窗观雨 <5931110@qq.com&gt;于2020年1月21日 周二上午10:15写道:

&gt; Dear Skywalking Dev Team,
&gt;
&gt;
&gt; I have a question about the service instance and did not find answer in
&gt; docs, so have to email here for your help.
&gt;
&gt;
&gt; Let's take the case in the discussion
&gt; https://github.com/apache/skywalking/issues/3829 as example, does the
&gt; "service instance" stand for the instance on which the service is deployed
&gt; "physically", or it is a dummy terminology in Skywalking does not match the
&gt; "physical" instances?


In agent case, no matter which language agent. It is the physical instance.
In serivce mesh case, It represents a pod.


&gt;
&gt;
&gt; I.e. Does it means the Service A is deployed to 3 VM instances and Service
&gt; B is deployed to 2 VM instances, or there is NO guarantee of this?
&gt;

In agent case, They are.


&gt;
&gt; If yes, does it require the DevOps team to maintain sequence number of the
&gt; deployed instances for Skywalking? Or Skywalking can get and maintain the
&gt; instance sequence itself, no need the extra work for DevOps team?
&gt;

No, It is automatically.


&gt;
&gt;
&gt; Also imagining the Instance 2 of Service A was kicked
&gt; out&amp;nbsp;automatically due to a serious issue, and registered back again
&gt; after is was fixed. In such case if the sequence is still "Instance 2", or
&gt; it will be&amp;nbsp;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.


&gt;
&gt;
&gt; Much appreciate,
&gt; Patrick

-- 
Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108

Re: Question about service instance

Posted by Sheng Wu <wu...@gmail.com>.
凭窗观雨 <59...@qq.com>于2020年1月23日 周四下午7:32写道:

> Thanks a lot for the reply.
>
> It is great that can get and maintain instance sequence automatically.
> Because from DevOps perspective, the instances management tends to be
> "stateless"&nbsp;, i.e. to ignore the differences between the individual
> intances.
>
>
>
> And could you pls tell me the instance management is in which module/class
> in source code? I'd like to learn more details about this great
> functionality.


ServiceInstanceInventory is the register entity. There is a register
process for this entity.  Also, metadata DAO is related to query.

>
>
>
> Thanks &amp; Happy Spring Festival
> Patrick
>
>
>
>
> ------------------&nbsp;原始邮件&nbsp;------------------
> 发件人:&nbsp;"Sheng Wu"<wusheng@apache.org&gt;;
> 发送时间:&nbsp;2020年1月21日(星期二) 晚上11:24
> 收件人:&nbsp;"dev"<dev@skywalking.apache.org&gt;;
>
> 主题:&nbsp;Re: Question about service instance
>
>
>
> Reply inline.
>
> 凭窗观雨 <5931110@qq.com&gt;于2020年1月21日 周二上午10:15写道:
>
> &gt; Dear Skywalking Dev Team,
> &gt;
> &gt;
> &gt; I have a question about the service instance and did not find answer
> in
> &gt; docs, so have to email here for your help.
> &gt;
> &gt;
> &gt; Let's take the case in the discussion
> &gt; https://github.com/apache/skywalking/issues/3829 as example, does the
> &gt; "service instance" stand for the instance on which the service is
> deployed
> &gt; "physically", or it is a dummy terminology in Skywalking does not
> match the
> &gt; "physical" instances?
>
>
> In agent case, no matter which language agent. It is the physical instance.
> In serivce mesh case, It represents a pod.
>
>
> &gt;
> &gt;
> &gt; I.e. Does it means the Service A is deployed to 3 VM instances and
> Service
> &gt; B is deployed to 2 VM instances, or there is NO guarantee of this?
> &gt;
>
> In agent case, They are.
>
>
> &gt;
> &gt; If yes, does it require the DevOps team to maintain sequence number
> of the
> &gt; deployed instances for Skywalking? Or Skywalking can get and maintain
> the
> &gt; instance sequence itself, no need the extra work for DevOps team?
> &gt;
>
> No, It is automatically.
>
>
> &gt;
> &gt;
> &gt; Also imagining the Instance 2 of Service A was kicked
> &gt; out&amp;nbsp;automatically due to a serious issue, and registered
> back again
> &gt; after is was fixed. In such case if the sequence is still "Instance
> 2", or
> &gt; it will be&amp;nbsp;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.
>
>
> &gt;
> &gt;
> &gt; Much appreciate,
> &gt; Patrick
>
> --
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108

-- 
Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108