Skip to main content

Azure Service Fabric: The primary or stateless instance for the partition has invalid address, this means that right address from the replica/instance is not registered in the system.

What should you do when you are using Azure Service Fabric and you receive the following error code when you call a Reliable Service that is Stateful:
The primary or stateless instance for the partition has invalid address, this means that right address from the replica/instance is not registered in the system.
Sample
Remote Call:
IStatefull smsService = ServiceProxy.Create<IStatefull>(
                        new Uri("fabric:/ITCamp.SF/Stateful"),new ServicePartitionKey(1));
                   
await smsService.SendSmsAsync(
    phoneNumber,
    $"{DateTime.Now.ToShortTimeString()} Hello ITCamp!, from '{phoneNumber}'");                    

Service
    internal sealed class Stateful : StatefulService, IStatefull
    {
        public Stateful(StatefulServiceContext context)
            : base(context)
        { }

        protected override IEnumerable<ServiceReplicaListener> CreateServiceReplicaListeners()
        {
            return new ServiceReplicaListener[0];
        }

        protected override async Task RunAsync(CancellationToken cancellationToken)
        {
            IReliableQueue<Sms> smsToSetQueue = await StateManager.GetOrAddAsync<IReliableQueue<Sms>>("smsToSent");

            while (true)
            {
                cancellationToken.ThrowIfCancellationRequested();
                await Task.Delay(TimeSpan.FromSeconds(1), cancellationToken);

                using (ITransaction tx=StateManager.CreateTransaction())
                {
                    ConditionalValue<Sms> smsToSent = await smsToSetQueue.TryDequeueAsync(tx);

                    if (!smsToSent.HasValue)
                    {
                        await tx.CommitAsync();
                        continue;        
                    }

                    ServiceEventSource.Current.ServiceMessage(this, 
                        "SMS to the phone number '{0}' was send to end client",
                        smsToSent.Value.PhoneNumber);
                    await tx.CommitAsync();
                }                               
            }
        }

        public async Task SendSmsAsync(string phoneNumber, string message)
        {
            IReliableQueue<Sms> smsToSetQueue = await StateManager.GetOrAddAsync<IReliableQueue<Sms>>("smsToSent");

            using (ITransaction tx = StateManager.CreateTransaction())
            {
                await smsToSetQueue.EnqueueAsync(tx, new Sms()
                {
                    Message = message,
                    PhoneNumber = phoneNumber
                });
                await tx.CommitAsync();
            }
        }
    }

Solution
The problem is from CreateServiceReplicaListeners and is happening because there is no listener set. The only thing that you need to do to be able to make a call over Service Remoting is to set the listener as below.

    internal sealed class Stateful : StatefulService, IStatefull
    {
        public Stateful(StatefulServiceContext context)
            : base(context)
        { }

        protected override IEnumerable<ServiceReplicaListener> CreateServiceReplicaListeners()
        {
            return new[] { new ServiceReplicaListener(context => this.CreateServiceRemotingListener(context)) };
        }

    ....
    }

Comments

  1. This is out of date. Do you have an example of the next version of the DLLs where there is no method CreateServiceRemotingListener() ??

    ReplyDelete
  2. Awesome catch! thanks! note: same trick for stateless too, only that it's ServiceInstanceListener instead of ServiceReplicaListener

    ReplyDelete
  3. I really like the way you put the information. Also thanks to JDer to mention the important point for stateless service. Great guidance post and can save lot of time.

    ReplyDelete
  4. For stateless, this does not compile:
    protected override IEnumerable CreateServiceInstanceListeners()
    {
    return new[] { new ServiceReplicaListener(context => this.ServiceInstanceListener(context)) };

    //return new ServiceInstanceListener[0];
    }

    ReplyDelete
    Replies
    1. Yes, the code doen't compiles anymore, because at the Build a new version of SDK wa released, that is not backward compatible with RC.

      Delete
  5. If anyone have issues with CreateServiceRemotingListener not being found, it is an extension method and you can get it by adding the following using in your service:

    using Microsoft.ServiceFabric.Services.Remoting.Runtime;

    ReplyDelete
  6. Thanks for all the input from you guys and great writeup as well.
    For stateless, this works for me:
    protected override IEnumerable CreateServiceInstanceListeners()
    {
    return new[] { new ServiceInstanceListener(context => this.CreateServiceRemotingListener(context)) };

    }

    ReplyDelete
    Replies
    1. Thanks Michael! After hours of frustration, this was exactly what I needed!

      Delete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP