Skip to content
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

fix replication #3099

Merged
merged 2 commits into from
Aug 22, 2017
Merged

fix replication #3099

merged 2 commits into from
Aug 22, 2017

Conversation

jsteemann
Copy link
Contributor

No description provided.

@fceller fceller merged commit 3946519 into devel Aug 22, 2017
ObiWahn added a commit that referenced this pull request Aug 24, 2017
…ture/planning-499-different-error-codes-for-version-check

* 'devel' of https://github.com/arangodb/arangodb: (29 commits)
  Revert "fixed return code"
  hotfix: fix examples in documentation, so the examples actually build
  fixed return code
  Fixing wrong response for DELETE _api/users/database (#3094)
  Update cluster architecture (#3100)
  Further checks/fixes for RocksDB recovery process (#3110)
  use filename conventions so the test only gets executed where it should be xecuted (#3108)
  fix typo as pointed out by @agreif
  fix proc filesystem URL as pointed out by @ThomasWeiss; fixes #3002
  only keep a few artifacts
  reference the graph management interface via general graphs
  enabled windows (#3078)
  Relaxing edge cache test asserts (#3103)
  fix replication (#3099)
  Fixed issue with periodic syncing and WAL file retention. (#3098)
  fixed openssl issue with 1.1 (#3095)
  Bug fix/foxx queue registration (#3097)
  Bug fix/planning issue 514 replication api (#3021)
  Added test to ensure RocksDB recovers keygen data outside WAL. (#3072)
  Fix edge cache behaviour (#3079)
  ...
@fceller fceller deleted the bug-fix/fix-rocksdb-replication branch September 14, 2017 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants