Lines Matching refs:master
23 # The master is site 1 in the MSGQUEUEDIR and clients 1-N map to message
27 # with a given id (i.e., repenv(1) is the master's environment.
132 # 1-master/1-client test, we try all four options. On a test
165 # the master and first client.
217 # Open the master and client environments; store these in the global repenv
218 # Return the master's environment: "-env masterenv"
244 # Open a master.
270 set repenv(master) $masterenv
317 set masterenv $repenv(master)
326 puts -nonewline "\t$test: Processing master/$i client queues"
397 # Verify that the directories in the master are exactly replicated in
405 # First dump the master.
413 # in the master environment, so we just call a no-op check function
415 # We just need to walk the master and the clients and make sure they
426 open_and_dump_file $testfile $repenv(master) $masterdir/t2 \
448 # Remove all the elements from the master and verify that these
455 # Delete all items in the master.
464 puts "\t$test: Deleting all items from the master."
465 set txn [$repenv(master) txn]
467 $repenv(master)] TRUE
468 set db [eval berkdb_open -txn $txn -env $repenv(master) \
510 # Close all the master and client environments in a replication test directory.
524 # databases on all the clients, do a checkpoint on the master and
528 puts "\t$test: Checkpointing master."
529 error_check_good masterenv_ckp [$repenv(master) txn_checkpoint] 0
540 error_check_good masterenv_close [$repenv(master) close] 0
745 # know we have a duplicate master.
1049 # reopen Should the new master (i.e. winner) be closed
1055 # If ignore is 1, the winner is not made master.
1057 # in electing a new master (perhaps because there
1058 # already is a master).
1222 # Reconfigure winning env as master.
1229 rep_start -master] 0
1233 # new master. This could
1234 # cause the new master to
1316 # If we did get a new master, its identity was checked
1321 error "FAIL: Did not elect new master."
1336 puts "\t\t$msg.3: Closing new master and reopening as client"
1516 # master handles them properly. Just abort
1769 # master handles them properly. Just abort
1915 # on a build with debug_rop enabled, the master's log is
1932 # Check that master and client logs and dbs are identical.
1937 # subset that both client and master have. Either the client or
1938 # the master may have more (earlier) log files, due to internal
2073 # if directed to do so. Read data on the master, ignoring
2091 # Now make sure we can successfully read on the master