[
https://issues.apache.org/jira/browse/COUCHDB-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421166#comment-13421166
]
Tuyen Tran commented on COUCHDB-1444:
-------------------------------------
We've seen this problem twice now in the last 30 days (rock solid for two+
years otherwise). Our situation was same as above: view started returning
missing_named_view; restart fixed the issue. View was trivial; design doc had
just one view. Problem was localized to just that one view in that one
database. Nothing useful in the log.
VMWare
Unbuntu 10.04 LTS (GNU/Linux 2.6.32-24-server x86_64)
R13B03
couchdb 1.1.1
> missing_named_view error on existing javascript design doc and view
> -------------------------------------------------------------------
>
> Key: COUCHDB-1444
> URL: https://issues.apache.org/jira/browse/COUCHDB-1444
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 1.1.1
> Environment: Ubuntu 11.01 64 bit Erlang R13B03
> Reporter: Sam Lown
> Priority: Critical
> Labels: 404, bug, missing_named_view
> Attachments: couchdb-missing-view.log
>
>
> Moved over from issue: https://issues.apache.org/jira/browse/COUCHDB-1225
> which has similar symptoms but the view is written in Erlang.
> On our production server for no apparent reason, one of our views just
> suddenly stopped responding to requests. The design document was still
> visible in Futon and the "all" view did provide a list of documents. All
> other views in the ddoc responded with a 404
> {"error":"not_found","reason":"missing_named_view"}.
> Restarting the couchdb server resolved the issue, and I've as yet been unable
> to reproduce the problem.
> Here is the last successful log entry for the view:
> [Fri, 16 Mar 2012 13:14:19 GMT] [info] [<0.831.531>] 192.168.163.3 - -
> 'GET'
> /maxi/_design/Payment/_view/by_journey_id_and_sequence?startkey=%5B%229bd1647eb09fca1634a8a6129a8cff46%22%2C%7B%7D%5D&endkey=%5B%229bd1647eb09fca1634a8a6129a8cff46%22%5D&limit=1&descending=true&include_docs=true&reduce=false
> 200
> Many requests later to other documents and views, here is when requests
> stopped working, some 6 minutes later:
> [Fri, 16 Mar 2012 13:20:29 GMT] [info] [<0.4510.531>] 192.168.163.3 - -
> 'GET'
> /maxi/_design/Payment/_view/by_user_id_and_created_at?startkey=%5B%22a0d0912e031b8fd28c2f89f828eebb12%22%5D&endkey=%5B%22a0d0912e031b8fd28c2f89f828eebb12%22%2C%7B%7D%5D&reduce=true&skip=0&limit=1
> 404
> Here is the design document in question: https://gist.github.com/2050446
> I could see nothing in the logs out of the ordinary.
> Obviously, this problem is very alarming indeed and not something I've come
> across before in CouchDB. As you can see the view in question is related to
> Payments, which is something we really do not want to go wrong.
> Please let me know if I can provide more information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
