discovery hotal service instances from SC.
>
>
>
>
> -- 原始邮件 --
> 发件人: "willem.jiang";
> 发送时间: 2018年7月26日(星期四) 上午9:32
> 收件人: "dev";
>
> 主题: Re: Cannot find the instance in ServiceComb Discovery
>
>
>
> Thx a
+00:00 INFO
> > > > > backend/listwatch.go:74 caught event {action: PUT, count: 1/1, rev:
> > 18,
> > > > > succeed: true}, watch prefix /cse-sr/ms/indexes/, start rev 15+1,
> > > > > service-center> 2018-07-25 08:00:43.0
UT, count: 1/1, rev:
> 18,
> > > > succeed: true}, watch prefix /cse-sr/ms/alias/, start rev 3+1,
> > > > payment> 2018-07-25 08:00:43.058 INFO 7 --- [ main]
> > > > o.a.s.s.task.MicroserviceRegisterTask: Registry Microservice
> >
ma.go:69
> > > get schema failed, serviceId d435f3f78fe011e89bc30242ac110002,
> schemaId
> > > payment-endpoint: schema not exists.
> > > payment> 2018-07-25 08:00:43.065 WARN 7 --- [ntloop-thread-0]
> > o.a.s.s.c.h.ServiceRegistryClientI
ds=[payment-endpoint], env=[]
>> > payment> 2018-07-25 08:00:43.063 INFO 7 --- [ main]
>> > o.a.s.s.task.MicroserviceRegisterTask: schemaId [payment-endpoint]
>> > exists [true], summary exists [false]
>> > service-center> 2018-07-25 0
t;,"errorMessage":"Schema
> > does not exist","detail":"Do not have this schema info."}
> > payment>
> > service-center> 2018-07-25 08:00:43.086 +00:00 INFO service/schema.go:564
> > start to modify schema, serviceId d435f3f78fe011e89bc30242ac110002,
>
pose and not
>> > intended for product use. Is there many scenarios need this? Or we
>> need to
>> > reorganize its code to meet product use.
>> >
>> >
>> >
>> >
>> > ------ 原始邮件 --
>> > 发件人: "willem
the user to write the test without starting the
> service-center,
> we could add it into the section of best practice of writing a uni test.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Jul 25, 2018 at 2:27 PM, bismy wrote:
>
>> Local
schema successfully: serviceId d435f3f78fe011e89bc30242ac110002,
> schemaId payment-endpoint.
> service-center> 2018-07-25 08:00:43.089 +00:00 INFO
> backend/listwatch.go:74 caught event {action: PUT, count: 1/1, rev: 19,
> succeed: true}, watch prefix /cse-sr/ms/schema-sum/, start rev 16+
product use.
> >
> >
> >
> >
> > -- 原始邮件 --
> > 发件人: "willem.jiang";
> > 发送时间: 2018年7月25日(星期三) 下午2:22
> > 收件人: "dev";
> >
> > 主题: Re: Cannot find the instance in ServiceComb Discovery
>
sis is created only for test purpose and not
> intended for product use. Is there many scenarios need this? Or we need to
> reorganize its code to meet product use.
>
>
>
>
> -- 原始邮件 --
> 发件人: "willem.jiang";
> 发送时间: 2018年7月25日(星期三) 下午2:
you write a local registry.yaml, but missed some important data
a easy way to fix: do not write the registry.yaml
because you test case is self invoke self, ServiceComb engine can generate
informations dynamiclly
change:
12 matches
Mail list logo