https://osmocom.org/https://osmocom.org/favicon.ico?16647414092022-05-15T14:20:15ZOpen Source Mobile CommunicationsOsmoMSC - Bug #5564: blocking database I/O by SMS databasehttps://osmocom.org/issues/5564?journal_id=240902022-05-15T14:20:15Zlaforge
<ul></ul><p>so the point of all of this is to try to have a minimal effort + lowest possible risk work-around for the problem of blocking database I/O. This doesn't mean that our long-term strategy still is to have a proper SMSC outside of osmo-msc.</p> OsmoMSC - Bug #5564: blocking database I/O by SMS databasehttps://osmocom.org/issues/5564?journal_id=240922022-05-15T14:21:13Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-7 priority-3 priority-high3" href="/issues/5563">Bug #5563</a>: OsmoMSC sometimes stalls for dozens of seconds in a production deployment</i> added</li></ul> OsmoMSC - Bug #5564: blocking database I/O by SMS databasehttps://osmocom.org/issues/5564?journal_id=240962022-05-16T10:07:09Zlaforge
<ul></ul><p>I've spent most parts of yesterday working on related changes. For most parts it looks fine, but one conceptual problem is the fact that every <em>gsm_sms_pending</em> points to a <em>vlr_subscr</em> and holds a related reference (use count). Given that the allocation of <em>gsm_sms_pending</em> is now happening in the new SMS thread, we would need thread-safe vlr_subscr look-up and use count get/put. The use count is from libosmocore, and rather complex, making all of that thread-safe is out of the question.</p>
<p>So my proposed approach now is to just work with MSISDNs in the sms_queue and not with pointes to <em>vlr_subscr</em>. Only once the SMS queue pushes a to-be-delivered SMS to the main thread, the main thread will look up the <em>vlr_subscr</em>.</p> OsmoMSC - Bug #5564: blocking database I/O by SMS databasehttps://osmocom.org/issues/5564?journal_id=241072022-05-16T20:20:55Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Stalled</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>20</i></li></ul> OsmoMSC - Bug #5564: blocking database I/O by SMS databasehttps://osmocom.org/issues/5564?journal_id=241092022-05-17T09:25:08Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/5566">Feature #5566</a>: avoid using synchronous = FULL</i> added</li></ul> OsmoMSC - Bug #5564: blocking database I/O by SMS databasehttps://osmocom.org/issues/5564?journal_id=241152022-05-17T09:43:39Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/3587">Feature #3587</a>: Possibility to route SMS messages over GSUP</i> added</li></ul>