Bug fix release
Compatibility
- RethinkDB 2.1.2 servers cannot be mixed with servers running earlier versions in the
same cluster - Changefeeds on a
get_all
query no longer return initial values. This restores the
behavior from RethinkDB 2.0
Bug fixes
- Fixed an issue where writes could be acknowledged before all necessary data was written
to disk - Restored the 2.0 behavior for changefeeds on
get_all
queries to avoid various
issues and incompatibilities - Fixed an issue that caused previously migrated tables to be shown as unavailable (#4723)
- Made outdated secondary index warnings disappear once the problem is resolved (#4664)
- Made
index_create
atomic to avoid race conditions when multiple indexes were created
in quick succession (#4694) - Improved how query execution times are reported in the Data Explorer (#4752)
- Fixed a memory leak in
r.js
(#4663) - Fixed the
Branch history is missing pieces
error (#4721) - Fixed a race condition causing a crash with
Guarantee failed: [!send_mutex.is_locked()]
(#4710) - Fixed a bug in the changefeed code that could cause crashes with the message
Guarantee failed: [active()]
(#4678) - Fixed various race conditions that could cause crashes if changefeeds were present
during resharding (#4735, #4734, #4678) - Fixed a race condition causing a crash with
Guarantee failed: [val.has()]
(#4736) - Fixed an
Assertion failed
issue when running a debug-mode binary (#4685) - Added a workaround for an
eglibc
bug that caused anunexpected address family
error on startup (#4470) - Added precautions to avoid secondary index migration issues in subsequent releases
- Out-of-memory errors in the server's JSON parser are now correctly reported (#4751)