?????? [Discussion]About service instances discovery reliable problems

2018-05-16 Thread bismy 
We have already done this @Yang Bo. But there are still some complicated 
scenarios. Firstly I addressed one of them is this PR: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/704






--  --
??: "Yang Bo";
: 2018??5??16??(??) 11:36
??: "dev";

: Re: [Discussion]About service instances discovery reliable problems



 We may do something like this:
Keep a copy of the instance/metadata information in clientside, and when
the SC is down, the client can still use the local information to visit
services.


On Wed, May 16, 2018 at 11:15 AM, Willem Jiang 
wrote:

> If we treat the service center as an online service, it should provide 7*24
> services.
> But if we use the standalone service center, it could be challenge for the
> service center provide 7*24 service.
>
> How can we setup the instance refresh strategy?
> We may need to provide different solution for different user case.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: willem
>
> On Mon, May 14, 2018 at 4:52 PM, bismy  wrote:
>
> > Supporting gray release need a lot of facilities to make it work and
> > service center upgrading can not apply gray release sometimes.
> > And other scenarios like standalone application(not cloud services)
> > restart is quite common. And base services restart can't influence user's
> > service communication.
> >
> >
> > --  --
> > ??: "wjm wjm";
> > : 2018??5??14??(??) 4:23
> > ??: "dev@servicecomb.apache.org";
> >
> > : Re: [Discussion]About service instances discovery reliable problems
> >
> >
> >
> > it's a problem, but why business use gray release, but we reject to the
> > solution?
> >
> > 2018??5??14??bismy  ??
> >
> > > When service center all instances stoped and then started. This is
> normal
> > > when we are doing maintenance. e.g. upgrading
> > >
> > >
> > >
> > >
> > > --  --
> > > ??: "wjm wjm";
> > > : 2018??5??14??(??) 12:36
> > > ??: "dev";
> > >
> > > : Re: [Discussion]About service instances discovery reliable problems
> > >
> > >
> > >
> > > " When service center restarted"
> > >
> > > that means one instance of SC cluster, or whole SC cluster?
> > > even one instance restart will clear all information?
> > >
> > > 2018-05-14 12:03 GMT+08:00 bismy :
> > >
> > > > Hi All,
> > > >
> > > >
> > > > Now we meet a reliable problem. When service center restarted, It
> will
> > > > clear all service instances information.
> > > > And when SDK(java-chassis) queries instance list periodically, it
> will
> > > get
> > > > an empty list and invocation will fail.
> > > >
> > > >
> > > > In order to resolve this problem, two solutions is suggested:
> > > > 1. service center provide instances persistence mechanism. When
> service
> > > > center restarted, it will restore instance information,
> > > > and re-calculate the timeout information(e.g. reset instance last
> > active
> > > > time to startup time). If he gets the heartbeat from instance, the
> > > instance
> > > > will not be removed, and after timeout,
> > > > it can removed instances, like the normal way.
> > > >  2. SDK need to take special care with instances remove. SDK don't
> > > > actually remove instances when he gets empty list from service center
> > and
> > > > it will ping the instances. If ping return
> > > > OK, the instance will not removed.
> > > >
> > > >
> > > > Known consequencies:
> > > > Solution 2:
> > > >   a. Conflicts with service center white/black rule.
> > > >   b. In docker or some instances changed frequently scenario, the
> > ip/port
> > > > is reused by many services when service start/stop, and service
> health
> > > URL
> > > > may also be the same. So it will give a lot of 400 like error when
> > > > instances is not updated.
> > > >
> > > >
> > > > Any suggestions?
> >
>



-- 
Best Regards,
Yang.

[ANNOUNCE] Yangbo Will Make a Speech about Apache ServiceComb (incubating) on OSC MeetUp in Shanghai on 27th May

2018-05-16 Thread Zen Lin 
Hi,

I am happy to share a good news, Yanbo is going to make a speech about our
project to promote the community, on OSChina MeetUp, in Shanghai, on 27th
May.

The topic is,
Design Considerations of DevOps for Microservices Solution in Apache
ServiceComb (incubating)

Draft introduction to the topic is,
With the rapid development of technologies/theories such as container,
cloud, agile, and DevOps, the microservice architecture has become
mainstream today. The Apache ServiceComb (incubating) has reached the good
performance, high reliability and other good results in the  traditional
enterprises when they transformation to CloudNative and building
microservices in CloudNative enterprises. The topic is to share how the
Apache ServiceComb (incubating) project is considered for the user's best
DevOps experience in the microservice architecture when design a
microservice framework.

