server (Batch Commits)
Syntax
server {
commit-intervalnumber-of-seconds-between-commits;
commit-schedule-profile;
days-to-keep-error-logsdays-to-keep-error-log-entries;
maximum-aggregate-poolmaximum-number-of-commits-to-aggregate;
maximum-entries number-of-entries;
redirect-completion-status;
retry-attempts;
retry-interval;
traceoptions {
file filename;
files number;
flag (all | batch | commit-server | configuration);
size maximum-file-size;
(world-readable | no-world-readable);
}
}
Hierarchy Level
[edit system commit]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Configure the system commit to occur in batches. Configure parameters for aggregating and saving batch commits.
Options
| commit-interval | Configure the interval in seconds between commits. |
| days-to-keep-error-logs | Configure the number of days to keep log entries. Valid range is from 1 to 366 days. |
| maximum-aggregate-pool | Configure the maximum number of commits to aggregate together. The valid range is 1 through 4294967295. |
| maximum-entries | Configure the maximum number of commit entries. |
| redirect-completion-status | Configure the redirect asynchronous commit status to server configured here. |
| retry-attempts | Configure the retry attempts for commit failure due to db lock error. The default is 5 retries. |
| retry-interval | Configure the retry interval in seconds for commit failure. The default is 20 seconds. |
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 12.1.