« Changelog History


ArangoDB v3.3.17 Release Notes

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

    • ⬆️ upgraded arangosync version to 0.6.0

    • ➕ added several advanced options for configuring and debugging LDAP connections. Please note that some of the following options are platform-specific and may not work on all platforms or with all LDAP servers reliably:

      • --ldap.serialized: whether or not calls into the underlying LDAP library should be serialized. This option can be used to work around thread-unsafe LDAP library functionality.
      • --ldap.serialize-timeout: sets the timeout value that is used when waiting to enter the LDAP library call serialization lock. This is only meaningful when --ldap.serialized has been set to true.
      • --ldap.retries: number of tries to attempt a connection. Setting this to values greater than one will make ArangoDB retry to contact the LDAP server in case no connection can be made initially.
      • --ldap.restart: whether or not the LDAP library should implicitly restart connections
      • --ldap.referrals: whether or not the LDAP library should implicitly chase referrals
      • --ldap.debug: turn on internal OpenLDAP library output (warning: will print to stdout).
      • --ldap.timeout: timeout value (in seconds) for synchronous LDAP API calls (a value of 0 means default timeout).
      • --ldap.network-timeout: timeout value (in seconds) after which network operations following the initial connection return in case of no activity (a value of 0 means default timeout).
      • --ldap.async-connect: whether or not the connection to the LDAP library will be done asynchronously.

    • 🛠 fixed a shutdown race in ArangoDB's logger, which could have led to some buffered log messages being discarded on shutdown

    • 🔀 display shard synchronization progress for collections outside of the _system database

    • 🛠 fixed issue #6611: Properly display JSON properties of user defined foxx services configuration within the web UI

    • 🛠 fixed issue #6583: Agency node segfaults if sent an authenticated HTTP request is sent to its port

    • when cleaning out a leader it could happen that it became follower instead of being removed completely

    • 🔀 make synchronous replication detect more error cases when followers cannot apply the changes from the leader

    • 🛠 fix some TLS errors that occurred when combining HTTPS/TLS transport with the VelocyStream protocol (VST)

    That combination could have led to spurious errors such as "TLS padding error" or "Tag mismatch" and connections being closed

    • ⚡️ agency endpoint updates now go through RAFT