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

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...