[GitHub] davisp commented on issue #674: Flaky compaction daemon test
davisp commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315198304 Oops, I think we both read that wrong with GitHub chopping off and forcing the horizontal scroll. The second database compaction is the view compaction. Which we expect. Though I find it odd that the config deletion happens nearly 10ms after the swap compacted. Though we wait for that compactor pid to exit... I *think* that's the key to what's causing us issues This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #674: Flaky compaction daemon test
wohali commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315185827 OK looked at a couch.log. We have a race where the compaction daemon finishes compacting the test DB, then immediately starts compacting it **again**, so our check for the db to be idle fails. ``` [info] 2017-06-16T18:49:25.122688Z nonode@nohost <0.13883.1> Starting compaction for db "eunit-test-db-1497638926674066" [notice] 2017-06-16T18:49:25.383106Z nonode@nohost <0.13883.1> Compaction swap for db: /home/travis/build/apache/couchdb/tmp/data/eunit-test-db-1497638926674066.couch 1646789 53445 [info] 2017-06-16T18:49:25.386118Z nonode@nohost <0.13883.1> Compaction for db "eunit-test-db-1497638926674066" completed. [info] 2017-06-16T18:49:25.390952Z nonode@nohost <0.16501.1> Compaction started for db: eunit-test-db-1497638926674066 idx: _design/foo [notice] 2017-06-16T18:49:25.434478Z nonode@nohost <0.13891.1> Compaction swap for view /home/travis/build/apache/couchdb/tmp/data/.eunit-test-db-1497638926674066_design/mrview/ee2c720a13443ab1d50210242730ca31.view 391267 28800 [notice] 2017-06-16T18:49:25.443473Z nonode@nohost <0.13662.1> config: [compactions] _default deleted for reason nil [info] 2017-06-16T18:49:25.443559Z nonode@nohost <0.16501.1> Compaction finished for db: eunit-test-db-1497638926674066 idx: _design/foo [error] 2017-06-16T18:49:25.472035Z nonode@nohost <0.13891.1> gen_server <0.13891.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'$gen_cast',delete} state: {st,couch_mrview_index,{mrst,<<238,44,114,10,19,68,58,177,213,2,16,36,39,48,202,49>>,<0.16503.1>,#Ref<0.0.6.37429>,<<"eunit-test-db-1497638926674066">>,<<"_design/foo">>,<<"javascript">>,[],false,false,{[]},[{mrview,0,0,0,[<<"foo3">>,<<"foo2">>,<<"foo">>],[],<<"function(doc) { emit(doc._id, doc); }">>,{btree,<0.16503.1>,{26184,{400,[]},18346},undefined,undefined,#Fun,#Fun,snappy},nil,nil,false,false,[]}],{btree,<0.16503.1>,{7946,[],7997},undefined,undefined,undefined,nil,snappy},nil,401,0,undefined,undefined,undefined,undefined,undefined,nil},<0.13894.1>,<0.13895.1>,[],false,false} [error] 2017-06-16T18:49:25.475163Z nonode@nohost <0.13891.1> CRASH REPORT Process (<0.13891.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:722) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index,init,['Argument__1']}, ancestors: [<0.13890.1>], messages: [], links: [<0.13894.1>,<0.13895.1>,<0.13861.1>], dictionary: [], trap_exit: false, status: running, heap_size: 2586, stack_size: 27, reductions: 31341 [error] 2017-06-16T18:49:25.476680Z nonode@nohost <0.13895.1> gen_server <0.13895.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state: {st,<0.13891.1>,couch_mrview_index,undefined} [error] 2017-06-16T18:49:25.477461Z nonode@nohost <0.13895.1> CRASH REPORT Process (<0.13895.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:744) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index_compactor,init,['Argument__1']}, ancestors: [<0.13891.1>,<0.13890.1>], messages: [], links: [], dictionary: [], trap_exit: true, status: running, heap_size: 610, stack_size: 27, reductions: 194 [error] 2017-06-16T18:49:25.478441Z nonode@nohost <0.13894.1> gen_server <0.13894.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state: {st,<0.13891.1>,couch_mrview_index,undefined} [error] 2017-06-16T18:49:25.479197Z nonode@nohost <0.13894.1> CRASH REPORT Process (<0.13894.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:744) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index_updater,init,['Argument__1']}, ancestors: [<0.13891.1>,<0.13890.1>], messages: [], links: [], dictionary: [], trap_exit: true, status: running, heap_size: 1598, stack_size: 27, reductions: 596288 [error] 2017-06-16T18:49:25.479677Z nonode@nohost <0.13861.1> gen_server couch_index_server terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state:
[GitHub] wohali commented on issue #674: Flaky compaction daemon test
wohali commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315185827 OK looked at a couch.log. We have a race where the compaction daemon finishes compacting the test DB, then immediately starts compacting it **again**, so our check for the db to be idle fails. What I don't know is if that's a legitimate attempt to re-compact (because it is still too fragmented) or if the compaction daemon is attempting to re-compact based on old data about the state of the DB in question. ``` [info] 2017-06-16T18:49:25.122688Z nonode@nohost <0.13883.1> Starting compaction for db "eunit-test-db-1497638926674066" [notice] 2017-06-16T18:49:25.383106Z nonode@nohost <0.13883.1> Compaction swap for db: /home/travis/build/apache/couchdb/tmp/data/eunit-test-db-1497638926674066.couch 1646789 53445 [info] 2017-06-16T18:49:25.386118Z nonode@nohost <0.13883.1> Compaction for db "eunit-test-db-1497638926674066" completed. [info] 2017-06-16T18:49:25.390952Z nonode@nohost <0.16501.1> Compaction started for db: eunit-test-db-1497638926674066 idx: _design/foo [notice] 2017-06-16T18:49:25.434478Z nonode@nohost <0.13891.1> Compaction swap for view /home/travis/build/apache/couchdb/tmp/data/.eunit-test-db-1497638926674066_design/mrview/ee2c720a13443ab1d50210242730ca31.view 391267 28800 [notice] 2017-06-16T18:49:25.443473Z nonode@nohost <0.13662.1> config: [compactions] _default deleted for reason nil [info] 2017-06-16T18:49:25.443559Z nonode@nohost <0.16501.1> Compaction finished for db: eunit-test-db-1497638926674066 idx: _design/foo [error] 2017-06-16T18:49:25.472035Z nonode@nohost <0.13891.1> gen_server <0.13891.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'$gen_cast',delete} state: {st,couch_mrview_index,{mrst,<<238,44,114,10,19,68,58,177,213,2,16,36,39,48,202,49>>,<0.16503.1>,#Ref<0.0.6.37429>,<<"eunit-test-db-1497638926674066">>,<<"_design/foo">>,<<"javascript">>,[],false,false,{[]},[{mrview,0,0,0,[<<"foo3">>,<<"foo2">>,<<"foo">>],[],<<"function(doc) { emit(doc._id, doc); }">>,{btree,<0.16503.1>,{26184,{400,[]},18346},undefined,undefined,#Fun,#Fun,snappy},nil,nil,false,false,[]}],{btree,<0.16503.1>,{7946,[],7997},undefined,undefined,undefined,nil,snappy},nil,401,0,undefined,undefined,undefined,undefined,undefined,nil},<0.13894.1>,<0.13895.1>,[],false,false} [error] 2017-06-16T18:49:25.475163Z nonode@nohost <0.13891.1> CRASH REPORT Process (<0.13891.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:722) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index,init,['Argument__1']}, ancestors: [<0.13890.1>], messages: [], links: [<0.13894.1>,<0.13895.1>,<0.13861.1>], dictionary: [], trap_exit: false, status: running, heap_size: 2586, stack_size: 27, reductions: 31341 [error] 2017-06-16T18:49:25.476680Z nonode@nohost <0.13895.1> gen_server <0.13895.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state: {st,<0.13891.1>,couch_mrview_index,undefined} [error] 2017-06-16T18:49:25.477461Z nonode@nohost <0.13895.1> CRASH REPORT Process (<0.13895.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:744) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index_compactor,init,['Argument__1']}, ancestors: [<0.13891.1>,<0.13890.1>], messages: [], links: [], dictionary: [], trap_exit: true, status: running, heap_size: 610, stack_size: 27, reductions: 194 [error] 2017-06-16T18:49:25.478441Z nonode@nohost <0.13894.1> gen_server <0.13894.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state: {st,<0.13891.1>,couch_mrview_index,undefined} [error] 2017-06-16T18:49:25.479197Z nonode@nohost <0.13894.1> CRASH REPORT Process (<0.13894.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:744) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index_updater,init,['Argument__1']}, ancestors: [<0.13891.1>,<0.13890.1>], messages: [], links: [], dictionary: [], trap_exit: true, status: running, heap_size: 1598, stack_size: 27, reductions: 596288 [error] 2017-06-16T18:49:25.479677Z nonode@nohost <0.13861.1> gen_server couch_index_server
[GitHub] davisp commented on issue #674: Flaky compaction daemon test
davisp commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315186525 Looks like the right diagnosis to me. My read on the is_idle test is that we're trying to assert that the compaction daemon doesn't hold a monitor on the database after its done compacting. Perhaps it'd be better to grab the monitors while its compacting and then just assert that its not got the same monitors? Though getting the monitor that Pid A has on Pid B from Pid C is racy at best. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #674: Flaky compaction daemon test
wohali commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315185827 OK looked at a couch.log. We have a race where the compaction daemon finishes compacting the test DB, then immediately starts compacting it **again**, so our check for the db to be idle fails. ``` [info] 2017-06-16T18:49:25.122688Z nonode@nohost <0.13883.1> Starting compaction for db "eunit-test-db-1497638926674066" [notice] 2017-06-16T18:49:25.383106Z nonode@nohost <0.13883.1> Compaction swap for db: /home/travis/build/apache/couchdb/tmp/data/eunit-test-db-1497638926674066.couch 1646789 53445 [info] 2017-06-16T18:49:25.386118Z nonode@nohost <0.13883.1> Compaction for db "eunit-test-db-1497638926674066" completed. [info] 2017-06-16T18:49:25.390952Z nonode@nohost <0.16501.1> Compaction started for db: eunit-test-db-1497638926674066 idx: _design/foo [notice] 2017-06-16T18:49:25.434478Z nonode@nohost <0.13891.1> Compaction swap for view /home/travis/build/apache/couchdb/tmp/data/.eunit-test-db-1497638926674066_design/mrview/ee2c720a13443ab1d50210242730ca31.view 391267 28800 [notice] 2017-06-16T18:49:25.443473Z nonode@nohost <0.13662.1> config: [compactions] _default deleted for reason nil [info] 2017-06-16T18:49:25.443559Z nonode@nohost <0.16501.1> Compaction finished for db: eunit-test-db-1497638926674066 idx: _design/foo [error] 2017-06-16T18:49:25.472035Z nonode@nohost <0.13891.1> gen_server <0.13891.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'$gen_cast',delete} state: {st,couch_mrview_index,{mrst,<<238,44,114,10,19,68,58,177,213,2,16,36,39,48,202,49>>,<0.16503.1>,#Ref<0.0.6.37429>,<<"eunit-test-db-1497638926674066">>,<<"_design/foo">>,<<"javascript">>,[],false,false,{[]},[{mrview,0,0,0,[<<"foo3">>,<<"foo2">>,<<"foo">>],[],<<"function(doc) { emit(doc._id, doc); }">>,{btree,<0.16503.1>,{26184,{400,[]},18346},undefined,undefined,#Fun,#Fun,snappy},nil,nil,false,false,[]}],{btree,<0.16503.1>,{7946,[],7997},undefined,undefined,undefined,nil,snappy},nil,401,0,undefined,undefined,undefined,undefined,undefined,nil},<0.13894.1>,<0.13895.1>,[],false,false} [error] 2017-06-16T18:49:25.475163Z nonode@nohost <0.13891.1> CRASH REPORT Process (<0.13891.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:722) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index,init,['Argument__1']}, ancestors: [<0.13890.1>], messages: [], links: [<0.13894.1>,<0.13895.1>,<0.13861.1>], dictionary: [], trap_exit: false, status: running, heap_size: 2586, stack_size: 27, reductions: 31341 [error] 2017-06-16T18:49:25.476680Z nonode@nohost <0.13895.1> gen_server <0.13895.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state: {st,<0.13891.1>,couch_mrview_index,undefined} [error] 2017-06-16T18:49:25.477461Z nonode@nohost <0.13895.1> CRASH REPORT Process (<0.13895.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:744) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index_compactor,init,['Argument__1']}, ancestors: [<0.13891.1>,<0.13890.1>], messages: [], links: [], dictionary: [], trap_exit: true, status: running, heap_size: 610, stack_size: 27, reductions: 194 [error] 2017-06-16T18:49:25.478441Z nonode@nohost <0.13894.1> gen_server <0.13894.1> terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state: {st,<0.13891.1>,couch_mrview_index,undefined} [error] 2017-06-16T18:49:25.479197Z nonode@nohost <0.13894.1> CRASH REPORT Process (<0.13894.1>) with 0 neighbors exited with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) at gen_server:terminate/6(line:744) <= proc_lib:init_p_do_apply/3(line:239); initial_call: {couch_index_updater,init,['Argument__1']}, ancestors: [<0.13891.1>,<0.13890.1>], messages: [], links: [], dictionary: [], trap_exit: true, status: running, heap_size: 1598, stack_size: 27, reductions: 596288 [error] 2017-06-16T18:49:25.479677Z nonode@nohost <0.13861.1> gen_server couch_index_server terminated with reason: no such process or port in call to gen_server:call(<0.16503.1>, close, infinity) last msg: {'EXIT',<0.13891.1>,{noproc,{gen_server,call,[<0.16503.1>,close,infinity]}}} state:
[GitHub] wohali commented on issue #638: Jenkins disks filling up
wohali commented on issue #638: Jenkins disks filling up URL: https://github.com/apache/couchdb/issues/638#issuecomment-315184379 I talked with INFRA just now and handed them a pointer to https://github.com/apache/couchdb-ci/blob/master/bin/cleanup-docker.sh . They're going to put something similar in a cron job on the Jenkins build agents. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali closed issue #638: Jenkins disks filling up
wohali closed issue #638: Jenkins disks filling up URL: https://github.com/apache/couchdb/issues/638 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #674: Flaky compaction daemon test
wohali commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315184184 #638 is out-of-disk-space on Jenkins. This is unrelated. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #638: EUnit compaction daemon timeout
wohali commented on issue #638: EUnit compaction daemon timeout URL: https://github.com/apache/couchdb/issues/638#issuecomment-315178290 Again @ https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/92/pipeline/41, but: ``` [warning] 2017-07-13T17:20:13.606448Z nonode@nohost <0.15086.1> Compaction daemon - skipping database `_dbs` compaction: the estimated necessary disk space is about 53890 bytes but the currently available disk space is 0 bytes. ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #638: EUnit compaction daemon timeout
wohali commented on issue #638: EUnit compaction daemon timeout URL: https://github.com/apache/couchdb/issues/638#issuecomment-315178290 Again @ https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/92/pipeline/41 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #675: couchdb_os_daemons_tests fails assertEqual
wohali commented on issue #675: couchdb_os_daemons_tests fails assertEqual URL: https://github.com/apache/couchdb/issues/675#issuecomment-315178171 Again @ https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/92/pipeline/49 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB » master #91
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/91/
[Jenkins] FAILURE: CouchDB » master #92
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/92/
[GitHub] wohali commented on issue #670: Failure in ets_lru eunit tests
wohali commented on issue #670: Failure in ets_lru eunit tests URL: https://github.com/apache/couchdb/issues/670#issuecomment-315147913 https://github.com/apache/couchdb/commit/f77a78f4d885aba0bf7bbeb607997b77de196b18 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali closed issue #670: Failure in ets_lru eunit tests
wohali closed issue #670: Failure in ets_lru eunit tests URL: https://github.com/apache/couchdb/issues/670 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #674: Flaky compaction daemon test
davisp commented on issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674#issuecomment-315147326 This is probably related to #638 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB » master #90
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/90/
[GitHub] wohali commented on issue #633: EUnit replicator tests timing out
wohali commented on issue #633: EUnit replicator tests timing out URL: https://github.com/apache/couchdb/issues/633#issuecomment-315146423 Another instance of this * https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/87/pipeline/47 * `couch_replicator_small_max_request_size_target:124: should_replicate...*timed out*` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #638: EUnit compaction daemon timeout
wohali commented on issue #638: EUnit compaction daemon timeout URL: https://github.com/apache/couchdb/issues/638#issuecomment-315146182 This is back: https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/88/pipeline/49 https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/88/pipeline/48 https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/87/pipeline/41 https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/87/pipeline/42 https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/89/pipeline/41 module 'couchdb_compaction_daemon_tests' Compaction daemon tests couchdb_compaction_daemon_tests:75: should_compact_by_default_rule...*timed out* undefined couchdb_compaction_daemon_tests:106: should_compact_by_dbname_rule...*timed out* undefined Need to analyze the couch logs to see if we're running out of disk space. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali opened a new issue #638: EUnit compaction daemon timeout
wohali opened a new issue #638: EUnit compaction daemon timeout URL: https://github.com/apache/couchdb/issues/638 ``` module 'couchdb_compaction_daemon_tests' Compaction daemon tests couchdb_compaction_daemon_tests:74: should_compact_by_default_rule...*timed out* undefined couchdb_compaction_daemon_tests:105: should_compact_by_dbname_rule...*timed out* undefined ``` * https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/41/pipeline/41 * https://couchdb-vm2.apache.org/ci_errorlogs/jenkins-couchdb-41-2017-06-24T14:43:39.566358/couchlog.tar.gz We've seen this before as [COUCHDB-3344](https://issues.apache.org/jira/browse/COUCHDB-3344) and attempts to fix it as recent as 2017.05.20 have failed. Full history: This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali opened a new issue #675: couchdb_os_daemons_tests fails assertEqual
wohali opened a new issue #675: couchdb_os_daemons_tests fails assertEqual URL: https://github.com/apache/couchdb/issues/675 ## Expected Behavior `couchdb_os_daemons_tests:187: should_die_quickly` should pass... ## Current Behavior ``` couchdb_os_daemons_tests:187: should_die_quickly...*failed* in function couchdb_os_daemons_tests:'-check_dead/2-fun-3-'/2 (test/couchdb_os_daemons_tests.erl, line 231) in call from couchdb_os_daemons_tests:check_dead/2 (test/couchdb_os_daemons_tests.erl, line 231) in call from couchdb_os_daemons_tests:should_halts/2 (test/couchdb_os_daemons_tests.erl, line 210) **error:{assertEqual_failed,[{module,couchdb_os_daemons_tests}, {line,231}, {expression,"D # daemon . status"}, {expected,halted}, {value,running}]} ``` Jenkins run: * https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/87/pipeline/49 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp opened a new issue #674: Flaky compaction daemon test
davisp opened a new issue #674: Flaky compaction daemon test URL: https://github.com/apache/couchdb/issues/674 Originally reported by @wohali here: https://github.com/apache/couchdb/issues/552#issuecomment-312722372 https://travis-ci.org/apache/couchdb/jobs/243780116 ``` module 'couchdb_compaction_daemon_tests' Compaction daemon tests couchdb_compaction_daemon_tests:74: should_compact_by_default_rule...*failed* in function couchdb_compaction_daemon_tests:'-should_compact_by_default_rule/1-fun-6-'/1 (test/couchdb_compaction_daemon_tests.erl, line 104) in call from couchdb_compaction_daemon_tests:'-should_compact_by_default_rule/1-fun-7-'/1 (test/couchdb_compaction_daemon_tests.erl, line 104) **error:{assertion_failed,[{module,couchdb_compaction_daemon_tests}, {line,104}, {expression,"is_idle ( DbName )"}, {expected,true}, {value,false}]} ``` And again in https://travis-ci.org/apache/couchdb/jobs/243544740 And again in https://travis-ci.org/apache/couchdb/jobs/243303511 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283
davisp commented on issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283 URL: https://github.com/apache/couchdb/issues/552#issuecomment-315144090 Hrm, I'm gonna open a new ticket with your comment then. I don't think these two issues are related but those failures do look to be flaky tests. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp opened a new issue #670: Failure in ets_lru eunit tests
davisp opened a new issue #670: Failure in ets_lru eunit tests URL: https://github.com/apache/couchdb/issues/670 eunit output: ``` ==> ets_lru (eunit) Compiled src/ets_lru.erl Compiled test/ets_lru_test.erl EUnit module 'ets_lru_test' Test LRU lifecycle ets_lru_test:17: lifecyle_test_ (ets_lru:start_link/2 returned an LRU)...ok ets_lru_test:21: lifecyle_test_ (Destroyed the LRU ok)...ok [done in 0.006 s] Test tables names ets_lru_test:37: table_names_test_ (foo_objects exists)...ok ets_lru_test:41: table_names_test_ (foo_atimes exists)...ok ets_lru_test:45: table_names_test_ (foo_ctimes exists)...ok ets_lru_test:49: table_names_test_ (LRU stopped normally)...ok ets_lru_test:56: table_names_test_ (foo_objects doesn't exists)...ok ets_lru_test:60: table_names_test_ (foo_atimes doesn't exists)...ok ets_lru_test:64: table_names_test_ (foo_ctimes doesn't exists)...ok [done in 0.021 s] Test basic behavior ets_lru_test:85: basic_behavior_test_ (Lookup returned the inserted value)...ok ets_lru_test:91: basic_behavior_test_ (Dirty lookup returned the inserted value)...ok ets_lru_test:98: basic_behavior_test_ (Lookup returned the inserted value)...ok ets_lru_test:102: basic_behavior_test_ (Insert new value)...ok ets_lru_test:106: basic_behavior_test_ (Lookup returned the newly inserted value)...ok ets_lru_test:112: basic_behavior_test_ (Lookup returned the inserted value)...ok ets_lru_test:116: basic_behavior_test_ (Remove value)...ok ets_lru_test:120: basic_behavior_test_ (Lookup returned not_found for removed value)...ok ets_lru_test:126: basic_behavior_test_ (Lookup returned the inserted value)...ok ets_lru_test:130: basic_behavior_test_ (Clear LRU)...ok ets_lru_test:134: basic_behavior_test_ (Lookup returned not_found after a clear)...ok [done in 0.033 s] Test LRU options ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_objects,1}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_objects,5}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_objects,923928342098203942}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_size,1}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_size,5}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_size,2342923423942309423094}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_lifetime,1}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_lifetime,5}])...ok ets_lru_test:246: test_good_opts (LRU created ok with options: [{max_lifetime,1244209909180928348}])...ok ets_lru_test:253: test_bad_opts (LRU failed with bad options: {bingo,bango})...ok undefined *** instantiation of subtests failed *** **in function ets_lru_test:test_bad_opts/2 (test/ets_lru_test.erl, line 251) called as test_bad_opts("\f",{error,{already_started,<0.685.0>}}) **error:function_clause undefined *** instantiation of subtests failed *** **in function ets_lru_test:test_bad_opts/2 (test/ets_lru_test.erl, line 251) called as test_bad_opts([true],{error,{already_started,<0.685.0>}}) **error:function_clause [done in 0.030 s] Test LRU limits ets_lru_test:258: test_limits (Max object count ok)...[0.105 s] ok ets_lru_test:263: test_limits (Max size ok)...[0.218 s] ok ets_lru_test:269: test_limits (Expire leaves new entries)...[0.028 s] ok ets_lru_test:276: test_limits (Entry was expired)...[0.150 s] ok [done in 0.516 s] Test match functions ets_lru_test:191: lru_match_test_ (Empty match)...ok ets_lru_test:198: lru_match_test_ (Single match)...ok ets_lru_test:208: lru_match_test_ (Multiple match)...ok ets_lru_test:214: lru_match_test_ (Empty match_object)...ok ets_lru_test:221: lru_match_test_ (Single match_object (registered))...ok ets_lru_test:226: lru_match_test_ (Single match_object (pid))...ok ets_lru_test:236: lru_match_test_ (Multiple match_object)...ok [done in 0.054 s] [done in 0.667 s] module 'ets_lru' === Failed: 0. Skipped: 0. Passed: 41. ``` There's no associated log output. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #670: Failure in ets_lru eunit tests
wohali commented on issue #670: Failure in ets_lru eunit tests URL: https://github.com/apache/couchdb/issues/670#issuecomment-315142131 @davisp Be sure to bump rebar.config.script in apache/couchdb !!! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #549: [Jenkins] timeout triggered by all_dbs_active
davisp commented on issue #549: [Jenkins] timeout triggered by all_dbs_active URL: https://github.com/apache/couchdb/issues/549#issuecomment-315141842 This is a duplicate of #571. The timeout error is the first error seen when you scroll up in the log. But if you keep going you'll see this bit in the logs: ``` module 'couchdb_os_daemons_tests' OS Daemons tests couchdb_os_daemons_tests:107: should_check_daemon...ok couchdb_os_daemons_tests:113: should_check_daemon_table_form...ok couchdb_os_daemons_tests:120: should_clean_tables_on_daemon_remove...[0.544 s] ok couchdb_os_daemons_tests:127: should_spawn_multiple_daemons...[0.618 s] ok undefined *** context cleanup failed *** **in function test_util:stop_sync_throw/4 (src/test_util.erl, line 160) in call from couchdb_os_daemons_tests:teardown/2 (test/couchdb_os_daemons_tests.erl, line 58) **throw:{timeout,os_daemon_stop} undefined *** context setup failed *** **in function meck_proc:start/2 (src/meck_proc.erl, line 96) called as start(couch_stats,[passthrough]) in call from test_util:mock/1 (src/test_util.erl, line 244) in call from test_util:'-mock/1-lc$^0/1-0-'/1 (src/test_util.erl, line 237) in call from test_util:start/3 (src/test_util.erl, line 225) in call from couchdb_os_daemons_tests:setup/1 (test/couchdb_os_daemons_tests.erl, line 47) **error:{already_started,<0.3624.1>} ``` We failed to shutdown couch properl which leaves it in a weird state which causes a lot of other failures as well. Given that this was fixed I'm closing and we can reopen if it happens again. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #669: Test failure in compact.js
wohali commented on issue #669: Test failure in compact.js URL: https://github.com/apache/couchdb/issues/669#issuecomment-315141786 @davisp we lose it because `dev/run` nukes the logfile when restarting the node. I considered changing this code about a week ago, but it would never clean up the logfile in that case, making a local dev instance's logfile grow until someone manually cleaned it out. In short `dev/run` should be enhanced so node restart doesn't wipe a logfile, but node initial-startup does. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB » master #89
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/89/
[GitHub] wohali commented on issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283
wohali commented on issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283 URL: https://github.com/apache/couchdb/issues/552#issuecomment-315141332 The previous comment from me was referencing an entirely different test, but one that I bisected back to @janl 's change. We can close for now but if that assertion comes up again we will have this "paper trail" to possibly indicate where it came from. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali closed issue #664: INSTALL.Unix.md: error when following instructions for Debian
wohali closed issue #664: INSTALL.Unix.md: error when following instructions for Debian URL: https://github.com/apache/couchdb/issues/664 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali closed pull request #672: Change recommended install path to /opt/couchdb
wohali closed pull request #672: Change recommended install path to /opt/couchdb URL: https://github.com/apache/couchdb/pull/672 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali closed pull request #671: Improve UNIX dependency installation docs (Node.JS, Sphinx)
wohali closed pull request #671: Improve UNIX dependency installation docs (Node.JS, Sphinx) URL: https://github.com/apache/couchdb/pull/671 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] nickva commented on issue #671: Improve UNIX dependency installation docs (Node.JS, Sphinx)
nickva commented on issue #671: Improve UNIX dependency installation docs (Node.JS, Sphinx) URL: https://github.com/apache/couchdb/pull/671#issuecomment-315136301 +1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283
davisp commented on issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283 URL: https://github.com/apache/couchdb/issues/552#issuecomment-315134975 Gonna close this as a duplicate of 655. The previous comment from @wohali is referencing an entirely different test so am assuming that was just having too many issue tabs open at once. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp closed issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283
davisp closed issue #552: [Jenkins] view monitor failure in couchdb_views_tests/couchdb_1283 URL: https://github.com/apache/couchdb/issues/552 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] nickva commented on issue #669: Test failure in compact.js
nickva commented on issue #669: Test failure in compact.js URL: https://github.com/apache/couchdb/issues/669#issuecomment-315134138 I did some of that in the jenkins-pipeline branch: https://github.com/apache/couchdb/blob/32eb49a0c2c26315aed8bb47befba915cd071f55/Makefile#L92-L103 It's a good idea. Even crazier could have a mini benchmark - try to write to disk, read back, run a few cpu speed tests, memory usage etc. And maybe decide test environment is just crappy and give up. Cause it certainly seems crappy a lot of the times. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #666: Move _users _design/auth into Erlang
davisp commented on issue #666: Move _users _design/auth into Erlang URL: https://github.com/apache/couchdb/issues/666#issuecomment-315133198 +1 with the caveat that we should't do this via enabling the erlang view server since that's leads to other issues (unless until Erlang figures out sandboxing). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] couchdb-ets-lru pull request #5: Fix flaky tests
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-ets-lru/pull/5 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] asfgit closed issue #670: Failure in ets_lru eunit tests
asfgit closed issue #670: Failure in ets_lru eunit tests URL: https://github.com/apache/couchdb/issues/670 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on issue #669: Test failure in compact.js
davisp commented on issue #669: Test failure in compact.js URL: https://github.com/apache/couchdb/issues/669#issuecomment-315132166 Could be. I can't figure out how we're not getting logs from the tests that are reported as passing in the same run. @wohali What do you think about adding a few commands to the script just before starting the javascript test suite to check on host health? I'm thinking of checking things like df, free, netstat, and maybe something like `ps ax | wc -l` or similar to try and get an idea of what we might be hitting. Also might be useful to add collecting whatever logs OOM-killer actions into our couchlog uploads incase we're seeing memory issues that you mentioned the other day. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB » master #88
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/88/
[GitHub] couchdb-ets-lru issue #5: Fix flaky tests
Github user nickva commented on the issue: https://github.com/apache/couchdb-ets-lru/pull/5 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nickva closed pull request #627: Pass UserCtx to fabric's all_docs from mango query
nickva closed pull request #627: Pass UserCtx to fabric's all_docs from mango query URL: https://github.com/apache/couchdb/pull/627 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] couchdb-ets-lru pull request #5: Fix flaky tests
GitHub user davisp opened a pull request: https://github.com/apache/couchdb-ets-lru/pull/5 Fix flaky tests The bad options test had a race condition between the process exit and the unregistering of the name. If the unregister didn't happen quickly enough then the next bad options test would break with an already_started error. Fixes apache/couchdb#670 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/couchdb-ets-lru 670-fix-flaky-test Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-ets-lru/pull/5.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5 commit 8c64f20565bed7599ec8e2b7561f0636ccee2bb5 Author: Paul J. DavisDate: 2017-07-13T16:24:45Z Fix flaky tests The bad options test had a race condition between the process exit and the unregistering of the name. If the unregister didn't happen quickly enough then the next bad options test would break with an already_started error. Fixes apache/couchdb#670 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nickva closed issue #535: Mango Query won't run on _users database
nickva closed issue #535: Mango Query won't run on _users database URL: https://github.com/apache/couchdb/issues/535 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] tonysun83 commented on issue #627: Pass UserCtx to fabric's all_docs from mango query
tonysun83 commented on issue #627: Pass UserCtx to fabric's all_docs from mango query URL: https://github.com/apache/couchdb/pull/627#issuecomment-315130740 +1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB » master #87
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/87/
[GitHub] davisp closed issue #655: Failure waiting for db shutdown in couchdb_1283 test
davisp closed issue #655: Failure waiting for db shutdown in couchdb_1283 test URL: https://github.com/apache/couchdb/issues/655 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp closed pull request #668: Fix timeout in couchdb_views_test for couchdb_1283
davisp closed pull request #668: Fix timeout in couchdb_views_test for couchdb_1283 URL: https://github.com/apache/couchdb/pull/668 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp closed issue #649: couch_mrview_changes_since_tests gen_server failing with unknown_info
davisp closed issue #649: couch_mrview_changes_since_tests gen_server failing with unknown_info URL: https://github.com/apache/couchdb/issues/649 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp closed pull request #667: 649 fix mrview changes since test
davisp closed pull request #667: 649 fix mrview changes since test URL: https://github.com/apache/couchdb/pull/667 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] jdc91 closed issue #21: Replication does not work across multiple instances of docker
jdc91 closed issue #21: Replication does not work across multiple instances of docker URL: https://github.com/apache/couchdb-docker/issues/21 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] jdc91 commented on issue #21: Replication does not work across multiple instances of docker
jdc91 commented on issue #21: Replication does not work across multiple instances of docker URL: https://github.com/apache/couchdb-docker/issues/21#issuecomment-315042179 Wow thanks wohali :) Got the replication working using the exact container IP's which can be found using ` docker inspect ` ![image](https://user-images.githubusercontent.com/3422709/28162825-15c7e7ae-67e6-11e7-84dd-ac743ebd9cac.png) So for the set up the ips were actually. 172.17.0.2:5984 172.17.0.3:5984 172.17.0.4:5984 Wonder why the bound addresses did not work though. Since I could access futon using the http://localhost:/_utils/ ip. I had bound port 5984 to a specific host port in the host. Each port corresponded to the ip! ![image](https://user-images.githubusercontent.com/3422709/28162553-1f4a153c-67e5-11e7-8a16-b4d46d124b15.png) All other PUT/POST/GET requests using POSTMAN worked using the bound IP. Maybe replication fails when the port forwarding happened. I however did not try out the docker-compose option, since this was quite trivial.Thanks for the help Wohali, really appreciate it! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] jdc91 commented on issue #21: Replication does not work across multiple instances of docker
jdc91 commented on issue #21: Replication does not work across multiple instances of docker URL: https://github.com/apache/couchdb-docker/issues/21#issuecomment-315042179 Wow thanks wohali :) Got the replication working using the exact container IP's which can be found using ` docker inspect ` ![image](https://user-images.githubusercontent.com/3422709/28162825-15c7e7ae-67e6-11e7-84dd-ac743ebd9cac.png) So for the set up the ips were actually. 172.17.0.2:5984 172.17.0.3:5984 172.17.0.4:5984 Wonder why the bound addresses did not work though. because I could access futon using the http://localhost:/_utils/ I had bound port 5984 to a specific host port in the host. Each port corresponded to the ip! ![image](https://user-images.githubusercontent.com/3422709/28162553-1f4a153c-67e5-11e7-8a16-b4d46d124b15.png) Even other requests using POSTMAN worked. Maybe replication fails when the port forwarding happened. Did not try out the docker-compose option though since this is quite trivial.Thanks for the help, Wohali really appreciate it! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] fkaempfer commented on issue #475: COUCHDB-3367: Require server admin user for db/_compact and db/_view_cleanup endpoints
fkaempfer commented on issue #475: COUCHDB-3367: Require server admin user for db/_compact and db/_view_cleanup endpoints URL: https://github.com/apache/couchdb/pull/475#issuecomment-315009764 Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #673: JS delayed_commits: connection refused
wohali commented on issue #673: JS delayed_commits: connection refused URL: https://github.com/apache/couchdb/issues/673#issuecomment-314987550 Also in Travis: * https://travis-ci.org/apache/couchdb/jobs/253082338#L5761 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #669: Test failure in compact.js
wohali commented on issue #669: Test failure in compact.js URL: https://github.com/apache/couchdb/issues/669#issuecomment-314986905 See #673 - related? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[Jenkins] FAILURE: CouchDB » jenkins-build-packages #9
Boo, we failed. https://builds.apache.org/job/CouchDB/job/jenkins-build-packages/9/
[GitHub] wohali opened a new pull request #672: Change recommended install path to /opt/couchdb
wohali opened a new pull request #672: Change recommended install path to /opt/couchdb URL: https://github.com/apache/couchdb/pull/672 This matches what we do in couchdb-pkg, where we always install to `/opt/couchdb`. It also matches where the Docker images place CouchDB. Also includes pointers to couchdb-pkg daemon scripts. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali opened a new pull request #671: Improve UNIX dependency installation docs (Node.JS, Sphinx)
wohali opened a new pull request #671: Improve UNIX dependency installation docs (Node.JS, Sphinx) URL: https://github.com/apache/couchdb/pull/671 Closes #664 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Closed] (COUCHDB-3245) couchjs -S option doesn't have any effect
[ https://issues.apache.org/jira/browse/COUCHDB-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Vatamaniuc closed COUCHDB-3245. > couchjs -S option doesn't have any effect > - > > Key: COUCHDB-3245 > URL: https://issues.apache.org/jira/browse/COUCHDB-3245 > Project: CouchDB > Issue Type: Bug >Reporter: Nick Vatamaniuc > > currently -S option of couchjs sets stack _chunk_ size for js contexts > Reference: to > https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/JSAPI_reference/JS_NewContext > Documentation recommends 8K and I have seen cases where it was raised to 1G+ > in production!. That doesn't seem right at all and also probably kills > performance and eats memory. > Docs from above say: > > The stackchunksize parameter does not control the JavaScript stack size. > > (The JSAPI does not provide a way to adjust the stack depth limit.) Passing > > a large number for stackchunksize is a mistake. In a DEBUG build, large > > chunk sizes can degrade performance dramatically. The usual value of 8192 > > is recommended > Instead we should be setting the max gc value which is set in the runtime > {{JS_NewRuntime(uint32_t maxbytes)}} > Experimentally a large maxbytes seems to fix out of memory error caused by > large views. I suspect that it works because it stops GC. At some point we > probably drops some object, GC collects them and we crash... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (COUCHDB-3245) couchjs -S option doesn't have any effect
[ https://issues.apache.org/jira/browse/COUCHDB-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Vatamaniuc resolved COUCHDB-3245. -- Resolution: Fixed > couchjs -S option doesn't have any effect > - > > Key: COUCHDB-3245 > URL: https://issues.apache.org/jira/browse/COUCHDB-3245 > Project: CouchDB > Issue Type: Bug >Reporter: Nick Vatamaniuc > > currently -S option of couchjs sets stack _chunk_ size for js contexts > Reference: to > https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/JSAPI_reference/JS_NewContext > Documentation recommends 8K and I have seen cases where it was raised to 1G+ > in production!. That doesn't seem right at all and also probably kills > performance and eats memory. > Docs from above say: > > The stackchunksize parameter does not control the JavaScript stack size. > > (The JSAPI does not provide a way to adjust the stack depth limit.) Passing > > a large number for stackchunksize is a mistake. In a DEBUG build, large > > chunk sizes can degrade performance dramatically. The usual value of 8192 > > is recommended > Instead we should be setting the max gc value which is set in the runtime > {{JS_NewRuntime(uint32_t maxbytes)}} > Experimentally a large maxbytes seems to fix out of memory error caused by > large views. I suspect that it works because it stops GC. At some point we > probably drops some object, GC collects them and we crash... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (COUCHDB-3245) couchjs -S option doesn't have any effect
[ https://issues.apache.org/jira/browse/COUCHDB-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085228#comment-16085228 ] Nick Vatamaniuc commented on COUCHDB-3245: -- @gdelfino the issues was fixed just forgot to close the ticket. > couchjs -S option doesn't have any effect > - > > Key: COUCHDB-3245 > URL: https://issues.apache.org/jira/browse/COUCHDB-3245 > Project: CouchDB > Issue Type: Bug >Reporter: Nick Vatamaniuc > > currently -S option of couchjs sets stack _chunk_ size for js contexts > Reference: to > https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/JSAPI_reference/JS_NewContext > Documentation recommends 8K and I have seen cases where it was raised to 1G+ > in production!. That doesn't seem right at all and also probably kills > performance and eats memory. > Docs from above say: > > The stackchunksize parameter does not control the JavaScript stack size. > > (The JSAPI does not provide a way to adjust the stack depth limit.) Passing > > a large number for stackchunksize is a mistake. In a DEBUG build, large > > chunk sizes can degrade performance dramatically. The usual value of 8192 > > is recommended > Instead we should be setting the max gc value which is set in the runtime > {{JS_NewRuntime(uint32_t maxbytes)}} > Experimentally a large maxbytes seems to fix out of memory error caused by > large views. I suspect that it works because it stops GC. At some point we > probably drops some object, GC collects them and we crash... -- This message was sent by Atlassian JIRA (v6.4.14#64029)