You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2013/02/04 00:10:12 UTC
[jira] [Updated] (COUCHDB-1666) Do not log errors on creating new
view index
[ https://issues.apache.org/jira/browse/COUCHDB-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Shorin updated COUCHDB-1666:
--------------------------------------
Attachment: COUCHDB-1666.1.patch
Patch attached.
This behaviour received from commit[1] about logging problems on opening databases.
[1]: https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=41667642
> Do not log errors on creating new view index
> --------------------------------------------
>
> Key: COUCHDB-1666
> URL: https://issues.apache.org/jira/browse/COUCHDB-1666
> Project: CouchDB
> Issue Type: Bug
> Reporter: Alexander Shorin
> Attachments: COUCHDB-1666.1.patch
>
>
> 1.3 may bring one more important change for users as logging errors on positive attempts to create new view index. This looks like:
> [Sun, 03 Feb 2013 22:16:23 GMT] [error] [<0.509.0>] Could not open file /var/lib/couchdb/.mailbox_design/mrview/e3d73d18920d243e87ddd8bbf54da21c.view: no such file or directory
> [Sun, 03 Feb 2013 22:31:33 GMT] [error] [<0.1437.0>] Could not open file /var/lib/couchdb/.mailbox_design/mrview/ac201fc14e4cd3e58c03679a5d6ded06.view: no such file or directory
> [Sun, 03 Feb 2013 22:35:39 GMT] [error] [<0.173.0>] Could not open file /var/lib/couchdb/.mailbox_design/mrview/782367e3d40790fcaba08e12ae1c8baa.view: no such file or directory
> While it's true that file is missed, but it will be created right after[1] (or failed one more time with more serious reason) so there is no reason to alert about since this error is self-healed.
> [1]: https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob;f=src/couch_mrview/src/couch_mrview_util.erl;h=ba4de2d6;hb=refs/heads/1.3.x#l515
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira