public class StopSchedulingOrder extends SchedulingOrder
When a client throws this, master will quit scheduling tasks and wait for currently executing tasks to finish, then go on to do any closetasks and endtasks. No error is reported.
For example, suppose a test wants to run until it has put 2GB of data into a region, but the data used in the test is random and its size is hard to pin down. The test can monitor the region and throw this exception when the condition is reached. Task granularity can be finer, with a small maxResultWaitSec, and totalTaskTimeSec can be very large to ensure that the test doesn't terminate before the 2GB goal is reached.
| Constructor and Description |
|---|
StopSchedulingOrder() |
StopSchedulingOrder(String s) |
getOrigin, getRootCause, setOriginaddSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toStringpublic StopSchedulingOrder()
public StopSchedulingOrder(String s)
Copyright © 2010-2015 Pivotal Software, Inc. All rights reserved.