Azure-docs: Clarification on Actor Partitioning

[smoms]

Hi, I am not sure i got completely the way Actors are partitioned. In the page is mentioned that an Actor is a stateful service and ranged partitioned (uniform Int64 scheme). Am I correct then that an Actor instance ID corresponds to one only integer number (e.g. 123) and that can only manage state that correspond to the bucket (123)?
Also, what is meant for Partitioning in the above example of the 9 partitions? This is not the same as the partitioning concept of the Reliable Services, right? Because i understand that here Partitioning is meant as "just" a set of random Actors. thanks

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 57342b31-8271-e130-3df5-130580c9ea70
• Version Independent ID: fbd3f4b8-4199-2d82-245c-4a18f1073386
• Content: Service Fabric Reliable Actors Overview
• Content Source: articles/service-fabric/service-fabric-reliable-actors-introduction.md
• Service: service-fabric
• GitHub Login: @vturecek
• Microsoft Alias: vturecek

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[mimckitt]

@aljo-microsoft would you be able to elaborate further on this topic?

[vturecek]

Am I correct then that an Actor instance ID corresponds to one only integer number (e.g. 123) and that can only manage state that correspond to the bucket (123)?

Yes that's correct. It's exactly the same partitioning as used with stateful services. An actor, once created, is assigned an ID that never changes, and the ID is its partition key, so it always belongs to the same partition. The only thing that's random is the generation of the ID when an actor is first created if you don't provide one explicitly.

[mimckitt]

Thanks @vturecek

@smoms I will close this out but if you have follow up questions just let us know and we can always reopen and continue the discussion.