[
https://issues.apache.org/jira/browse/COUCHDB-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990122#comment-15990122
]
Joan Touzet commented on COUCHDB-3402:
--------------------------------------
With a little trickery, I managed to get stack traces showing where the
collision happens.
Path 1: {{gen_server:init_it/6 -> mem3_shards:init/1 ->
mem3_shards:get_update_seq/0 -> couch_server:create/2}}
Path 2: {{mem3_sync:initial_sync/1 -> mem3_shards:fold/2 ->
couch_server:create/2}}
It appears that Paths 1 and 2 start nearly simultaneously, with the bug
occurring when Path 2's {{couch_server:create/2}} completes before Path 1's.
This leads to the {{file_exists}} error bubbling back up to
{{mem3_shards:get_update_seq/0}} which doesn't know what to do with it.
> JS: dev/run timing out starting up nodes
> ----------------------------------------
>
> Key: COUCHDB-3402
> URL: https://issues.apache.org/jira/browse/COUCHDB-3402
> Project: CouchDB
> Issue Type: Bug
> Components: Test Suite
> Reporter: Joan Touzet
> Priority: Critical
>
> Seen this a bunch of times recently in the Jenkins infrastructure. May be a
> symptom of ASF Jenkins nodes being overloaded.
> {noformat}
> make[1]: Entering directory `/usr/src/couchdb/apache-couchdb-2.0.0-28dd801'
> # This might help with emfile errors during `make javascript`: ulimit -n 10240
> Failed to start all the nodes. Check the dev/logs/*.log for errors.
> make[1]: *** [javascript] Error 1
> make[1]: Leaving directory `/usr/src/couchdb/apache-couchdb-2.0.0-28dd801'
> make: *** [check] Error 2
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
