public class InstanceConfig extends Object
Modifier and Type | Field and Description |
---|---|
static int |
DEFAULT_BACKUP_COUNT
The default value of the
backup-count |
static int |
DEFAULT_FLOW_CONTROL_PERIOD_MS
The default value of the
flow-control period . |
Constructor and Description |
---|
InstanceConfig() |
Modifier and Type | Method and Description |
---|---|
int |
getBackupCount()
Returns the
number of backups used for job
metadata and snapshots. |
int |
getCooperativeThreadCount()
Returns the number of cooperative execution threads.
|
int |
getFlowControlPeriodMs()
Returns the
flow-control period in
milliseconds. |
long |
getScaleUpDelayMillis()
Returns the scale-up delay, see
setScaleUpDelayMillis(long) . |
boolean |
isLosslessRestartEnabled()
Returns if lossless restart is enabled, see
setLosslessRestartEnabled(boolean) . |
InstanceConfig |
setBackupCount(int newBackupCount)
Sets the number of backups that Jet will maintain for the job metadata
and snapshots.
|
InstanceConfig |
setCooperativeThreadCount(int size)
Sets the number of threads each cluster member will use to execute Jet
jobs.
|
InstanceConfig |
setFlowControlPeriodMs(int flowControlPeriodMs)
While executing a Jet job there is the issue of regulating the rate
at which one member of the cluster sends data to another member.
|
InstanceConfig |
setLosslessRestartEnabled(boolean enabled)
Sets whether lossless job restart is enabled for the node.
|
InstanceConfig |
setScaleUpDelayMillis(long millis)
Sets the delay after which auto-scaled jobs will restart if a new member
is added to the cluster.
|
public static final int DEFAULT_FLOW_CONTROL_PERIOD_MS
flow-control period
.public static final int DEFAULT_BACKUP_COUNT
backup-count
@Nonnull public InstanceConfig setCooperativeThreadCount(int size)
public int getCooperativeThreadCount()
@Nonnull public InstanceConfig setFlowControlPeriodMs(int flowControlPeriodMs)
public int getFlowControlPeriodMs()
flow-control period
in
milliseconds.@Nonnull public InstanceConfig setBackupCount(int newBackupCount)
For example, if you set the backup count to 2, Jet will replicate all the job metadata and snapshot data to two other members. If one or two members of the cluster fail, Jet can recover the data from the snapshot and continue executing the job on the remaining members without loss.
public int getBackupCount()
number of backups
used for job
metadata and snapshots.public InstanceConfig setScaleUpDelayMillis(long millis)
millis
- the delay, in millisecondspublic long getScaleUpDelayMillis()
setScaleUpDelayMillis(long)
.public boolean isLosslessRestartEnabled()
setLosslessRestartEnabled(boolean)
.public InstanceConfig setLosslessRestartEnabled(boolean enabled)
If enabled, you have to also configure Hot Restart:
JetConfig jetConfig = new JetConfig();
jetConfig.getInstanceConfig().setLosslessRestartEnabled(true);
jetConfig.getHazelcastConfig().getHotRestartPersistenceConfig()
.setEnabled(true)
.setBaseDir(new File("/mnt/hot-restart"))
.setParallelism(2);
Note: the snapshots exported using Job.exportSnapshot(java.lang.String)
will also have Hot Restart storage enabled.
Feature is disabled by default. If you enable this option in open-source Hazelcast Jet, the member will fail to start, you need Jet Enterprise to run it and obtain a license from Hazelcast.
Copyright © 2019 Hazelcast, Inc.. All rights reserved.