Anyway , I am going to share the OSChina meetup link When the organizer
hangs out the activitie online.


Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb

Error Report Received When Sending a mail through dev@

2018-05-16 Thread Zen Lin 
Hi,
When I sent out a mail through the dev@ mail list,  I received a error
reply as following,  I think it is maybe because of someone have
unsubscribed the mail list.
I think it should not report error in this situation, could anyone help to
fix it?
postmas...@outlook.com
18:03 (3分钟前)
发送至 我

*newmx36.qq.com  rejected your message to the
following email addresses:*

liujichun1...@qq.com
Your message couldn't be delivered. When Office 365 tried to send the
message, the external email server returned the error below. This is
probably due to a problem or policy setting on the recipient's email system.

Check the error for information about the problem. The error might tell you
what went wrong and how to fix it. For example, if it says the message was
blocked due to a potential virus, try sending the message again without
attachments.

*For Email Admins*
This error was reported by an email server outside Office 365, and if the
sender is unable to fix the problem by modifying their message then it's
likely that it's a problem that only the recipient's email admin can fix.


   1. *Check the error for information about the problem.* The error might
   tell you what went wrong and provide clues for how to fix it. For example,
   if it says the message was rejected due a Sender Policy Framework (SPF)
   issue then you'll have to work with your domain registrar to properly
   configure your SPF record.
   2. *Check the error for information about where the problem is
   happening.* For example, look for a domain name like contoso.com. This
   tells you which organization was responsible for the error. The recipient's
   email server could be causing the problem, or it could be due to a
   third-party service that your organization or the recipient's organization
   is using to process or filter email messages.
   3. *If you can't fix the problem, contact the responsible party's email
   admin.* This could be the recipient's email admin, your smart host
   service admin, or someone similar. Provide them with the error code and
   error message from this non-delivery report (NDR) to help them troubleshoot
   the issue.

Unfortunately, Office 365 support is unlikely to be able to help with these
kinds of externally reported errors.




*newmx36.qq.com  gave this error:Remote server
returned an error -> 550 Mailbox not
found. http://service.mail.qq.com/cgi-bin/help?subtype=1&=20022&=1000728
 *




Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb

Re: Please Update the JIRA Status for Preparing the Next Release

2018-05-16 Thread Zen Lin 
Hi Yangbo, It is so nice of you to help sorting out issues on JIRA.

Maybe we have lacked of a part, about contributions on website.
Although the website's issue is not included in the releases, it is indeed
an important part of the next release of ServiceComb,
for example, the userguide and quickstart improvements that Liu Bao and Qi
Lin are dealing with.

I think It could be better if you can include this part too. In this case,
we can put them into the release notes to promotion as important features
before the release.

By the way, It is better to put the attachment in other place and
referenced in the mail,but not in the mail list directly.

Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb

2018-05-16 17:30 GMT+08:00 Yang Bo :

> Hi All,
>
> We will release the next version of ServiceComb in late June, and the
> feature freeze will happen in the end of May.
>
> I checked all the undone issues of SCB project on apache JIRA today. And
> assigned fixVersions to some of the issues.
>
> Please check the issues you report or assigned and update them
> accordingly. If the fixVersions is incorrect, please update it.
>
> There are many issues that is unassigned, please assign them or modify the
> fixVersions to the next release.(1.0.0 for SC and Chassis, 0.3.0 for Saga).
>
> The attachment is a list of all issues. Please update them by 2018/05/18.
>
>
>
> --
> Best Regards,
> Yang.
>

Please Update the JIRA Status for Preparing the Next Release

2018-05-16 Thread Yang Bo 
Hi All,

We will release the next version of ServiceComb in late June, and the
feature freeze will happen in the end of May.

I checked all the undone issues of SCB project on apache JIRA today. And
assigned fixVersions to some of the issues.

Please check the issues you report or assigned and update them accordingly.
If the fixVersions is incorrect, please update it.

There are many issues that is unassigned, please assign them or modify the
fixVersions to the next release.(1.0.0 for SC and Chassis, 0.3.0 for Saga).

The attachment is a list of all issues. Please update them by 2018/05/18.



-- 
Best Regards,
Yang.


JIRA_Issues_20180516.xlsx
Description: MS-Excel 2007 spreadsheet