8000 make replication timeouts configurable via startup options by jsteemann · Pull Request #10473 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

make replication timeouts configurable via startup options #10473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 19, 2019

Conversation

jsteemann
Copy link
Contributor
@jsteemann jsteemann commented Nov 19, 2019

Scope & Purpose

This targets 3.5.4.

Make replication timeouts configurable via startup options.
The following options are available (for active failover and master-slave replication):

    --replication.connect-timeout
    --replication.request-timeout

Values can be specified in seconds. If these options are used, they will be used for replication requests, overriding any hard-coded defaults or explicitly configured timeouts.

  • Bug-Fix for devel-branch (i.e. no need for backports?)
  • Bug-Fix for a released version (did you remember to port this to all relevant release branches?)
  • The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)

Testing & Verification

This change is a trivial rework / code cleanup without any test coverage.

https://172.16.10.101/view/PR/job/arangodb-matrix-pr/7250/

The following options are available (for active failover
and master-slave replication):

    --replication.connect-timeout
    --replication.request-timeout

Values can be specified in seconds. If these options are used, they will
be used for replication requests, overriding any hard-coded defaults or
explicitly configured timeouts.

Additionally, this change increases the default request timeout
for replication from 10 minutes to 20 minutes.
@jsteemann jsteemann added this to the 3.5 milestone Nov 19, 2019
@jsteemann
Copy link
Contributor Author

@KVS85
Copy link
Contributor
KVS85 commented Nov 19, 2019

Tests blue except failed Windows PR (known issue with active_failover suite).

Decided to be included in 3.5.3.

@KVS85 KVS85 merged commit abca9b0 into 3.5 Nov 19, 2019
@KVS85 KVS85 deleted the feature-3.5/configurable-replication-timeouts branch November 19, 2019 17:24
KVS85 pushed a commit that referenced this pull request Nov 19, 2019
* make replication timeouts configurable via startup options

The following options are available (for active failover
and master-slave replication):

    --replication.connect-timeout
    --replication.request-timeout

Values c
B1F3
an be specified in seconds. If these options are used, they will
be used for replication requests, overriding any hard-coded defaults or
explicitly configured timeouts.

Additionally, this change increases the default request timeout
for replication from 10 minutes to 20 minutes.

* do *not* change default value for timeouts

* make tests work again

* Update CHANGELOG
ObiWahn added a commit that referenced this pull request Nov 26, 2019
…re-3.5/query-timeout

* '3.5' of https://github.com/arangodb/arangodb:
  Allow the optimizer to use indexes (#10543)
  Updated arangosync to 0.7.0 (#10532)
  Bug fix 3.5/little weekend fix (#10527)
  Bug fix 3.5/issue 10470 (#10497)
  add tests for inventory (#10464) (#10495)
  fixed issue #10440: Incorrect sorting with sort criteria partially covered by index (#10443)
  [3.5] Added precondition to ensure that server is still as seen before. (#10477)
  improve error message (#10478)
  allow in-place analyzer creation via link definition (#10466) (#10481)
  make replication timeouts configurable via startup options (#10473)
  [3.5] no coordinators left behind (#10420)
  don't return any in-progress indexes (#10431)
  fix invalid assertion (#10428)
  show type of index when non-implemented exception is thrown (#10425)
  Fix dump tests
  Improve syncer error message (#10404)
  DEVSUP-492 (#10379) (#10402)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0