Skip to content

How to handle IService interface update #270

Open
@8ggmaker

Description

@8ggmaker

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions