<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed May 22 04:12:07 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/MB-4189/MB-4189.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>[MB-4189] ns_server&apos;s concept of time is decoupled from the OS</title>
                <link>http://www.couchbase.com/issues/browse/MB-4189</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>When testing some systems in a lab environment, I&amp;#39;ve noticed that after the VM was paused and restarted, the OS is happy with the new time of day, but the ns_server erl VM is stuck in the past.  Negative effects of this are the log showing the wrong date and time and the graphs in the UI not working.&lt;br/&gt;
&lt;br/&gt;
This would seem to indicate any drift fixed at the OS level isn&amp;#39;t making it&amp;#39;s way into erl.  This is particularly bad for things that are paused/restarted, but could also affect those that just naturally drift or drift due to virtualization.&lt;br/&gt;
&lt;br/&gt;
Note: this hasn&amp;#39;t actually been observed against 2.0 Alpha, but it&amp;#39;s presumed to be there as well.  Filed there so it doesn&amp;#39;t get lost in the shift from 1.7 to 2.0.</description>
                <environment>RHEL 5.2 64-bit</environment>
            <key id="14860">MB-4189</key>
            <summary>ns_server&apos;s concept of time is decoupled from the OS</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</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="alkondratenko">Aleksey Kondratenko</assignee>
                                <reporter username="ingenthr">Matt Ingenthron</reporter>
                        <labels>
                        <label>1.8.1-release-notes</label>
                    </labels>
                <created>Sun, 14 Aug 2011 14:20:40 -0500</created>
                <updated>Sun, 13 May 2012 18:23:42 -0500</updated>
                    <resolved>Wed, 25 Apr 2012 17:06:28 -0500</resolved>
                            <version>1.7.1</version>
                <version>1.8.0</version>
                <version>2.0-beta</version>
                                <fixVersion>1.8.1</fixVersion>
                                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="21654" author="ingenthr" created="Sun, 14 Aug 2011 14:21:11 -0500"  >One workaround is to restart, but that isn&amp;#39;t intuitive and shouldn&amp;#39;t be necessary.</comment>
                    <comment id="24619" author="ingenthr" created="Sat, 25 Feb 2012 12:03:04 -0600"  >Assigning to Farshid for triage.</comment>
                    <comment id="25171" author="alkondratenko" created="Mon, 26 Mar 2012 13:10:21 -0500"  >use of os:timestamp is merged to 1.8.1. &lt;a href=&quot;http://review.couchbase.org/13611&quot;&gt;http://review.couchbase.org/13611&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
It quite possibly fixes this issue.</comment>
                    <comment id="26246" author="alkondratenko" created="Wed, 25 Apr 2012 17:06:28 -0500"  >This issue was indeed fixed</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Mon, 26 Mar 2012 13:10:21 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>6231</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>