8000 Bug fix/changelog 324 cleanup (#3325) · MohammedDeveloper/arangodb@e583867 · GitHub
[go: up one dir, main page]
Skip to content

Commit e583867

Browse files
jsteemannfceller
jsteemann
authored and
fceller
committed
Bug fix/changelog 324 cleanup (arangodb#3325)
* updated CHANGELOG * even more cleanup * removed tabs
1 parent af35364 commit e583867

File tree

1 file changed

+65
-64
lines changed

1 file changed

+65
-64
lines changed

‎CHANGELOG

Lines changed: 65 additions & 64 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,61 @@
11
v3.2.4 (2017-XX-XX)
22
-------------------
33

4-
* ui: added replicationFactor option during SmartGraph creation.
4+
* UI: added replicationFactor option during SmartGraph creation
5+
6+
* make the MMFiles compactor perform less writes during normal compaction
7+
operation
8+
9+
This partially fixes issue #3144
10+
11+
* make the MMFiles compactor configurable
12+
13+
The following options have been added:
14+
15+
* `--compaction.db-sleep-time`: sleep interval between two compaction runs
16+
(in s)
17+
* `--compaction.min-interval"`: minimum sleep time between two compaction
18+
runs (in s)
19+
* `--compaction.min-small-data-file-size`: minimal filesize threshold
20+
original datafiles have to be below for a compaction
21+
* `--compaction.dead-documents-threshold`: minimum unused count of documents
22+
in a datafile
23+
* `--compaction.dead-size-threshold`: how many bytes of the source data file
24+
are allowed to be unused at most
25+
* `--compaction.dead-size-percent-threshold`: how many percent of the source
26+
datafile should be unused at least
27+
* `--compaction.max-files`: Maximum number of files to merge to one file
28+
* `--compaction.max-result-file-size`: how large may the compaction result
29+
file become (in bytes)
30+
* `--compaction.max-file-size-factor`: how large the resulting file may
31+
be in comparison to the collection's `--database.maximal-journal-size' setting`
32+
33+
* fix downwards-incompatibility in /_api/explain REST handler
34+
35+
* fix Windows implementation for fs.getTempPath() to also create a
36+
sub-directory as we do on linux
537

6-
* make the mmfiles compactor configurable
38+
* fixed a multi-threading issue in cluster-internal communication
739

8-
* fix windows implementation for fs.getTempPath() to also create a
9-
sub-directory as we do on linux
40+
* performance improvements for traversals and edge lookups
41+
42+
* removed internal memory zone handling code. the memory zones were a leftover
43+
from the early ArangoDB days and did not provide any value in the current
44+
implementation.
45+
46+
* (Enterprise only) added `skipInaccessibleCollections` option for AQL queries:
47+
if set, AQL queries (especially graph traversals) will treat collections to
48+
which a user has no access rights to as if these collections were empty.
1049

50+
* adjusted scheduler thread handling to start and stop less threads in
51+
normal operations
52+
1153
* leader-follower replication catchup code has been rewritten in C++
1254

1355
* early stage AQL optimization now also uses the C++ implementations of
1456
AQL functions if present. Previously it always referred to the JavaScript
15-
implementations and ignored the C++ implementations.
57+
implementations and ignored the C++ implementations. This change gives
58+
more flexibility to the AQL optimizer.
1659

1760
* ArangoDB tty log output is now colored for log messages with levels
1861
FATAL, ERR and WARN.
@@ -34,6 +77,10 @@ v3.2.4 (2017-XX-XX)
3477

3578
The default value for this option is `false`, so no roles will be logged.
3679

80+
81+
v3.2.3 (2017-09-07)
82+
-------------------
83+
3784
* fixed issue #3106: orphan collections could not be registered in general-graph module
3885

3986
* fixed wrong selection of the database inside the internal cluster js api
@@ -62,63 +109,17 @@ v3.2.4 (2017-XX-XX)
62109
the maximum number of invocations per context is unlimited. The default value
63110
for `--javascript.v8-contexts-max-age` is 60 seconds.
64111

65-
* fixed wrong ui cluster health information
112+
* fixed wrong UI cluster health information
66113

67114
* fixed issue #3070: Add index in _jobs collection
68115

69116
* fixed issue #3125: HTTP Foxx API JSON parsing
70117

71118
* fixed issue #3120: Foxx queue: job isn't running when server.authentication = true
72119

120+
* fixed supervision failure detection and handling, which happened with simultaneous
121+
agency leadership change
73122

74-
v3.2.3 (2017-09-07)
75-
-------------------
76-
77-
* ui: added replicationFactor option during SmartGraph creation.
78-
79-
* leader-follower replication catchup code has been rewritten in C++
80-
81-
* early stage AQL optimization now also uses the C++ implementations of
82-
AQL functions if present. Previously it always referred to the JavaScript
83-
implementations and ignored the C++ implementations.
84-
85-
* ArangoDB tty log output is now colored for log messages with levels
86-
FATAL, ERR and WARN.
87-
88-
* changed the return values of AQL functions `REGEX_TEST` and `REGEX_REPLACE`
89-
to `null` when the input regex is invalid. Previous versions of ArangoDB
90-
partly returned `false` for invalid regexes and partly `null`.
91-
92-
* added `--log.role` option for arangod
93-
94-
When set to `true`, this option will make the ArangoDB logger print a single
95-
character with the server's role into each logged message. The roles are:
96-
97-
- U: undefined/unclear (used at startup)
98-
- S: single server
99-
- C: coordinator
100-
- P: primary
101-
- A: agent
102-
103-
* fix double invocation of the compactor
104-
105-
* fixed issue #3106: orphan collections could not be registered in general-graph module
106-
107-
* fixed wrong selection of the database inside the internal cluster js api
108-
109-
* added startup option `--server.check-max-memory-mappings` to make arangod check
110-
the number of memory mappings currently used by the process and compare it with
111-
the maximum number of allowed mappings as determined by /proc/sys/vm/max_map_count
112-
113-
Note that this option is effective on Linux systems only.
114-
115-
* fixed wrong ui cluster health information
116-
117-
* fixed issue #3125: HTTP Foxx API Json parsing
118-
119-
* fixed issue #3120: Foxx queue: job isn't running when server.authentication = true
120-
121-
* fixed supervision failure detection and handling, which happened with simultaneous agency leadership change
122123

123124
v3.2.2 (2017-08-23)
124125
-------------------
@@ -1099,16 +1100,16 @@ v3.1.10 (2017-02-02)
10991100
db.test.count(true);
11001101

11011102
{
1102-
"s100058" : 99,
1103-
"s100057" : 103,
1104-
"s100056" : 100,
1105-
"s100050" : 94,
1106-
"s100055" : 90,
1107-
"s100054" : 122,
1108-
"s100051" : 109,
1109-
"s100059" : 99,
1110-
"s100053" : 95,
1111-
"s100052" : 89
1103+
"s100058" : 99,
1104+
"s100057" : 103,
1105+
"s100056" : 100,
1106+
"s100050" : 94,
1107+
"s100055" : 90,
1108+
"s100054" : 122,
1109+
"s100051" : 109,
1110+
"s100059" : 99,
1111+
"s100053" : 95,
1112+
"s100052" : 89
11121113
}
11131114

11141115
* added optional memory limit for AQL queries:

0 commit comments

Comments
 (0)
0