« Changelog History


ArangoDB v3.3.19 Release Notes

Release Date: 2018-10-20 // almost 7 years ago

    • 🛠 fixes validation of allowed or not allowed foxx service mount paths within the Web UI

    • The single database or single coordinator statistics in a cluster environment within the Web UI sometimes got called way too often. This caused artifacts in the graphs, which is now fixed.

    • An aardvark statistics route could not collect and sum up the statistics of all coordinators if one of them was ahead and had more results than the others

    • ⬆️ upgraded arangodb starter version to 0.13.6

    • turn on intermediate commits in replication applier in order to decrease the size of transactional operations on replication (issue #6821)

    • 🛠 fixed issue #6770: document update: ignoreRevs parameter ignored

    • when returning memory to the OS, use the same memory protection flags as when initializing the memory

    this prevents "hole punching" and keeps the OS from splitting one memory mapping into multiple mappings with different memory protection settings

    • 🛠 fix internal issue #2770: the Query Profiling modal dialog in the Web UI was slightly malformed.

    • 🛠 fix internal issue #2035: the Web UI now updates its indices view to check whether new indices exist or not.

    • 🛠 fix internal issue #6808: newly created databases within the Web UI did not appear when used Internet Explorer 11 as a browser.

    • 🛠 fix internal issue #2688: the Web UI's graph viewer created malformed node labels if a node was expanded multiple times.

    • 🛠 fix internal issue #2957: the Web UI was not able to display more than 1000 documents, even when it was set to a higher amount.

    • 🛠 fix internal issue #2785: web ui's sort dialog sometimes got rendered, even if it should not.

    • 🛠 fix internal issue #2764: the waitForSync property of a SatelliteCollection could not be changed via the Web UI

    • 👌 improved logging in case of replication errors

    • recover short server id from agency after a restart of a cluster node

    this fixes problems with short server ids being set to 0 after a node restart, which then prevented cursor result load-forwarding between multiple coordinators to work properly

    this should fix arangojs#573

    • 0️⃣ increased default timeouts in replication

    this decreases the chances of followers not getting in sync with leaders because of replication operations timing out

    • 🛠 fixed internal issue #1983: the Web UI was showing a deletion confirmation multiple times.

    • 🛠 fixed agents busy looping gossip

    • 🖐 handle missing _frontend collections gracefully

    the _frontend system collection is not required for normal ArangoDB operations, so if it is missing for whatever reason, ensure that normal operations can go on.