- Update Akka.NET to 1.5.30
- Make sure that any exceptions thrown during start-up are logged and stops the application
Note
Deprecated
Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.
- Update Akka.NET to 1.5.29
- Make sure that any exceptions thrown during start-up are logged and stops the application
- Update Akka.NET to 1.5.27.1
- Fix only the last ShardOptions were applied
- Add ClusterClientDiscovery support
Note
We added support for cluster client initial contact discovery feature in this feature. To use this feature, you will need to use Akka.Management v1.5.27 or higher.
- Update Akka.NET to 1.5.25, which resolves a critical bug: Akka.Logging: v1.5.21 appears to have truncated log source, timestamps, etc from all log messages
You can now start ShardedDaemonProcess
host and proxy using Akka.Hosting through 2 new Akka.Cluster.Hosting extension methods
public static AkkaConfigurationBuilder WithShardedDaemonProcess<TKey>(
this AkkaConfigurationBuilder builder,
string name,
int numberOfInstances,
Func<ActorSystem, IActorRegistry, IDependencyResolver, Func<int, Props>> entityPropsFactory,
ClusterDaemonOptions? options = null)
public static AkkaConfigurationBuilder WithShardedDaemonProcessProxy<TKey>(
this AkkaConfigurationBuilder builder,
string name,
int numberOfInstances,
string role)
Filtering Logs In Akka.NET
In Akka.NET 1.5.21, we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style, you can use this feature in Akka.Hosting in several ways.
-
Using The
LoggerConfigBuilder.WithLogFilter()
method.The
LoggerConfigBuilder.WithLogFilter()
method lets you set up theLogFilterBuilder
builder.Services.AddAkka("MyActorSystem", configurationBuilder => { configurationBuilder .ConfigureLoggers(loggerConfigBuilder => { loggerConfigBuilder.WithLogFilter(filterBuilder => { filterBuilder.ExcludeMessageContaining("Test"); }); }); });
-
Setting the
loggerConfigBuilder.LogFilterBuilder
property directly.builder.Services.AddAkka("MyActorSystem", configurationBuilder => { configurationBuilder .ConfigureLoggers(loggerConfigBuilder => { loggerConfigBuilder.LogFilterBuilder = new LogFilterBuilder(); loggerConfigBuilder.LogFilterBuilder.ExcludeMessageContaining("Test"); }); });
- Update Akka.NET to 1.5.20
- Added improved APIs for setting default
ILogMessageFormatter
s - theLoggerConfigBuilder.WithDefaultLogMessageFormatter<T>
method.
- Update Akka.NET to 1.5.15
- Marked all Akka.Cluster.Hosting methods that accept deprecated sharding delegates as
Obsolete
- Update Akka.NET to 1.5.14
- Akka.Cluster.Hosting: don't use sharding delegates
- Akka.Hosting.TestKit: Add method to configure
IHostBuilder
- Add IConfiguration to HOCON adapter key name normalization toggle flag
- Expand Cluster.Hosting and Remote.Hosting options
You can now specify whether IConfiguration key strings should be normalized to lower case or not when they are being converted into HOCON keys. You can read the documentation here
- Update Akka.NET to 1.5.12
- TestKit: Fix missing actor context on test start
- Remote: Add SSL settings into RemoteOptions
- Update Akka.NET to 1.5.8
- [Akka.Cluster.Hosting] PassivateEntityAfter should not override HOCON settings
- [Akka.Hosting] Set application exit code to -1 if CoordinatedShutdown was caused by cluster down or leave
- Akka.Hosting now throws
PlatformNotSupportedException
when attempting to run on Maui, due to dotnet/maui#2244. Maui support will be added in https://github.com/akkadotnet/Akka.Hosting.Maui - make
AkkaHostedService
public
+virtual
so it can be extended and customized - advanced feature.
- Update Akka.NET to 1.5.4
- Update Akka.Persistence.SqlServer to 1.5.4
- Update Akka.Persistence.PostgreSql to 1.5.4
SQL Transaction Isolation Level Setting
In 1.5.3, we're introducing fine-grained control over transaction isolation level inside the Akka.Persistence.Hosting
, Akka.Persistence.SqlServer.Hosting
, and Akka.Persistence.PostgreSql.Hosting
plugins.
you can go to the official Microsoft documentation to read more about these isolation level settings.
- Update Akka.NET to 1.5.2
- Bump Akka.Persistence.PostgreSql to 1.5.2
- Bump Akka.Persistence.SqlServer to 1.5.2
- Persistence: Change persistence default serializer from json to null
Major Changes
- Persistence.Hosting default value for default serializer has been changed from
json
tonull
. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated, you will need to change this setting.
Inherited Changes From Akka.NET Core
- Persistence will now ignore the
serializer
setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated. - Cluster.Hosting, by default, will have
SplitBrainResolver
enabled.
- Update Akka.NET to 1.5.1
- Bump Akka.Persistence.PostgreSql to 1.5.1
- Bump Akka.Persistence.SqlServer to 1.5.1
- Add GetAsync method to
IRequiredActor
to resolve IActorRef in background services - Add cluster Distributed Data options support for Akka.Cluster.Hosting extensions
Version 1.5.0 is the RTM release of Akka.Hosting and Akka.NET v1.5.0 RTM integration.
Full changes
- Update Akka.NET to 1.5.0
- Fix missing cluster configuration on certain edge cases
- Add new Cluster.Sharding RememberEntitiesStore
- Add Cluster.Sharding journal migration adapter convenience method
- Add LogMessageFormatter formatter support to logging
As noted in the upgrade advisories, there was some major changes inside Akka.NET that directly affects Akka.Hosting. To upgrade from v1.4 to v1.5, please watch our video here covering this process.