Jump to content

Perforce Replication Issues

replication issues journal p4 pull compressed journal

  • Please log in to reply
2 replies to this topic

#1 vinodarokiya



  • Members
  • PipPip
  • 15 posts
  • LocationBangalore

Posted 10 July 2013 - 10:42 AM


I have configured Perforce Replication with all the configurations files and everything was fine,
unless Checkpoint backup was taken with the below command.

./p4d -J /mnt/Journal/journal  -jc -z /mnt2/Backup/Backup0fCheckpoint/checkpoint

P4JOURNAL location on master is /mnt/Journal/journal,
for saftey purposes we create SNAPSHOT on different Filesystem /mnt2/Backup/Backup0fCheckpoint/checkpoint.

Replica Server details:

p4 configure show replica
replica: P4LOG = replicaLog.txt
replica: P4TARGET = perforce.jstpl.com:1666
replica: P4TICKETS = /d01/perforce/replica/VersionFiles/.p4tickets
replica: db.replication = readonly
replica: lbr.replication = readonly
replica: monitor = 1
replica: server = 1
replica: serviceUser = service
replica: startup.1 = pull -J /mnt/Journal/journal -i 1
replica: startup.2 = pull -u -i 1

After Master Checkpoint was taken Perforce Replica stopped to replicate as it was trying to fetch journal from /mnt/Journal/journal.nnn .

The problem now I am having is that I take Checkpoint Back up at different location than P4JOURNAL.

How can I overcome Perforce Replication error problem.
just now i noticed in the documentation:
p4 pull (when replicating metadata) does not read compressed journals. The master
server must not compress journals until the replica server has fetched all journal
records from older journals.

If this is the case how can I control the size of Journal file on Master Server?

Thanks in advance,

#2 P4Geoff


    Advanced Member

  • Members
  • PipPipPip
  • 217 posts

Posted 10 July 2013 - 05:16 PM


I am sorry to hear of your difficulty.

This sort of problem is best handled by our excellent support folks, you can find details on contacting them at:

Just as an additional FYI, if you are running Swarm behind the replica it will work great for read only operations
but you may find write operations quite slow. You can fix that by increasing the polling rate of your replica.
Kindly advise if you are running Swarm behind your replica and I can provide more details on tweaking the poll rate.


#3 vinodarokiya



  • Members
  • PipPip
  • 15 posts
  • LocationBangalore

Posted 11 July 2013 - 06:22 AM

Thanks Geofff :)

Also tagged with one or more of these keywords: replication, issues, journal, p4 pull, compressed journal

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users