<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Thu May 23 11:48:26 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/JCBC-30/JCBC-30.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[JCBC-30] document warning on not-my-vbucket errors</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-30</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>During rebalance, WARNING level errors such as&lt;br/&gt;
WARN com.couchbase.client.CouchbaseConnection:  Reschedule read op due to NOT_MY_VBUCKET error: Cmd: 0 Opaque: 460 Key: membase-test-key-24 &lt;br/&gt;
can come up.  These are safe to ignore, as long as they&amp;#39;re small in number and do not persist for a long period of time.&lt;br/&gt;
&lt;br/&gt;
This needs to be documented somewhere in the manuals.</description>
                <environment></environment>
            <key id="16479">JCBC-30</key>
            <summary>document warning on not-my-vbucket errors</summary>
                <type id="2" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="ingenthr">Matt Ingenthron</assignee>
                                <reporter username="ingenthr">Matt Ingenthron</reporter>
                        <labels>
                    </labels>
                <created>Thu, 5 Apr 2012 10:38:23 -0500</created>
                <updated>Wed, 27 Feb 2013 13:10:00 -0600</updated>
                    <resolved>Wed, 27 Feb 2013 13:10:00 -0600</resolved>
                                            <fixVersion>1.1.0</fixVersion>
                                <component>docs</component>
                                <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="27425" author="SteveC" created="Wed, 16 May 2012 20:41:31 -0500"  >If safe to ignore, should the log level be INFO?&lt;br/&gt;
&lt;br/&gt;
When I see this error, couchbase reads fail with and the bucket being queried reindexes itself. The bucket is not readable during this period. Writes, however, seem ok&lt;br/&gt;
&lt;br/&gt;
Not sure if it is related or just a UI error, but the Admin console reports &amp;quot;-2929743.01979 resident %&amp;quot; under vbucket resources&lt;br/&gt;
</comment>
                    <comment id="37237" author="ingenthr" created="Wed, 29 Aug 2012 10:16:37 -0500"  >Yes, should be INFO log level.  I think this is fixed, but we&amp;#39;ll check.</comment>
                    <comment id="43894" author="daschl" created="Tue, 13 Nov 2012 09:43:22 -0600"  >In spy the mentioned log message is now a DEBUG. does this resolve the issue or is there something more to it?&lt;br/&gt;
&lt;br/&gt;
I wonder because its a &amp;quot;docs&amp;quot; issue and I don&amp;#39;t see specific info on what to document here.&lt;br/&gt;
&lt;br/&gt;
If not, we can safely close this one I think.&lt;br/&gt;
&lt;br/&gt;
Thanks,&lt;br/&gt;
Michael</comment>
                    <comment id="51568" author="ingenthr" created="Wed, 27 Feb 2013 13:10:00 -0600"  >This was fixed back in May of 2011.  There is no longer a warning.&lt;br/&gt;
&lt;br/&gt;
Note that there have been a couple of reported circumstances where users had an old spymemcached (which we do not prevent or warn against), and they&amp;#39;d still see these warnings.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>8603</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>