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(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too