<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Moosefs on CineNeural</title>
    <link>https://blog.cineneural.com/tags/moosefs/</link>
    <description>Recent content in Moosefs on CineNeural</description>
    <image>
      <title>CineNeural</title>
      <url>https://blog.cineneural.com/images/main/logo-2.png</url>
      <link>https://blog.cineneural.com/images/main/logo-2.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>cineneural.com</copyright>
    <lastBuildDate>Wed, 23 Nov 2022 13:54:21 +0800</lastBuildDate>
    <atom:link href="https://blog.cineneural.com/tags/moosefs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Moosefs Master High Availability</title>
      <link>https://blog.cineneural.com/blog/2022-11/moosefs-master-high-availability/</link>
      <pubDate>Wed, 23 Nov 2022 13:54:21 +0800</pubDate>
      <guid>https://blog.cineneural.com/blog/2022-11/moosefs-master-high-availability/</guid>
      <description>&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://blog.cineneural.com/images/2022-11/MFS-HA.svg&#34;&gt;&lt;/p&gt;
&lt;p&gt;I designed a rudimentary k8s persistentvolumeclaims solution myself, using &lt;a href=&#34;https://moosefs.com&#34;&gt;Moosefs&lt;/a&gt; on the backend as a distributed data store. The principle is based on the kubernetes events mechanism, when a create pvc message is received, the backend control application will create the corresponding pv on moosefs and bind the corresponding pvc, in order to facilitate the application to move between nodes, I mount the moosefs file system to each worker node, here a problem arises: how to keep the moosefs master high availability!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
