Akka.Cluster.Hosting
1.6.0-beta8
Prefix Reserved
dotnet add package Akka.Cluster.Hosting --version 1.6.0-beta8
NuGet\Install-Package Akka.Cluster.Hosting -Version 1.6.0-beta8
<PackageReference Include="Akka.Cluster.Hosting" Version="1.6.0-beta8" />
<PackageVersion Include="Akka.Cluster.Hosting" Version="1.6.0-beta8" />
<PackageReference Include="Akka.Cluster.Hosting" />
paket add Akka.Cluster.Hosting --version 1.6.0-beta8
#r "nuget: Akka.Cluster.Hosting, 1.6.0-beta8"
#:package Akka.Cluster.Hosting@1.6.0-beta8
#addin nuget:?package=Akka.Cluster.Hosting&version=1.6.0-beta8&prerelease
#tool nuget:?package=Akka.Cluster.Hosting&version=1.6.0-beta8&prerelease
Akka.Cluster.Hosting
This module provides Akka.Hosting ease-of-use extension methods for Akka.Cluster, Akka.Cluster.Sharding, and Akka.Cluster.Tools.
Content
Akka.Cluster Extension Methods
WithClustering Method
An extension method to add Akka.Cluster support to the ActorSystem.
public static AkkaConfigurationBuilder WithClustering(
this AkkaConfigurationBuilder builder,
ClusterOptions options = null);
Parameters
optionsClusterOptionsOptional. Akka.Cluster configuration parameters.
Example
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
{
configurationBuilder
.WithRemoting("localhost", 8110)
.WithClustering(new ClusterOptions {
Roles = new[] { "myRole" },
SeedNodes = new[] { Address.Parse("akka.tcp://MyActorSystem@localhost:8110")},
SplitBrainResolver = SplitBrainResolverOption.Default
});
});
var app = builder.Build();
app.Run();
The code above will start Akka.Cluster with Akka.Remote at localhost domain port 8110 and joins itself through the configured SeedNodes to form a single node cluster. The ClusterOptions class lets you configure the node roles and the seed nodes it should join at start up.
Configure A Cluster With Split-Brain Resolver (SBR)
The ClusterOptions.SplitBrainResolver property lets you configure a SBR. There are four different strategies that the SBR can use, to set one up you will need to pass in one of these class instances:
| Strategy name | Option class |
|---|---|
| Keep Majority | KeepMajorityOption |
| Static-Quorum | StaticQuorumOption |
| Keep Oldest | KeepOldestOption |
| Lease Majority | LeaseMajorityOption |
You can also pass in SplitBrainResolverOption.Default for the default SBR setting that uses the Keep Majority strategy with no role defined.
builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
{
configurationBuilder
.WithClustering(new ClusterOptions {
SplitBrainResolver = new KeepMajorityOption{ Role = "myRole" },
});
});
Using Lease-Majority Split-Brain Resolver Strategy
In order to use LeaseMajorityOption you will need to provide an instance of the option class of the Lease module you're going to use in the LeaseMajorityOption.LeaseImplementation property.
For
Akka.Coordination.KubernetesApi, this is an instance ofAkka.Coordination.KubernetesApi.KubernetesLeaseOptionclass.builder.Services.AddAkka("MyActorSystem", configurationBuilder => { var leaseOptions = new KubernetesLeaseOption(); configurationBuilder .WithClustering(new ClusterOptions { SplitBrainResolver = new LeaseMajorityOption{ LeaseImplementation = leaseOptions, }, }) .WithKubernetesLease(leaseOptions); });For
Akka.Coordination.Azurethis is an instance ofAkka.Coordination.Azure.AzureLeaseOptionclass.builder.Services.AddAkka("MyActorSystem", configurationBuilder => { var leaseOptions = new AzureLeaseOption { ConnectionString = "<Your-Azure-Blob-storage-connection-string>", ContainerName = "<Your-Azure-Blob-storage-container-name>"; }; configurationBuilder .WithClustering(new ClusterOptions { SplitBrainResolver = new LeaseMajorityOption{ LeaseImplementation = leaseOptions, }, }) .WithAzureLease(leaseOptions); });
Akka.Cluster.Sharding Extension Methods
WithShardRegion Method
An extension method to set up Cluster Sharding. Starts a ShardRegion actor for the given entity typeName and registers the ShardRegion IActorRef with TKey in the ActorRegistry for this ActorSystem.
Overloads
public static AkkaConfigurationBuilder WithShardRegion<TKey>(
this AkkaConfigurationBuilder builder,
string typeName,
Func<string, Props> entityPropsFactory,
IMessageExtractor messageExtractor,
ShardOptions shardOptions);
public static AkkaConfigurationBuilder WithShardRegion<TKey>(
this AkkaConfigurationBuilder builder,
string typeName,
Func<string, Props> entityPropsFactory,
ExtractEntityId extractEntityId,
ExtractShardId extractShardId,
ShardOptions shardOptions);
public static AkkaConfigurationBuilder WithShardRegion<TKey>(
this AkkaConfigurationBuilder builder,
string typeName,
Func<ActorSystem, IActorRegistry, Func<string, Props>> compositePropsFactory,
IMessageExtractor messageExtractor,
ShardOptions shardOptions);
public static AkkaConfigurationBuilder WithShardRegion<TKey>(
this AkkaConfigurationBuilder builder,
string typeName,
Func<ActorSystem, IActorRegistry, Func<string, Props>> compositePropsFactory,
ExtractEntityId extractEntityId,
ExtractShardId extractShardId,
ShardOptions shardOptions);
Type Parameters
TKeyThe type key to use to retrieve the
IActorReffor thisShardRegionfrom theActorRegistry.
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
typeNamestringThe name of the entity type
entityPropsFactoryFunc<string, Props>Function that, given an entity id, returns the
Actor.Propsof the entity actors that will be created by theSharding.ShardRegioncompositePropsFactoryFunc<ActorSystem, IActorRegistry, Func<string, Props>>A delegate function that takes an
ActorSystemand anActorRegistryas parameters and returns aPropsfactory. Used when thePropsfactory either depends on another actor or needs to access theActorSystemto set thePropsup.messageExtractorIMessageExtractorAn
IMessageExtractorinterface implementation to extract the entity id, shard id, and the message to send to the entity from the incoming message.extractEntityIdExtractEntityIdPartial delegate function to extract the entity id and the message to send to the entity from the incoming message, if the partial function does not match the message will be
unhandled, i.e.posted asUnhandledmessages on the event streamextractShardIdExtractShardIdDelegate function to determine the shard id for an incoming message, only messages that passed the
extractEntityIdwill be usedshardOptionsShardOptionsThe set of options for configuring
ClusterShardingSettings
Example
public class EchoActor : ReceiveActor
{
private readonly string _entityId;
public EchoActor(string entityId)
{
_entityId = entityId;
ReceiveAny(message => {
Sender.Tell($"{Self} rcv {message}");
});
}
}
public class Program
{
private const int NumberOfShards = 5;
private static Option<(string, object)> ExtractEntityId(object message)
=> message switch {
string id => (id, id),
_ => Option<(string, object)>.None
};
private static string? ExtractShardId(object message)
=> message switch {
string id => (id.GetHashCode() % NumberOfShards).ToString(),
_ => null
};
private static Props PropsFactory(string entityId)
=> Props.Create(() => new EchoActor(entityId));
public static void Main(params string[] args)
{
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
{
configurationBuilder
.WithRemoting(hostname: "localhost", port: 8110)
.WithClustering(new ClusterOptions{SeedNodes = new []{ Address.Parse("akka.tcp://MyActorSystem@localhost:8110"), }})
.WithShardRegion<Echo>(
typeName: "myRegion",
entityPropsFactory: PropsFactory,
extractEntityId: ExtractEntityId,
extractShardId: ExtractShardId,
shardOptions: new ShardOptions());
});
var app = builder.Build();
app.MapGet("/", async (context) =>
{
var echo = context.RequestServices.GetRequiredService<ActorRegistry>().Get<Echo>();
var body = await echo.Ask<string>(
message: context.TraceIdentifier,
cancellationToken: context.RequestAborted)
.ConfigureAwait(false);
await context.Response.WriteAsync(body);
});
app.Run();
}
}
Using Lease With Cluster Sharding
To use the cluster sharding lease feature, you will need to pass in the lease option into the shardOptions parameter:
var leaseOptions = new AzureLeaseOption {
ConnectionString = "<Your-Azure-Blob-storage-connection-string>",
ContainerName = "<Your-Azure-Blob-storage-container-name>";
};
configurationBuilder
.WithRemoting(hostname: "localhost", port: 8110)
.WithClustering(new ClusterOptions{SeedNodes = new []{ Address.Parse("akka.tcp://MyActorSystem@localhost:8110"), }})
.WithShardRegion<Echo>(
typeName: "myRegion",
entityPropsFactory: PropsFactory,
extractEntityId: ExtractEntityId,
extractShardId: ExtractShardId,
shardOptions: new ShardOptions{
LeaseImplementation = leaseOptions,
})
.WithAzureLease(leaseOptions);
WithShardRegionProxy Method
An extension method to start a ShardRegion proxy actor that points to a ShardRegion hosted on a different role inside the cluster and registers the IActorRef with TKey in the ActorRegistry for this ActorSystem.
Overloads
public static AkkaConfigurationBuilder WithShardRegionProxy<TKey>(
this AkkaConfigurationBuilder builder,
string typeName,
string roleName,
ExtractEntityId extractEntityId,
ExtractShardId extractShardId);
public static AkkaConfigurationBuilder WithShardRegionProxy<TKey>(
this AkkaConfigurationBuilder builder,
string typeName,
string roleName,
IMessageExtractor messageExtractor);
Type Parameters
TKeyThe type key to use to retrieve the
IActorReffor thisShardRegionfrom theActorRegistry.
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
typeNamestringThe name of the entity type
roleNamestringThe role of the Akka.Cluster member that is hosting the target
ShardRegion.messageExtractorIMessageExtractorAn
IMessageExtractorinterface implementation to extract the entity id, shard id, and the message to send to the entity from the incoming message.extractEntityIdExtractEntityIdPartial delegate function to extract the entity id and the message to send to the entity from the incoming message, if the partial function does not match the message will be
unhandled, i.e.posted asUnhandledmessages on the event streamextractShardIdExtractShardIdDelegate function to determine the shard id for an incoming message, only messages that passed the
extractEntityIdwill be used
Akka.Cluster.Tools Extension Methods
WithDistributedPubSub Method
An extension method to start Distributed Publish Subscribe on this node immediately upon ActorSystem startup. Stores the pub-sub mediator IActorRef in the ActorRegistry using the DistributedPubSub key.
public static AkkaConfigurationBuilder WithDistributedPubSub(
this AkkaConfigurationBuilder builder,
string role);
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
rolestringSpecifies which role
DistributedPubSubwill broadcast gossip to. If this value is left blank then ALL roles will be targeted.
WithSingleton Method
An extension method to start Cluster Singleton. Creates a new Singleton Manager to host an actor created via actorProps.
If createProxyToo is set to true then this method will also create a ClusterSingletonProxy that will be added to the ActorRegistry using the key TKey. Otherwise this method will register nothing with the ActorRegistry.
public static AkkaConfigurationBuilder WithSingleton<TKey>(
this AkkaConfigurationBuilder builder,
string singletonName,
Props actorProps,
ClusterSingletonOptions options = null,
bool createProxyToo = true);
Type Parameters
TKeyThe key type to use for the
ActorRegistrywhencreateProxyToois set to true.
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
singletonNamestring
The name of this singleton instance. Will also be used in the ActorPath for the ClusterSingletonManager and optionally, the ClusterSingletonProxy created by this method.
actorPropsProps
The underlying actor type. SHOULD NOT BE CREATED USING ClusterSingletonManager.Props
optionsClusterSingletonOptions
Optional. The set of options for configuring both the ClusterSingletonManager and optionally, the ClusterSingletonProxy.
createProxyToobool
When set to true, creates a ClusterSingletonProxy that automatically points to the ClusterSingletonManager created by this method.
Using Lease With Cluster Singleton
To use the cluster singleton lease feature, you will need to pass in the lease option into the options parameter:
Props propsFactory(ActorSystem system, IActorRegistry registry, IDependencyResolver resolver)
=> Props.Create(() => new EchoActor());
var leaseOptions = new AzureLeaseOption {
ConnectionString = "<Your-Azure-Blob-storage-connection-string>",
ContainerName = "<Your-Azure-Blob-storage-container-name>";
};
configurationBuilder
.WithRemoting()
.WithClustering()
.WithSingleton<Echo>(
singletonName: "singleton",
propsFactory: propsFactory,
options: new ClusterSingletonOptions {
LeaseImplementation = leaseOptions,
})
.WithAzureLease(leaseOptions);
WithSingletonProxy Method
An extension method to create a Cluster Singleton Proxy and adds it to the ActorRegistry using the given TKey.
public static AkkaConfigurationBuilder WithSingletonProxy<TKey>(
this AkkaConfigurationBuilder builder,
string singletonName,
ClusterSingletonOptions options = null,
string singletonManagerPath = null);
Type Parameters
TKeyThe key type to use for the
ActorRegistry.
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
singletonNamestringThe name of this singleton instance. Will also be used in the
ActorPathfor theClusterSingletonManagerand optionally, theClusterSingletonProxycreated by this method.optionsClusterSingletonOptionsOptional. The set of options for configuring the
ClusterSingletonProxy.singletonManagerPathstringOptional. By default Akka.Hosting will assume the
ClusterSingletonManageris hosted at "/user/{singletonName}" - but if for some reason the path is different you can use this property to override that value.
WithClusterClientReceptionist Method
Configures a Cluster Client ClusterClientReceptionist for the ActorSystem
public static AkkaConfigurationBuilder WithClusterClientReceptionist(
this AkkaConfigurationBuilder builder,
string name = "receptionist",
string role = null);
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
namestring
Actor name of the ClusterReceptionist actor under the system path, by default it is "/system/receptionist"
rolestring
Checks that the receptionist only start on members tagged with this role. All members are used if set to null.
WithClusterClient Method
Creates a Cluster Client and adds it to the ActorRegistry using the given TKey.
Overloads
public static AkkaConfigurationBuilder WithClusterClient<TKey>(
this AkkaConfigurationBuilder builder,
IList<ActorPath> initialContacts);
public static AkkaConfigurationBuilder WithClusterClient<TKey>(
this AkkaConfigurationBuilder builder,
IEnumerable<Address> initialContactAddresses,
string receptionistActorName = "receptionist");
public static AkkaConfigurationBuilder WithClusterClient<TKey>(
this AkkaConfigurationBuilder builder,
IEnumerable<string> initialContacts);
Parameters
builderAkkaConfigurationBuilderThe builder instance being configured.
initialContactsIList<ActorPath>, IEnumerable<string>List of
ClusterClientReceptionistactor path inActorPathorstringform that will be used as a seed to discover all of the receptionists in the cluster.initialContactAddressesIEnumerable<Address>List of node addresses where the
ClusterClientReceptionistare located that will be used as seed to discover all of the receptionists in the cluster.receptionistActorNamestringThe name of the
ClusterClientReceptionistactor. Defaults to "receptionist"
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Akka.Cluster.Sharding (>= 1.6.0-beta8)
- Akka.DistributedData (>= 1.6.0-beta8)
- Akka.Persistence.Hosting (>= 1.6.0-beta8)
- Akka.Remote.Hosting (>= 1.6.0-beta8)
NuGet packages (21)
Showing the top 5 NuGet packages that depend on Akka.Cluster.Hosting:
| Package | Downloads |
|---|---|
|
Aaron.Akka.Reminders
Durable, re-entrant reminders system for Akka.Cluster.Sharding. |
|
|
Aaron.Akka.Reminders.Sqlite
SQLite storage implementation for Akka.Reminders. |
|
|
Akka.Coordination.Azure
Akka.NET coordination module for Microsoft Azure |
|
|
Akka.Coordination.KubernetesApi
Akka.NET coordination module for Kubernetes |
|
|
FAkka.Shared
Package Description |
GitHub repositories (3)
Showing the top 3 popular GitHub repositories that depend on Akka.Cluster.Hosting:
| Repository | Stars |
|---|---|
|
petabridge/akkadotnet-code-samples
Akka.NET professional reference code samples
|
|
|
Aaronontheweb/InMemoryCQRSReplication
Akka.NET Reference Architecture - CQRS + Sharding + In-Memory Replication
|
|
|
petabridge/DrawTogether.NET
Multi-player MS Paint application. Built with Akka.NET, Blazor, and .NET Aspire.
|
| Version | Downloads | Last Updated |
|---|---|---|
| 1.6.0-beta8 | 0 | 11/18/2026 |
| 1.6.0-beta7 | 1,678 | 11/10/2026 |
| 1.6.0-beta6 | 357 | 11/7/2026 |
| 1.6.0-beta5 | 1,982 | 11/4/2026 |
| 1.6.0-beta4 | 278 | 10/28/2026 |
| 1.6.0-beta3 | 486 | 10/7/2026 |
| 1.6.0-beta2 | 131 | 10/6/2026 |
| 1.6.0-beta1 | 128 | 10/2/2026 |
| 1.5.75 | 314 | 11/16/2026 |
| 1.5.74 | 5,986 | 11/5/2026 |
| 1.5.73 | 40,179 | 10/5/2026 |
| 1.5.72 | 1,859 | 10/3/2026 |
| 1.5.71 | 34,579 | 8/27/2026 |
| 1.5.70 | 123,864 | 7/3/2026 |
| 1.5.69 | 32,939 | 6/15/2026 |
| 1.5.68 | 31,873 | 5/19/2026 |
| 1.5.67 | 45,667 | 4/26/2026 |
| 1.5.65 | 11,628 | 4/10/2026 |
| 1.5.64 | 7,999 | 3/31/2026 |
| 1.5.63 | 10,701 | 3/23/2026 |
Akka.NET 1.6.0-beta8 adds TLS certificate rotation without a restart on both DotNetty and Artery, brings Akka.Reminders into the repository, and fixes a PersistAll completion bug plus two recurring-reminder ordering bugs. Read the [v1.6 getting started guide](https://github.com/akkadotnet/akka.net/blob/dev/GETTING_STARTED_V1.6.md) for the full upgrade path.
**Akka.IO / TLS**
* `TlsCertificateSource` picks the certificate a node presents from a folder, a certificate store by common name, or a callback, and picks up a renewed certificate without a restart. A folder or store source is re-read in the background at most once every 10 seconds and the result is reused in between; a callback is called every time. Startup waits for the first look-up, and a source with nothing usable throws `ConfigurationException` so the node never binds. A connection that cannot get a certificate fails alone and the node stays up. ([#8966](https://github.com/akkadotnet/akka.net/pull/8966), relates to [#7663](https://github.com/akkadotnet/akka.net/issues/7663))
* Certificate errors are logged at most once a minute per cause, so one bad certificate does not log a Warning for every connection. DotNetty and Artery now share `Akka.IO.TlsCertificateRotation` for that limiter, the startup check and the one-minute poll interval, but each transport keeps its own instance so one transport never hides another's errors. ([#8982](https://github.com/akkadotnet/akka.net/pull/8982))
* On Artery's provider path, a failed certificate look-up now surfaces as an internal `TlsCertificateUnavailableException` that wraps the original cause, instead of writing a flag into the caller's own exception object. The only visible difference is one more `--->` level in the stack trace of Akka.Streams' "Restarting graph due to failure." warning. Fixed-certificate TLS and DotNetty are unaffected. ([#8982](https://github.com/akkadotnet/akka.net/pull/8982))
**Akka.Remote / DotNetty**
* DotNetty TLS certificates now rotate without a restart. `DotNettySslSetup.FromSource`, the HOCON keys `certificate.common-name` and `certificate.path` (a folder), `SslOptions.CertificateSource` and `SslCertificateOptions.CommonName` wire a `TlsCertificateSource` into the transport and Akka.Hosting. ([#8967](https://github.com/akkadotnet/akka.net/pull/8967))
* Artery rotates TLS certificates through the same `TlsCertificateSource`. Three new factories on `ArteryTlsSettings` - `Mutual(TlsCertificateSource, TlsPeerPolicy)`, a two-policy `Mutual` overload, and `ServerOnly(TlsCertificateSource, TlsPeerPolicy)` - take a source, and the node asks it for a certificate each time it builds a connection. Akka.Remote.Hosting needs no new API: `ArteryRemoteOptions.Tls` takes the profile. A startup look-up with nothing usable throws `ConfigurationException` and the node never binds, and a connection that cannot get a certificate fails alone while the node stays up. ([#8979](https://github.com/akkadotnet/akka.net/pull/8979), relates to [#7663](https://github.com/akkadotnet/akka.net/issues/7663))
* **Behavior change:** `SslOptions.CustomValidator` now runs when the certificate comes from `SslOptions.CertificateOptions` (a file `Path` or a `Thumbprint`). It used to run only with `SslOptions.X509Certificate`; with the other two it was silently ignored, so a security check you configured never ran. A validator that was ignored can now fail a TLS handshake, and on the dialing side a failed handshake shuts the `ActorSystem` down. With `EnableSsl = true`, a `CustomValidator` and no certificate in the options, `WithRemoting` now throws `ConfigurationException`. The certificate also loads when `WithRemoting` runs rather than when the `ActorSystem` starts, so a missing file or thumbprint fails earlier. See the [v1.6 breaking-change ledger](https://github.com/akkadotnet/akka.net/blob/dev/BREAKING_CHANGES_V1.6.md). ([#8964](https://github.com/akkadotnet/akka.net/pull/8964))
**Akka.Reminders (new module)**
* Akka.Reminders now ships from this repository as `Akka.Reminders` and its storage packages, replacing the standalone `Aaron.Akka.Reminders` packages. It provides durable, re-entrant reminders for Akka.Cluster.Sharding with SQL Server, PostgreSQL, SQLite and in-memory storage, a cluster-singleton scheduler, and Akka.Hosting integration. **Migration:** the package ID changed, so update your `PackageReference` and namespaces. ([#8946](https://github.com/akkadotnet/akka.net/pull/8946))
* Opt-in retry-until-acknowledged delivery: a reminder can require an explicit acknowledgement before it counts as delivered, with exponential backoff between attempts. The policy is persisted in all four storage backends, and existing signatures and default-policy wire layouts are unchanged. Opted-in schedules, responses and listings use versioned manifests, so **upgrade every potential scheduler host and policy-message reader before enabling the feature** - older schedulers must not take over while opted-in rows exist. Manual migration scripts for each provider live in `src/contrib/reminders/docs/migrations/retry-policy/`, and every provider and potential scheduler host must be recreated after migrating because schema capabilities are cached. ([#8973](https://github.com/akkadotnet/akka.net/pull/8973))
* An early send of a recurring reminder now ends every older live occurrence atomically with the newer delivery, suppresses those rows for the rest of the fetch pass, and prevents a stale row from writing them back as Pending. Previously only the previous occurrence was ended, so a series with an interval below `MaxSlippage` could deliver stale occurrences after a newer one during a shard-region outage. ([#8971](https://github.com/akkadotnet/akka.net/pull/8971), [#8976](https://github.com/akkadotnet/akka.net/pull/8976), fixes [#8965](https://github.com/akkadotnet/akka.net/issues/8965))
* That cleanup is capped at 256 older occurrences per send, nearest first. A 1 ms interval would otherwise put thousands of expiries in one commit, and a sub-millisecond interval could put millions into the scheduler's memory. Below roughly a 20 ms interval at the default 5 s `MaxSlippage`, an older occurrence more than 256 intervals back can still be delivered after a newer one during a shard-region outage. ([#8975](https://github.com/akkadotnet/akka.net/pull/8975), [#8976](https://github.com/akkadotnet/akka.net/pull/8976))
**Akka**
* `Unwatch` now clears the sole watcher from an optimized actor state. `DefaultActorState.RemoveWatchedBy` never cleared its optimized slot, so a target kept a reference to an actor that had unwatched it. `FullActorState` already removed watchers correctly. No public API or wire-format change. ([#8936](https://github.com/akkadotnet/akka.net/pull/8936))
**Akka.Persistence**
* The `PersistAll` completion callback no longer runs when the journal rejects the batch. `OnPersistRejected` fired for each event and then the completion callback ran anyway, so a handler saw a completion for a batch that was never persisted. This affected all eight `PersistAll`/`PersistAllAsync` overloads. Journal write failures are unchanged: the actor stops before the completion's message is processed. ([#8949](https://github.com/akkadotnet/akka.net/pull/8949), fixes [#8948](https://github.com/akkadotnet/akka.net/issues/8948))
**Akka.Remote / Artery**
* Artery's inbound stage now reports a framing error when a peer closes after a partial connection preamble, frame length or frame body, instead of silently completing the connection. Empty connections and complete frame boundaries still close cleanly, and cancellation and upstream failure keep their existing semantics. Artery is new in v1.6, so this changes unreleased behavior only. ([#8956](https://github.com/akkadotnet/akka.net/pull/8956))
**Serialization**
* Native module replacements can preserve legacy serializer type names through an optional type-alias map, so a ported serializer keeps reading data written under the original assembly-qualified name. Each declared name resolves to an existing module row using the declared type's assembly simple name and the existing strict name-matching rules; subclasses are not matched. Missing or ambiguous aliases, non-serializer types and conflicting registrations are rejected. No serializer rows, ids or configuration switches are added. ([#8920](https://github.com/akkadotnet/akka.net/pull/8920))
**Akka.Hosting**
* `Akka.Hosting`, `Akka.Cluster.Hosting`, `Akka.Remote.Hosting`, `Akka.Persistence.Hosting` and `Akka.Persistence.Embedded.Hosting` now ship their own module READMEs on nuget.org instead of the generic Akka.NET one. Relative links were rewritten to absolute GitHub permalinks because nuget.org cannot resolve relative paths. ([#8945](https://github.com/akkadotnet/akka.net/pull/8945))
**Docs**
* New [TLS certificate rotation](https://github.com/akkadotnet/akka.net/blob/dev/docs/articles/remoting/certificate-rotation.md) article covers folder, store and callback sources, when a renewed certificate is used, what happens when a look-up finds nothing usable, and the error-logging behavior. Both the DotNetty transport and Artery rotate certificates the same way. ([#8968](https://github.com/akkadotnet/akka.net/pull/8968), relates to [#7663](https://github.com/akkadotnet/akka.net/issues/7663))
**Internal**
* `MultiNodeSpec` now terminates a replacement actor system when initialization fails, including on caller cancellation, and preserves the original exception. ([#8955](https://github.com/akkadotnet/akka.net/pull/8955))
* `RemotePingPong` validates delivery and compares authenticated TCP, and measures latency at a scheduled offered load with per-run reporting that separates generator lateness, dispatch delay, send-to-echo and scheduled-to-echo latency. ([#8953](https://github.com/akkadotnet/akka.net/pull/8953), [#8957](https://github.com/akkadotnet/akka.net/pull/8957))
* Artery's DeathWatch ACK-loss test now witnesses TCP system-message retries by counting dropped ACKs per peer UID and cumulative sequence. ([#8954](https://github.com/akkadotnet/akka.net/pull/8954))
* `ShardedDaemonProcessSpecs` waits for sharded daemon restarts with one overall deadline instead of back-to-back 3-second waits, fixing a Windows CI timeout. ([#8981](https://github.com/akkadotnet/akka.net/pull/8981))
* Slopwatch upgraded to 0.5.0 with a regenerated schema-v2 baseline. ([#8980](https://github.com/akkadotnet/akka.net/pull/8980))
* The Serialization V2 port-comparison test kit now compares the root message's members in its structural fallback and checks the exact runtime type before the equality fast path, and supports shared system names. Test-only; no production API, bindings or wire bytes change. ([#8916](https://github.com/akkadotnet/akka.net/pull/8916))
1 contributor since release 1.6.0-beta7
| COMMITS | LOC+ | LOC- | AUTHOR |
|---------|------|------|-----------------|
| 22 | 44500 | 1088 | Aaron Stannard |