X-Git-Url: https://git.octo.it/?p=rrdtool.git;a=blobdiff_plain;f=doc%2Frrdcached.pod;h=5113c2d521e9f7767a7221c4cb58cde834231dea;hp=b01165e81437df6ffde8a41d1c4b7b8e8f3a8419;hb=bf67cc26d0b43871039259add067aa1ed6f0758f;hpb=db9842391d7f238faf7b5ad1b01059115a4f2264 diff --git a/doc/rrdcached.pod b/doc/rrdcached.pod index b01165e..5113c2d 100644 --- a/doc/rrdcached.pod +++ b/doc/rrdcached.pod @@ -6,7 +6,17 @@ rrdcached - Data caching daemon for rrdtool =head1 SYNOPSIS -B [B<-l/-L> I
] [B<-w> I] [B<-z> I] [B<-f> I] [B<-j> I] [-F] [B<-b> I [B<-B>]] +B +[B<-l/-L>EI
] +[B<-w>EI] +[B<-z>EI] +[B<-f>EI] +[B<-p>EI] +[B<-t>EI] +[B<-j>EI] +[-F] +[-g] +[B<-b>EIE[B<-B>]] =head1 DESCRIPTION @@ -81,6 +91,13 @@ cases. This timeout defaults to 3600Eseconds. Sets the name and location of the PID-file. If not specified, the default, C/run/rrdcached.pid> will be used. +=item B<-t> I + +Specifies the number of threads used for writing RRD files. The default +isE4. Increasing this number will allow rrdcached to have more +simultaneous I/O requests into the kernel. This may allow the kernel to +re-order disk writes, resulting in better disk throughput. + =item B<-j> I Write updates to a journal in I. In the event of a program or system @@ -107,6 +124,10 @@ To disable fast shutdown, use the B<-F> option. ALWAYS flush all updates to the RRD data files when the daemon is shut down, regardless of journal setting. +=item B<-g> + +Run in the foreground. The daemon will not fork(). + =item B<-b> I The daemon will change into a specific directory at startup. All files passed @@ -125,6 +146,18 @@ used. updated by the daemon, assuming the base directory "/tmp". +B The paths up to and including the base directory B +symbolic links. In other words, if the base directory is +specified as: + + -b /base/dir/somewhere + +... then B of the following should be symbolic links: + + /base + /base/dir + /base/dir/somewhere + =item B<-B> Only permit writes into the base directory specified in B<-b> (and any @@ -173,7 +206,7 @@ The daemon reports errors in one of two ways: During startup, error messages are printed to C. One of the steps when starting up is to fork to the background and closing C - after this writing directly to the user is no longer possible. Once this has happened, the daemon will send log messages -to the system logging daemon using L. The facility used it +to the system logging daemon using L. The facility used is C. =head1 HOW IT WORKS @@ -372,6 +405,14 @@ not yet been written to the underlying RRD file. Removes I from the cache. Any pending updates B. +=item B + +Shows the files that are on the output queue. Returns zero or more lines +in the following format, where Enum_valsE is the number of values +to be written for the EfileE: + + + =item B [I] Returns a short usage message. If no command is given, or I is @@ -409,6 +450,10 @@ Adds more data to a filename. This is B operation the daemon was designed for, so describing the mechanism again is unnecessary. Read L above for a detailed explanation. +Note that rrdcached only accepts absolute timestamps in the update values. +Updates strings like "N:1:2:3" are automatically converted to absolute +time by the RRD client library before sending to rrdcached. + =item B I This command is written to the journal after a file is successfully @@ -434,14 +479,18 @@ message itself. The first user command after B is command number one. client: BATCH server: 0 Go ahead. End with dot '.' on its own line. - client: UPDATE x.rrd N:1:2:3 <--- command #1 - client: UPDATE y.rrd N:3:4:5 <--- command #2 + client: UPDATE x.rrd 1223661439:1:2:3 <--- command #1 + client: UPDATE y.rrd 1223661440:3:4:5 <--- command #2 client: and so on... client: . server: 2 Errors server: 1 message for command 1 server: 12 message for command 12 +=item B + +Disconnect from rrdcached. + =back =head2 Performance Values @@ -469,10 +518,11 @@ daemon was started. =item B I<(unsigned 64bit integer)> -Total number of "data sets" written to disk since the daemon was started. A -data set is one or more values passed to the B command. For example: -C is one data set with two values. The term "data set" is used to -prevent confusion whether individual values or groups of values are counted. +Total number of "data sets" written to disk since the daemon was +started. A data set is one or more values passed to the B +command. For example: C<1223661439:123:456> is one data set with two +values. The term "data set" is used to prevent confusion whether +individual values or groups of values are counted. =item B I<(unsigned 64bit integer)>