https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2019-03-20T06:29:17ZCeph CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1323492019-03-20T06:29:17Zhuanwen ren
<ul></ul><p>Cause:<br />If you run MDSDaemon::init(), an exception occurs that causes MDSDaemon::suicide()--->Beacon::shutdown()--->sender.join();<br />this problem occurs because sender is just Default-constructed is in Beacon.h(std::thread sender;), there is no call<br />to Beacon::init() to construct the sender, so the sender has no "joinable"</p>
<p>fix: <a class="external" href="https://github.com/ceph/ceph/pull/27063">https://github.com/ceph/ceph/pull/27063</a></p> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1323922019-03-20T21:24:57ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fix Under Review</i></li><li><strong>Assignee</strong> set to <i>huanwen ren</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>v15.0.0</i></li><li><strong>Start date</strong> deleted (<del><i>03/20/2019</i></del>)</li><li><strong>Source</strong> set to <i>Community (dev)</i></li><li><strong>Backport</strong> set to <i>nautilus,mimic,luminous</i></li><li><strong>Pull request ID</strong> set to <i>27063</i></li></ul> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1327442019-03-26T00:49:49Zhuanwen ren
<ul></ul><p>hi Patrick @Patrick Donnelly<br />Can you pull me into the development of the tracker? I can't modify most of the states in this issue.</p> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1330782019-03-28T16:46:36ZPatrick Donnellypdonnell@redhat.com
<ul></ul><p>huanwen ren wrote:</p>
<blockquote>
<p>hi Patrick @Patrick Donnelly<br />Can you pull me into the development of the tracker? I can't modify most of the states in this issue.</p>
</blockquote>
<p>I've added you to the ceph developers group.</p> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1333602019-04-01T21:46:40ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Pending Backport</i></li></ul> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1340652019-04-10T21:06:40ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/39213">Backport #39213</a>: luminous: mds: there is an assertion when calling Beacon::shutdown()</i> added</li></ul> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1340672019-04-10T21:06:47ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/39214">Backport #39214</a>: nautilus: mds: there is an assertion when calling Beacon::shutdown()</i> added</li></ul> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1340692019-04-10T21:06:54ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/39215">Backport #39215</a>: mimic: mds: there is an assertion when calling Beacon::shutdown()</i> added</li></ul> CephFS - Bug #38822: mds: there is an assertion when calling Beacon::shutdown()https://tracker.ceph.com/issues/38822?journal_id=1489842019-10-18T11:39:56ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul><p>While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".</p>