What’s new in P4 Server administration in 2022.2

Released: May 2021

For a complete list of what’s new in this release, see the Release notes and What’s new in the Helix Core Command-Line (P4) Reference.

Parallel checkpointing

Support for Parallel checkpointing, dumping, and recovery.

Triggers

• Support for failback triggers and extensions. See Triggering on failed-back.

• Server triggers can use %serverprocesspid% for the process to complement %serverpid% for the thread. See Trigger script variables.

• A unique command identifier. See %commandIdent% in Trigger script variables (and Server extension session variables).

• Triggers can use the %maxOpenFiles% variable. See Trigger script variables (and Server extension session variables).

Structure logging

• Server log files now include an estimate of the memory used by a command. See "command-end" in Structured Log Events.

• A command group identifier that clients can use to tie multiple events to a single action for improved traceability. Requires using version 55 of the structured log schema. See Protocol for server and clients by release and Using structured logging.

• Server log support for tracking network stats for upstream server-to-server communication as well as with the client or downstream server. These stats are recorded as additional 'NetworkPerformance' events in the structured logs at version 55 (8.55). See track-rpc under Structured Log Events and the examples and explanations at Server-to-server network usage on replicas.

Additional enhancements

• On Windows Server 2016 and newer, journal rotation can be performed using an atomic rename instead of a copy and truncate operation. To enable this feature, see the filesys.atomic.rename configurable in the P4 CLI Reference.

• The -jr recovery command to p4d supports recalculating the net storage reference count change from the revision records. See -S under Journal restore options and the associated "Important" note.