forked from docs/doc-exports
Yang, Tong
48706b7552
Reviewed-by: Kacur, Michal <michal.kacur@t-systems.com> Co-authored-by: Yang, Tong <yangtong2@huawei.com> Co-committed-by: Yang, Tong <yangtong2@huawei.com>
20 lines
3.6 KiB
HTML
20 lines
3.6 KiB
HTML
<a name="mrs_01_24814"></a><a name="mrs_01_24814"></a>
|
|
|
|
<h1 class="topictitle1">Configuring HA for TimelineServer</h1>
|
|
<div id="body0000001533519124"><div class="section" id="mrs_01_24814__section169235553332"><h4 class="sectiontitle">Scenario</h4><p id="mrs_01_24814__p181667206313">As a role of the Yarn service, TimelineServer supports the HA mode since the current version. To prevent a single point of failure of TimelineServer, you can enable TimelineServer HA to ensure high availability of the TimelineServer role.</p>
|
|
<div class="note" id="mrs_01_24814__note1286611300323"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="mrs_01_24814__p1486614300321">Currently, clusters in IPv6 security mode do not support TimelineServer HA.</p>
|
|
<p id="mrs_01_24814__p12542135416223">This function applies to MRS 3.2.0-LTS.1 or later.</p>
|
|
</div></div>
|
|
</div>
|
|
<div class="section" id="mrs_01_24814__section0409636133611"><h4 class="sectiontitle">Impact on the System</h4><ul id="mrs_01_24814__ul1455211161518"><li id="mrs_01_24814__li1551211171512">Before the conversion, change the value of <strong id="mrs_01_24814__b123351419326">TLS_FLOAT_IP</strong> of TimelineServer to an available floating IP address. (In the case of a single instance, the service IP address of the node is used by default.)</li><li id="mrs_01_24814__li9505182131517">During the conversion, the configuration of the TimelineServer role will expire. In this case, you need to restart the instance whose configuration expires.</li></ul>
|
|
</div>
|
|
<div class="section" id="mrs_01_24814__section10398012430"><h4 class="sectiontitle">Procedure</h4><ol id="mrs_01_24814__ol1740815045313"><li id="mrs_01_24814__li558826173"><span>Log in to FusionInsight Manager and choose <strong id="mrs_01_24814__b11873185612336">Cluster</strong> > <strong id="mrs_01_24814__b74393003416">Services</strong> > <strong id="mrs_01_24814__b27599312344">Yarn</strong>. Click <strong id="mrs_01_24814__b1145511510341">Configurations</strong>.</span></li><li id="mrs_01_24814__li223325365514"><span>Change the value of <strong id="mrs_01_24814__b1187515563346">TLS_FLOAT_IP</strong> to an available floating IP address (the floating IP address and the service IP addresses of the two TimelineServer instances must be in the same network segment) and click <strong id="mrs_01_24814__b1454533203519">Save</strong> then <strong id="mrs_01_24814__b1953639123517">OK</strong>.</span></li><li id="mrs_01_24814__li963913117710"><span>Click the <strong id="mrs_01_24814__b168431114285925">Instance</strong> tab. Click <strong id="mrs_01_24814__b214017485685925">Add Instance</strong>, select a node to add a TimelineServer instance, and choose <strong id="mrs_01_24814__b61307771985925">Next</strong> > <strong id="mrs_01_24814__b67637427085925">Next</strong> > <strong id="mrs_01_24814__b174634398285925">Submit</strong>. The instance is added.</span></li><li id="mrs_01_24814__li060211141118"><span>On FusionInsight Manager, click <span><img id="mrs_01_24814__image91688177276" src="en-us_image_0000001533359808.jpg"></span> next to the cluster name, select <strong id="mrs_01_24814__b1933216426370">Restart Configuration-Expired Instances</strong>, and wait until the instance is restarted.</span></li><li id="mrs_01_24814__li13283154731"><span>Check the status of each instance after the restart. For example, the active/standby status and running status of the TimelineServer instances are normal.</span></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_0851.html">Using Yarn</a></div>
|
|
</div>
|
|
</div>
|
|
|