p4 servers

Display list of all server specifications or evaluate replication status.

A user with operator privileges can execute p4 servers and p4 servers -J.

Syntax

p4 [g-opts] servers [-J | --replication-status]

Syntax conventions

Description

Syntax variants are described in the following subsections.

Listing server specifications

p4 servers lists all server specifications stored at a central server The one server that is innermost in a multi-server deployment. In the server specification form field for Services, the central server might be specified as “standard” or “commit-server”. If edge servers are part of the multi-server deployment, the central server must be a commit server. See also 'upstream server'. .

edge-server_1 server edge-server_1 10.0.101.55:41261 edge-server 'edge-server '
edge-server_2 server edge-server_2 10.0.101.55:47050 edge-server 'edge-server '

Output lists the server ID, the type, the services provided, and the description supplied when the server was created.

The output of p4 servers is easier to parse if you retrieve it in tagged form by including the -ztag option (see Global options):

p4 -ztag servers

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
... ServerID commit-1... Name... Address... Type server
... Services commit-server
... Options nomandatory
... Description commit-1
... ServerID edge-server-1
... Name
... Address
... Type server
... Services edge-server
... Options nomandatory
... Description edge-server-1

... ServerID edge-server-2
... Name
... Address
... Type server
... Services edge-server
... Options nomandatory
... Description edge-server-2

... ServerID remote-standby
... Name
... Address
... Type server
... Services standby
... Options nomandatory
... ReplicatingFrom commit-1

... Description Remote DR server
... ServerID standby-1
... Name
... Address
... Type server
... Services standby
... Options mandatory
... ReplicatingFrom commit-1
... Description Local HA server

The Options and ReplicationFrom fields that appear in tagged output (line 26-27 and 35-36) are related to the failover feature. To learn more, see p4 failover.

Evaluating replication status

Using the -J or --replication-status option allows you to check how efficiently one or more replicas are replicating the target server’s records. Given a server A and a replica B, output for this command gives you two basic pieces of information:

• The size and update time of A's journal.
• For every server, B, that has sent a p4 pull or p4 journalcopy request, information is given as to when that request was sent and what is the persisted and applied state of B's journal. (In the case of a simple target server and replica, the persisted and applied numbers are always the same: B's journal is updated by the p4 pull command.

This assumes that the command is executed with the target server as the target. A standby server can replicate target server records using two operations:

• It uses the p4 journalcopy command to copy (persist) the target server’s journal to the standby’s journal.
• It uses the p4 pull -L command to apply the copied journal records to the standby’s database and to update its state file.

You can look at the output to evaluate the load on various parts of your multi-server system and to see how well your replicas are keeping up with the target server. Growing lag times might be a reason for concern.

The untagged output of p4 servers -J looks like this:

edge-server_1 '2014/09/18 13:14:58' edge-server 5/258 5/258 WaDl/10 1
edge-server_2'2014/09/18 13:14:57' edge-server 5/258 5/258 WaDl/10 1

It is easier to interpret this output in tagged form:

... ServerID edge-server_1
... Updated 2014/09/18 13:14:58
... ServerType edge-server
... PersistedJournal 5
... PersistedSequence 258
... AppliedJournal 5
... AppliedSequence 258
... JAFlags WaDl/10 1
... IsAlive 1

... ServerID edge-server_2
... Updated 2014/09/18 13:14:57
... ServerType edge-server
... PersistedJournal 5
... PersistedSequence 258
... AppliedJournal 5
... AppliedSequence 258
... JAFlags WaDl/10 1
... IsAlive 1

Form fields

Pull or journal-copy requests are recorded in the db.jnlack table only if they are made from a replica that has a serverID (or a P4NAME, which is deprecated).

Options

Usage notes

Related commands