-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Jenkins] timeout triggered by all_dbs_active #549
Comments
I looked at this one a bit more closely. The Makefile log output is here: https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/2.1.x/1/pipeline/49/
ok = config:set("couchdb", "max_dbs_open", "3", false),
EDIT: Thanks, @rnewson, for helping me see that the harness calls |
This is a really odd failure. My guess is we've hit a race condition where an attempt to open the database is happening prior to the database having been created yet, but I'm not comfortable enough with the We see in the couch.log file that the PUT to create the eunit test database returns with a 201, so presumably the database has been created. But just a few hundred milliseconds, later, we also see:
Question 1: Is it normal for a PUT to get back a 201 before all the shards have been created on disk? During the open call, we hit maybe_close_lru_db(#server{dbs_open=NumOpen, max_dbs_open=MaxOpen}=Server)
when NumOpen < MaxOpen ->
{ok, Server}; Question 2: Why did we fail that guard? So we get past the guard, head into close_int(none, _) ->
false; In this particular failure, we can't possibly have >100 dbs open already. I wonder if Question 3: Should we handle the special case of Also: I noticed couch/src/couch_server.erl:-define(MAX_DBS_OPEN, 100). but |
|
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:
We failed to shutdown couch properly 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. |
Add missing word "key" in "What is a partition?"
Current & Expected Behaviour
During an eunit test (
couchdb_mrview_cors_tests
) a request is made to retrieve the output of a view. It should succeed. Sometimes, it fails on a timeout.Possible Solution
In one failure, the attempt to create the database in the eunit test fails, running into an
all_dbs_active
error. This is unusual because the couch application has just started up and only a single database is created for this test.Perhaps we have a race condition in startup on in
couch_lru
?Your Environment
Jenkins automated build, 2.1.x branch, Debian 8, default Erlang (17), logs uploaded as
jenkins-couchdb-1-2017-05-29T02:02:45.043081
. Relevant paste here: https://paste.apache.org/sdgkThe text was updated successfully, but these errors were encountered: