FailoverTestScenarioParameters Class
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Caution
FailoverTestScenario and FailoverTestScenarioParameters are deprecated. Please use Chaos instead https://docs.microsoft.com/azure/service-fabric/service-fabric-controlled-chaos
This class defines all the test parameters to configure the FailoverTestScenario.
[System.Obsolete("FailoverTestScenario and FailoverTestScenarioParameters are deprecated. Please use Chaos instead https://docs.microsoft.com/azure/service-fabric/service-fabric-controlled-chaos")]
[System.Serializable]
public class FailoverTestScenarioParameters : System.Fabric.Testability.Scenario.TestScenarioParameters
[<System.Obsolete("FailoverTestScenario and FailoverTestScenarioParameters are deprecated. Please use Chaos instead https://docs.microsoft.com/azure/service-fabric/service-fabric-controlled-chaos")>]
[<System.Serializable>]
type FailoverTestScenarioParameters = class
inherit TestScenarioParameters
Public Class FailoverTestScenarioParameters
Inherits TestScenarioParameters
- Inheritance
- Attributes
Constructors
FailoverTestScenarioParameters(PartitionSelector, TimeSpan, TimeSpan) |
Constructor for the FailoverTestScenarioParameters. |
Properties
MaxServiceStabilizationTimeout |
The maximum amount of time to wait for the service to stabilize after a fault before failing the test. |
PartitionSelector |
The PartitionSelector which gives the partition that needs to be targeted for the test. |
TimeToRun |
Total time for which the scenario will run before ending. (Inherited from TestScenarioParameters) |
WaitTimeBetweenFaults |
The maximum wait time between consecutive faults: the larger the value, the lower the concurrency (of faults). (Inherited from TestScenarioParameters) |
Applies to
Azure SDK for .NET
Feedback
https://aka.ms/ContentUserFeedback.
Binnenkort beschikbaar: In de loop van 2024 zullen we GitHub-problemen geleidelijk uitfaseren als het feedbackmechanisme voor inhoud en deze vervangen door een nieuw feedbacksysteem. Zie voor meer informatie:Feedback verzenden en weergeven voor