Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle IService interface update #270

Open
8ggmaker opened this issue Mar 19, 2021 · 0 comments
Open

How to handle IService interface update #270

8ggmaker opened this issue Mar 19, 2021 · 0 comments

Comments

@8ggmaker
Copy link
Member

The problem can be simplified as below :
we have two services of our service fabric cluster:

public class ServiceA: IService
{
     public async Task CallA()
    {
        var proxy = CreateProxy(urlofBService);
        await proxy.CallB();
    }
}

public class ServiceB: IService
{
     public async Task CallB()
     {
     }
}

ServiceA will call ServiceB with remoting call.
If next time we update code to:

public class ServiceA: IService
{
     public async Task CallA()
    {
        var proxy = CreateProxy(urlofBService);
        await proxy.CallBNew();
    }
}

public class ServiceB: IService
{
     public async Task CallBNew()
     {
     }
}

we have 3 nodes in our cluster, when we do upgrade deployment, node0 and node1 upgrade successfully, and node2 is on pending, when there is call from ServiceA in node0 target to node2, it will throw exception, because CallBNew is not ready in node2. Is there any solution about this scenario ?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant