[ 
https://issues.apache.org/jira/browse/COUCHDB-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050491#comment-13050491
 ] 

Mike Leddy commented on COUCHDB-999:
------------------------------------

I noticed that what appears in the couch.log is somewhat difficult to 
understand:

[Thu, 16 Jun 2011 14:51:54 GMT] [error] [<0.886.0>] ** Generic server <0.886.0> 
terminating 
** Last message in was {'EXIT',<0.885.0>,
                               [68,117,112,108,105,99,97,116,101,115,32,111,
                                102,32,"1307433591F4608",32,100,101,116,101,
                                99,116,101,100,32,105,110,32,"iris",32,
                                "_design/admin",32,45,32,114,101,98,117,105,
                                108,100,32,114,101,113,117,105,114,101,100]}
** When Server state == {file,{file_descriptor,prim_file,{#Port<0.2581>,56}},
                              18063917287}
** Reason for termination == 
** [68,117,112,108,105,99,97,116,101,115,32,111,102,32,"1307433591F4608",32,
    100,101,116,101,99,116,101,100,32,105,110,32,"iris",32,"_design/admin",32,
    45,32,114,101,98,117,105,108,100,32,114,101,113,117,105,114,101,100]

The exit message is not being shown as a normal 'string' in the log.

> Detect view indexes with duplicates in them
> -------------------------------------------
>
>                 Key: COUCHDB-999
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-999
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: Database Core
>    Affects Versions: 0.11.2, 1.0.1
>            Reporter: Adam Kocoloski
>             Fix For: 1.0.2, 1.1
>
>         Attachments: 
> 0001-Crash-if-duplicates-are-detected-during-view-compact.patch
>
>
> In COUCHDB-968 we discovered and fixed a bug that could introduce duplicate 
> documents in a database.  Under certain circumstances these duplicate 
> documents would introduce duplicate entries in view indexes.
> We can detect duplicates in the view group by looking for duplicate entries 
> in the docid => view key btree.  We can try to repair the view indexes by 
> removing the extra keys from the views, or we can just report that duplicates 
> exist in the view group and direct the user to rebuild that group.  We might 
> incorporate this code into the view compactor, or we might release it as a 
> separate standalone tool.
> I think my personal preference is to include any repair functionality in the 
> view compactor.  A separate standalone tool that simply reports the presence 
> of duplicates would also be a nice thing to have.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to