Bot releases are hidden (Show)
Published by sergeybykov about 4 years ago
This release includes improvements to give developers additional context when a request does not return promptly. PR #6672 added these improvements. Orleans will periodically probe active grains to inspect their message queues and send status updates for certain requests which have been enqueued or executing for too long. These status messages will appear as warnings in the logs and will also be included in exceptions when a request timeout occurs. The information included can help a developer to identify what the grain is doing at the time of the request. For example, which messages are enqueued ahead of this message, and which messages are executing, how long they have been executing, how long this message has been enqueued, and the status of the grain's TaskScheduler
.
This release adds a new pre-release package, Microsoft.Orleans.Hosting.Kubernetes
, which adds richer integration for users hosting on Kubernetes. The package assists users by monitoring Kubernetes for silo pods and reflecting changes in cluster membership. For example, when a Pod is deleted, it is immediately removed from Orleans' membership. In addition, the package configures EndpointOptions
and `ClusterOptions' to match the Pod's environments. Documentation and a sample project are expected in the coming weeks, and in the meantime, please see the original PR for more information: #6707.
Potentially breaking change
IStorage<TState>
and IGrainState
need to be updated to add a RecordExists property.)Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov about 4 years ago
Improvements and bug fixes since 3.3.0-rc1.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov about 4 years ago
Improvements and bug fixes since 3.2.2.
This release includes improvements to give developers additional context when a request does not return promptly. PR #6672 added these improvements. Orleans will periodically probe active grains to inspect their message queues and send status updates for certain requests which have been enqueued or executing for too long. These status messages will appear as warnings in the logs and will also be included in exceptions when a request timeout occurs. The information included can help a developer to identify what the grain is doing at the time of the request. For example, which messages are enqueued ahead of this message, and which messages are executing, how long they have been executing, how long this message has been enqueued, and the status of the grain's TaskScheduler
.
Published by sergeybykov about 4 years ago
Improvements and bug fixes since 3.2.1.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.2.0.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
This feature allows to use external storage as an option for keeping grain directory information. Directory plugins can be configured for different grain classes independently, so that different consistency/availability tradeoffs can be made for different grain classes.
As part of this change, we had to remove support for multi-cluster functionality. We intend to bring it back as a grain directory plugin at a later time. Removal of multi-clustering is the only breaking change, and only if you used the feature previously.
Since the initial release, Orleans has been using its own custom thread pool implementation to make up for the deficiencies in the .NET thread pool. Since then, the .NET thread pool has improved significantly, and there is no need any more for a separate solution within Orleans.
We measured a performance increase of 3.2.0 compared to 3.1.6 of 12% to 20% depending on the test scenario.
Other improvements and bug fixes since 3.1.0.
Breaking changes
Non-breaking improvements
READ COMMITTED
to avoid Gap Lock issues (#6331)Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.2.0-rc2
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.1.6.
Published by sergeybykov over 4 years ago
This feature allows to use external storage as an option for keeping grain directory information. Directory plugins can be configured for different grain classes independently, so that different consistency/availability tradeoffs can be made for different grain classes.
As part of this change, we had to remove support for multi-cluster functionality. We intend to bring it back as a grain directory plugin at a later time. Removal of multi-clustering is the only breaking change, and only if you used the feature previously.
Since first version, Orleans has been using its own custom thread pool implementation to make up for the deficiencies in the .NET thread pool. Since then, the .NET thread pool has improved significantly, and there is no need any more for a separate solution within Orleans.
We measured a performance increase of 3.2.0-rc1 compared to 3.1.6 of 12% to 20% depending on the test scenario.
Other improvements and bug fixes since 3.1.6.
Breaking changes
Non-breaking improvements
READ COMMITED
to avoid Gap Lock issues (#6331)Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.1.5.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.1.4.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.1.3.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
This release fixes the partial backward compatibility regression introduced in 3.1.0. See #6392 for more details.
If your application targets .NET Core 3.1, rolling upgrade to 3.1.3 can be performed from all versions except for 3.1.0 and 3.1.2
For all other .NET versions, there are no known compatibility issues with rolling upgrades to 3.1.3
Improvements and bug fixes since 3.1.2.
Breaking changes (for rolling upgrades from 3.1.0 and 3.1.2 running on .NET Core 3.1)
Non-breaking improvements
Published by sergeybykov over 4 years ago
Known issue:
We discovered a partial backward compatibility regression in this release. If your application targets .NET Core 3.1, a rolling upgrade from previous versions to 3.1.2 will fail. See #6392 for more details. The regression is fixed in 3.1.3.
Improvements and bug fixes since 3.1.0.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Known issue:
We discovered a partial backward compatibility regression in this release. If your application targets .NET Core 3.1, a rolling upgrade from previous versions to 3.1.0 will fail. See #6392 for more details. The regression is fixed in 3.1.3.
Improvements and bug fixes since 3.0.0.
In this release we enabled multi-targeting, nestandard2.0
and netcoreapp3.1
, for Microsoft.Orleans.Core
, Microsoft.Orleans.OrleansRuntime
, and Microsoft.Orleans.Connections.Security
packages to leverage some performance features available in netcoreapp3.1
.
Microsoft.Orleans.OrleansCodeGenerator.Build
package has been marked as deprecated in favor of Microsoft.Orleans.CodeGenerator.MSBuild
. We don't plan future releases of Microsoft.Orleans.OrleansCodeGenerator.Build
.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.1.0-rc2.
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.1.0-rc1.
In this release we enabled multi-targeting, nestandard2.0
and netcoreapp3.1
, for Microsoft.Orleans.Core
, Microsoft.Orleans.OrleansRuntime
, and Microsoft.Orleans.Connections.Security
packages to leverage some performance features available in netcoreapp3.1
.
Published by sergeybykov over 4 years ago
Improvements and bug fixes since 3.0.2.
In this release we enabled multi-targeting, nestandard2.0
and netcoreapp3.1
, for Microsoft.Orleans.Core
, Microsoft.Orleans.OrleansRuntime
, and Microsoft.Orleans.Connections.Security
packages to leverage some performance features available in netcoreapp3.1
.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov almost 5 years ago
Improvements and bug fixes since 2.4.4.
Non-breaking improvements
Non-breaking bug fixes
Published by sergeybykov almost 5 years ago
Improvements and bug fixes since 3.0.1.
Non-breaking improvements
Non-breaking bug fixes