<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:39:42 UTC 2024

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 append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LUDOC-31] servicenode is not documented</title>
                <link>https://jira.whamcloud.com/browse/LUDOC-31</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;&lt;tt&gt;--servicenode&lt;/tt&gt; is not documented in the manual&lt;/p&gt;</description>
                <environment></environment>
        <key id="12741">LUDOC-31</key>
            <summary>servicenode is not documented</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="jessica">Jessica A. Popp</assignee>
                                    <reporter username="rhenwood">Richard Henwood</reporter>
                        <labels>
                    </labels>
                <created>Wed, 21 Dec 2011 12:35:51 +0000</created>
                <updated>Tue, 27 Nov 2012 07:19:27 +0000</updated>
                            <resolved>Wed, 1 Feb 2012 14:48:22 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                            <comments>
                            <comment id="25089" author="rhenwood" created="Wed, 21 Dec 2011 12:45:41 +0000"  >&lt;p&gt;I have just had a chat with Brian on this topic, the conversation went as follows:&lt;/p&gt;


&lt;p&gt;&lt;b&gt;B&lt;/b&gt; historically, when one formats a target with a failnode and then registers it, the node it was registered from and the fail node are both written as locations for the target.&lt;br/&gt;
when you use &amp;#45;&amp;#45;servicenode the node you register from is no longer listed as a service node but the listed --servicenodes are.&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; this makes it possible to register the target somewhere other than where you intend it to run, for example.&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; so imagine &amp;#45;&amp;#45;servicenode as being the merging of --failnode and (a fictitious and implied) --register-from-node parameter.  if that makes sense.&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; imho, &amp;#45;&amp;#45;servicenode is superior and less confusing than the old implict +&amp;#45;&amp;#45;failnode behaviour.&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; since it makes absolutely clear which nodes will be service nodes and doesn&apos;t hide one of them as the node being registered from.&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; and it also doesn&apos;t require a specific one (or any, iiuc) of the service nodes to be up in order to register the target&lt;br/&gt;
&lt;b&gt;Me&lt;/b&gt; what is a service node?&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; a node that provides service for the target&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; i.e. an OSS or MDS&lt;br/&gt;
&lt;b&gt;Me&lt;/b&gt; is Active-Active failover an example of when you would want to register an target without a service node?&lt;br/&gt;
&lt;b&gt;B&lt;/b&gt; so normally if you have two nodes (A and B) for a target you do:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;A # mkfs.lustre ... --failnode B /dev/sda
A # mount -t lustre /dev/sda /mnt
with service node you (can) &lt;span class=&quot;code-keyword&quot;&gt;do&lt;/span&gt;:
C # mkfs.lustre ... --servicenode A --servicenode B
C # mount -t lustre /dev/sda /mnt
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&lt;b&gt;B&lt;/b&gt; and nodes A and B will be configured as the nodes that hosts go to for that target&lt;br/&gt;
&lt;b&gt;J&lt;/b&gt; the service node option is just a way to control what nids are registered to the mgs&lt;/p&gt;</comment>
                            <comment id="25120" author="bobijam" created="Thu, 22 Dec 2011 03:46:02 +0000"  >&lt;p&gt;manual update tracking at &lt;a href=&quot;http://review.whamcloud.com/1904&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/1904&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="25128" author="rhenwood" created="Thu, 22 Dec 2011 09:31:58 +0000"  >&lt;p&gt;Excellent! Thanks for getting on this so quickly!&lt;/p&gt;</comment>
                            <comment id="27719" author="rhenwood" created="Wed, 1 Feb 2012 14:48:22 +0000"  >&lt;p&gt;Bobijam&apos;s manual update has landed.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvl3r:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7180</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>