Arangodb journal logfiles
up vote
1
down vote
favorite
What for are logfiles in:
"arango_instance_database/journals/logfile-xxxxxx.db
Can I delete them ?
How can I reduce their size ?
I set
database.maximal-journal-size = 1048576
but those files are still 32M large.
Can I set some directory for them like
/var/log/...
?
arangodb
asked Sep 12 '16 at 11:24
Tomek
206
add a comment |
up vote
1
down vote
favorite
What for are logfiles in:
"arango_instance_database/journals/logfile-xxxxxx.db
Can I delete them ?
How can I reduce their size ?
I set
database.maximal-journal-size = 1048576
but those files are still 32M large.
Can I set some directory for them like
/var/log/...
?
arangodb
asked Sep 12 '16 at 11:24
Tomek
206
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
What for are logfiles in:
"arango_instance_database/journals/logfile-xxxxxx.db
Can I delete them ?
How can I reduce their size ?
I set
database.maximal-journal-size = 1048576
but those files are still 32M large.
Can I set some directory for them like
/var/log/...
?
arangodb
asked Sep 12 '16 at 11:24
Tomek
206
What for are logfiles in:
"arango_instance_database/journals/logfile-xxxxxx.db
Can I delete them ?
How can I reduce their size ?
I set
database.maximal-journal-size = 1048576
but those files are still 32M large.
Can I set some directory for them like
/var/log/...
?
arangodb
arangodb
asked Sep 12 '16 at 11:24
Tomek
206
asked Sep 12 '16 at 11:24
Tomek
206
asked Sep 12 '16 at 11:24
Tomek
206
asked Sep 12 '16 at 11:24
Tomek
206
asked Sep 12 '16 at 11:24
Tomek
206
206
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
You're referencing the Write Ahead Logfiles which are at least temporarily the files your data is kept in.
So its a very bad idea to remove them on your own, as long as you still like your data to be intact.
The files are used so documents can be written to disk in a contineous fashion. Once the system is idle, the aggregator job will pick the documents from them and move them over into your database files.
You can find interesting documentation of situations where others didn't choose such an architectural approach, and data was written directly into their data files on the disk, and what this then does to your sytem.
Once all documents in a WAL-file have been moved into db files, the ArangoDB will remove the allocated space.
answered Sep 12 '16 at 14:47
dothebart
4,804829
add a comment |
up vote
0
down vote
Thank You a lot for reply :-)
So in case of arangodb deployed as "single instance" I can set:
--wal.suppress-shape-information true
--wal.historic-logfiles 0
Anything else ?
How about
--wal.logfile-size
What are best/common practises in determining its size ?
answered Sep 13 '16 at 9:39
Tomek
206
suppress-shape-informationisn't available in 3.0 anymore. Reducinglogfile-sizewill probably end up in more of them being used, however they may be removed faster.historic-logfilesare needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.
– dothebart
Sep 14 '16 at 11:29
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You're referencing the Write Ahead Logfiles which are at least temporarily the files your data is kept in.
So its a very bad idea to remove them on your own, as long as you still like your data to be intact.
The files are used so documents can be written to disk in a contineous fashion. Once the system is idle, the aggregator job will pick the documents from them and move them over into your database files.
You can find interesting documentation of situations where others didn't choose such an architectural approach, and data was written directly into their data files on the disk, and what this then does to your sytem.
Once all documents in a WAL-file have been moved into db files, the ArangoDB will remove the allocated space.
answered Sep 12 '16 at 14:47
dothebart
4,804829
add a comment |
up vote
1
down vote
accepted
You're referencing the Write Ahead Logfiles which are at least temporarily the files your data is kept in.
So its a very bad idea to remove them on your own, as long as you still like your data to be intact.
The files are used so documents can be written to disk in a contineous fashion. Once the system is idle, the aggregator job will pick the documents from them and move them over into your database files.
You can find interesting documentation of situations where others didn't choose such an architectural approach, and data was written directly into their data files on the disk, and what this then does to your sytem.
Once all documents in a WAL-file have been moved into db files, the ArangoDB will remove the allocated space.
answered Sep 12 '16 at 14:47
dothebart
4,804829
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You're referencing the Write Ahead Logfiles which are at least temporarily the files your data is kept in.
So its a very bad idea to remove them on your own, as long as you still like your data to be intact.
The files are used so documents can be written to disk in a contineous fashion. Once the system is idle, the aggregator job will pick the documents from them and move them over into your database files.
You can find interesting documentation of situations where others didn't choose such an architectural approach, and data was written directly into their data files on the disk, and what this then does to your sytem.
Once all documents in a WAL-file have been moved into db files, the ArangoDB will remove the allocated space.
answered Sep 12 '16 at 14:47
dothebart
4,804829
You're referencing the Write Ahead Logfiles which are at least temporarily the files your data is kept in.
So its a very bad idea to remove them on your own, as long as you still like your data to be intact.
The files are used so documents can be written to disk in a contineous fashion. Once the system is idle, the aggregator job will pick the documents from them and move them over into your database files.
You can find interesting documentation of situations where others didn't choose such an architectural approach, and data was written directly into their data files on the disk, and what this then does to your sytem.
Once all documents in a WAL-file have been moved into db files, the ArangoDB will remove the allocated space.
answered Sep 12 '16 at 14:47
dothebart
4,804829
answered Sep 12 '16 at 14:47
dothebart
4,804829
answered Sep 12 '16 at 14:47
dothebart
4,804829
answered Sep 12 '16 at 14:47
dothebart
4,804829
4,804829
add a comment |
add a comment |
up vote
0
down vote
Thank You a lot for reply :-)
So in case of arangodb deployed as "single instance" I can set:
--wal.suppress-shape-information true
--wal.historic-logfiles 0
Anything else ?
How about
--wal.logfile-size
What are best/common practises in determining its size ?
answered Sep 13 '16 at 9:39
Tomek
206
suppress-shape-informationisn't available in 3.0 anymore. Reducinglogfile-sizewill probably end up in more of them being used, however they may be removed faster.historic-logfilesare needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.
– dothebart
Sep 14 '16 at 11:29
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
add a comment |
up vote
0
down vote
Thank You a lot for reply :-)
So in case of arangodb deployed as "single instance" I can set:
--wal.suppress-shape-information true
--wal.historic-logfiles 0
Anything else ?
How about
--wal.logfile-size
What are best/common practises in determining its size ?
answered Sep 13 '16 at 9:39
Tomek
206
suppress-shape-informationisn't available in 3.0 anymore. Reducinglogfile-sizewill probably end up in more of them being used, however they may be removed faster.historic-logfilesare needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.
– dothebart
Sep 14 '16 at 11:29
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
add a comment |
up vote
0
down vote
up vote
0
down vote
Thank You a lot for reply :-)
So in case of arangodb deployed as "single instance" I can set:
--wal.suppress-shape-information true
--wal.historic-logfiles 0
Anything else ?
How about
--wal.logfile-size
What are best/common practises in determining its size ?
answered Sep 13 '16 at 9:39
Tomek
206
Thank You a lot for reply :-)
So in case of arangodb deployed as "single instance" I can set:
--wal.suppress-shape-information true
--wal.historic-logfiles 0
Anything else ?
How about
--wal.logfile-size
What are best/common practises in determining its size ?
answered Sep 13 '16 at 9:39
Tomek
206
answered Sep 13 '16 at 9:39
Tomek
206
answered Sep 13 '16 at 9:39
Tomek
206
answered Sep 13 '16 at 9:39
Tomek
206
206
suppress-shape-informationisn't available in 3.0 anymore. Reducinglogfile-sizewill probably end up in more of them being used, however they may be removed faster.historic-logfilesare needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.
– dothebart
Sep 14 '16 at 11:29
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
add a comment |
suppress-shape-informationisn't available in 3.0 anymore. Reducinglogfile-sizewill probably end up in more of them being used, however they may be removed faster.historic-logfilesare needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.
– dothebart
Sep 14 '16 at 11:29
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
suppress-shape-information isn't available in 3.0 anymore. Reducing logfile-size will probably end up in more of them being used, however they may be removed faster. historic-logfiles are needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.– dothebart
Sep 14 '16 at 11:29
suppress-shape-information isn't available in 3.0 anymore. Reducing logfile-size will probably end up in more of them being used, however they may be removed faster. historic-logfiles are needed to possibly re-sync replicas; if you decide to throw them away quicker, a replication may not be able to catch up after a netsplit anymore.– dothebart
Sep 14 '16 at 11:29
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
@ dothebart But --wal.suppress-shape-information is still present in official documentation for 3.0. docs.arangodb.com/3.0/Manual/Administration/Configuration/… So how/ to who can I report to update documentation ?
– Tomek
Sep 16 '16 at 13:42
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
me ;-) github.com/arangodb/arangodb/commit/… Thanks for reporting.
– dothebart
Sep 16 '16 at 14:22
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f39449237%2farangodb-journal-logfiles%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
