2023-03-18 15:58:54 +01:00
|
|
|
[wait_for_async_pid]
|
|
|
|
|
|
|
|
|
|
# Max waiting time, ms, for appearing of some asynchronously
|
|
|
|
|
# launched process (isql, gbak, gfix etc) in the mon$attachments.
|
|
|
|
|
# This time can be valuable in case of heavy concurrent workload,
|
|
|
|
|
# but we have to limit such attempts. Test must raise assert if
|
|
|
|
|
# known <launched_process>.pid does not appear for that time:
|
|
|
|
|
#
|
|
|
|
|
MAX_WAIT_FOR_PID_APPEAR_WIN = 5000
|
|
|
|
|
MAX_WAIT_FOR_PID_APPEAR_NIX = 5000
|
|
|
|
|
|
2022-06-18 18:52:21 +02:00
|
|
|
[encryption]
|
2023-03-11 08:02:40 +01:00
|
|
|
|
|
|
|
|
# Max waiting time, ms, for encryption finish.
|
|
|
|
|
# Must be set separately for different OS.
|
|
|
|
|
# Used in bugs/core_6048_test.py et al:
|
|
|
|
|
#
|
|
|
|
|
MAX_WAIT_FOR_ENCR_FINISH_WIN = 10000
|
|
|
|
|
MAX_WAIT_FOR_ENCR_FINISH_NIX = 10000
|
|
|
|
|
|
2022-06-18 18:52:21 +02:00
|
|
|
ENCRYPTION_PLUGIN = fbSampleDbCrypt
|
|
|
|
|
ENCRYPTION_HOLDER = fbSampleKeyHolder
|
|
|
|
|
ENCRYPTION_KEY = Red
|
2022-07-31 12:46:10 +02:00
|
|
|
ENCRYPTION_BADKEY = NoSuchkey
|
2022-08-23 08:59:15 +02:00
|
|
|
|
|
|
|
|
[replication]
|
2023-04-14 06:35:54 +02:00
|
|
|
|
2023-04-18 06:39:05 +02:00
|
|
|
# Value of 'journal_archive_timeout' parameter for master DB. Default is 10 secons.
|
|
|
|
|
#
|
|
|
|
|
JOURNAL_ARCHIVE_TIMEOUT = 10
|
|
|
|
|
|
|
|
|
|
# Value of 'apply_idle_timeout' parameter for replica DB. Default is 10 secons.
|
|
|
|
|
#
|
|
|
|
|
REPLICA_TIMEOUT_FOR_IDLE = 3
|
|
|
|
|
|
|
|
|
|
# Value of 'apply_error_timeout' parameter for replica DB. Default is 60 secons.
|
|
|
|
|
#
|
|
|
|
|
REPLICA_TIMEOUT_FOR_ERROR = 7
|
|
|
|
|
|
2023-12-12 08:40:55 +01:00
|
|
|
# Max limit, in seconds, to wait until data that we have added in master
|
|
|
|
|
# will appear in replica DB.
|
|
|
|
|
#
|
|
|
|
|
MAX_TIME_FOR_WAIT_DATA_IN_REPLICA = 65
|
2023-04-14 06:35:54 +02:00
|
|
|
|
2022-08-24 12:23:09 +02:00
|
|
|
# Max limit, in seconds, to wait until message about replicating segment
|
|
|
|
|
# with known number will appear in the replication.log (after we take
|
|
|
|
|
# "snapshot" of its original content and compare it with new data):
|
|
|
|
|
#
|
2023-12-12 08:40:55 +01:00
|
|
|
MAX_TIME_FOR_WAIT_SEGMENT_IN_LOG = 65
|
2022-08-24 12:23:09 +02:00
|
|
|
|
2022-08-27 18:51:53 +02:00
|
|
|
|
2022-08-24 12:23:09 +02:00
|
|
|
# Aliases for main and replica databases as they are defined in the pre-created
|
|
|
|
|
# file <QA_root>/qa-databases.conf:
|
|
|
|
|
#
|
|
|
|
|
# db_main_alias = $(dir_sampleDb)/qa_replication/db_main.fdb
|
|
|
|
|
# db_repl_alias = $(dir_sampleDb)/qa_replication/db_repl.fdb
|
|
|
|
|
#
|
|
|
|
|
# DO NOT use full path+filenames here! Databases will be opened in tests using
|
|
|
|
|
# '#'-syntax, e.g.:
|
|
|
|
|
# db_factory( filename = '#' + MAIN_DB_ALIAS, do_not_create = True, do_not_drop = True)
|
|
|
|
|
# db_factory( filename = '#' + REPL_DB_ALIAS, do_not_create = True, do_not_drop = True)
|
|
|
|
|
#
|
2022-08-23 08:59:15 +02:00
|
|
|
MAIN_DB_ALIAS = db_main_alias
|
|
|
|
|
REPL_DB_ALIAS = db_repl_alias
|
2022-08-24 12:23:09 +02:00
|
|
|
|
2022-08-24 12:28:19 +02:00
|
|
|
# Relative names of replication-related directories.
|
2022-08-24 12:23:09 +02:00
|
|
|
# These folders must be created in the same folder as
|
|
|
|
|
# database <MAIN_DB_ALIAS>.
|
|
|
|
|
# Tests will cleanup these folders in case of any error
|
|
|
|
|
# (together with re-creation of both databases):
|
|
|
|
|
#
|
|
|
|
|
JOURNAL_SUB_DIR = repl_journal
|
|
|
|
|
ARCHIVE_SUB_DIR = repl_archive
|
2023-12-23 13:27:06 +01:00
|
|
|
|
|
|
|
|
# Replication tests which do some DML (i.e. changes not only metadata but data itself) had a problem:
|
|
|
|
|
# it was necessary run SWEEP after test completion, both for DB_MAIN and DB_REPL. Otherwise next runs
|
|
|
|
|
# of this test (or other tests related to replication) caused:
|
|
|
|
|
# "ERROR: Record format with length <NNN> is not found for table TEST"
|
|
|
|
|
# (discussed with dimitr, letters since 04-aug-2021)
|
|
|
|
|
# This problem existed during 2021...2022 and then was fixed:
|
|
|
|
|
# * for FB 4.x: 26-jan-2023, commit 2ed48a62c60c029cd8cb2b0c914f23e1cb56580a
|
|
|
|
|
# * for FB 5.x: 20-apr-2023, commit 5af209a952bd2ec3723d2c788f2defa6b740ff69
|
|
|
|
|
# (log message: 'Avoid random generation of field IDs, respect the user-specified order instead').
|
|
|
|
|
# If we want to check these two commits (making SKIP sweep) in all replication tests then set parameter
|
|
|
|
|
# RUN_SWEEP_AT_END to zero. Otherwise (if regression occurs and some of tests again fail with message
|
|
|
|
|
# related to record format) set RUN_SWEEP_AT_END to 1.
|
|
|
|
|
#
|
|
|
|
|
RUN_SWEEP_AT_END = 0
|
