Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Warning error with no proper message #109

Open
taris opened this issue Jun 13, 2012 · 4 comments
Open

Warning error with no proper message #109

taris opened this issue Jun 13, 2012 · 4 comments

Comments

@taris
Copy link

taris commented Jun 13, 2012

I am currently struggling with a bulk insert error that is occuring with a small set of documents:

{"error":"case_clause","reason":"{24,43}","stack":["fabric_doc_update:handle_message/3","rexi_utils:process_mailbox/6","rexi_utils:recv/6","fabric_doc_update:go/3","fabric:update_docs/3","chttpd_db:db_req/2","chttpd:handle_request/1","mochiweb_http:headers/5"]},"stack":["fabric_doc_update:handle_message/3","rexi_utils:process_mailbox/6","rexi_utils:recv/6","fabric_doc_update:go/3","fabric:update_docs/3","chttpd_db:db_req/2","chttpd:handle_request/1","mochiweb_http:headers/5"]}

Is there a way to find out what the reason "{24,43}" means (sometimes "{24,499}"). Unfortunately i am not able to reproduce the error every time and all documents are in the database, but it would be very helpful to get a proper message.
The complete size of all documents in that bulk insert is about ~1MB.

Thx alot!

@davisp
Copy link
Contributor

davisp commented Jun 13, 2012

Yeah, that's a bad match. Do you perhaps have a docid repeated in a call to _bulk_docs?

@taris
Copy link
Author

taris commented Jun 29, 2012

Sorry, for the late reply!

No, all docids are unique in each call - and the database does respond with an error for a specific document if it already exits - this is, of course, valid.
The interesting part is, that all documents have been created successfully and there are no missing docs. That is why this warning is so disturbing and leaves a "bad taste" :)

@nikita-volkov
Copy link

Experiencing a similar issue on cloudant. Here's server response:

{
  "stack":["fabric_doc_update:handle_message/3","rexi_utils:process_mailbox/6","fabric_doc_update:go/3","fabric:update_docs/3","chttpd_db:db_req/2","chttpd:handle_request/1","mochiweb_http:headers/5","proc_lib:init_p_do_apply/3"],
  "reason":"{12,18}",
  "error":"case_clause"
}

@ath88
Copy link

ath88 commented Mar 6, 2017

We had the same issue with a bigcouch cluster.

Eliminating duplicate keys in the posted document list fixed the problem.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants