.\" Man page generated from reStructuredText. . .TH "CLUSTER.CONFIG" "5" "Mar 22, 2017" "7.0" "Apache Traffic Server" .SH NAME cluster.config \- the cluster.config tracks Traffic Server cluster membership, allowing more than one server running Traffic Server to coordinate and either replicate or distribute cache operations . .nr rst2man-indent-level 0 . .de1 rstReportMargin \\$1 \\n[an-margin] level \\n[rst2man-indent-level] level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] - \\n[rst2man-indent0] \\n[rst2man-indent1] \\n[rst2man-indent2] .. .de1 INDENT .\" .rstReportMargin pre: . RS \\$1 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin] . nr rst2man-indent-level +1 .\" .rstReportMargin post: .. .de UNINDENT . RE .\" indent \\n[an-margin] .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]] .nr rst2man-indent-level -1 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. .sp For the contents of this file to reflect any clustering peers, Traffic Server clustering must first be enabled by adjusting \fBproxy.local.cluster.type\fP\&. .sp For information on how to enable and configure Traffic Server clustering, refer to the traffic\-server\-cluster section. .sp \fBDANGER:\fP .INDENT 0.0 .INDENT 3.5 The \fI\%cluster.config\fP configuration file is generated and managed by Traffic Server itself and should not be modified directly. .UNINDENT .UNINDENT .SH FORMAT .sp The format of \fI\%cluster.config\fP is simple. Lines beginning with \fB#\fP are comments and, as such, will be ignored by Traffic Server\&. The first non\-comment, non\-empty line is an integer indicating the number of Traffic Server cluster peers for the current node. If the current node is not a member of a cluster, this value will be \fB0\fP\&. .sp Following lines provide the \fB
: