Helix Core Server Administrator Guide: Multi-Site Deployment (2019.2)

How replica types handle requests

Replica servers differ in how they respond to user commands:

Replica type Global update commands Read-only commands Work-in-progress commands

Standby, replica

Reject

Local

Reject

Forwarding standby, forwarding replica

Forward

Local

Forward

Build server (for client creation and local sync)

p4 client

Local

p4 sync

Edge server

Forward

Local

Local

Standard server, commit server

Local

Local

Local

User requests fall into three categories, depending on the command and command options:

Global update Read-only Work-in-progress

p4 branch

p4 change

p4 configure set

p4 client

 

p4 counter

p4 depot

 

 

 

 

 

p4 group

 

p4 job

p4 label

 

p4 protect

p4 server

p4 stream

p4 triggers

p4 typemap

 

p4 user

 

p4 branches

p4 changes

p4 configure show

p4 client -o

p4 clients

p4 counters

p4 depots

p4 dirs

p4 filelog

p4 files

p4 fstat

p4 fixes

p4 groups

p4 interchanges

p4 jobs

p4 labels

p4 opened

 

p4 servers

p4 streams

 

 

p4 sizes

p4 user -o

p4 users

p4 where

p4 workspaces

p4 add

p4 edit

p4 delete

p4 diff

p4 integrate

p4 reconcile

p4 resolve

p4 revert

p4 shelve

p4 submit

p4 sync

p4 unshelve

 

 

 

Tip

For a more detailed summary of replica server types, see the Support Knowledgebase article "Replica Types and Use Cases".