8000 added a TTL for Pregel conductors, plus GC by jsteemann · Pull Request #14311 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

added a TTL for Pregel conductors, plus GC #14311

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 5 commits into from
Jul 1, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Merge branch 'devel' into feature/pregel-conductor-ttl
  • Loading branch information
jsteemann authored Jul 1, 2021
commit d2b2bc1c687751df7058788bcb0249d6d4e5b8d9
36 changes: 36 additions & 0 deletions CHANGELOG
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,42 @@ devel
about 10 minutes after finalization. The time-to-live values can be
overriden per Pregel job by passing a "ttl" value.

* Revive startup parameter `--server.session-timeout` to control the timeout
for web interface sessions and other sessions that are based on JWTs created
by the `/_open/auth` API.

This PR also changes the default session timeout for web interface sessions
to one hour. Older versions of ArangoDB had longer session timeouts.

* Add prefix parameter to LEVENSHTEIN_MATCH function in ArangoSearch

* Removed redirects from /_admin/cluster* to /_admin/cluster/*. Adjusted
internal requests to use the new url.

* Fix display of running and slow queries in web UI when there are multiple
coordinators. Previously, the display order of queries was undefined, which
could lead to queries from one coordinator being display on top once and
then the queries from another. That made using this UI harder than necessary.

Now queries are sorted for display, according to their query IDs.

* Updated ArangoDB Starter to 0.15.1-preview-2.

* Fix potential stack overflow when executing large queries. This is
achieved by splitting the callstack and moving part of the execution
to a separate thread. The number of execution nodes after which such
a callstack split should be performed can be configured via the query
option `maxNodesPerCallstack` and the command line option
`--query.max-nodes-per-callstack`; the default is 250.

* Bug-Fix: Pregel WCC algorithm could yield incorrect results if a
part of the connected component was only attached via OUTBOUND edges.
The underlying algorithm is now modified to properly retain INBOUND
edges for the runtime of the execution. This uses more RAM for the
algorithm but guarantees correctness.

* Updated ArangoDB Starter to 0.15.1-preview-1.

* Updated arangosync to 2.4.0.

* Fixed DEVSUP-799: unique vertex getter may point to invalid memory after being
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.
0