[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openser-devel
Subject:    Re: [sr-dev] [kamailio/kamailio] DB_UNIXODBC always changes language and context (#1993)
From:       Tim Chubb <notifications () github ! com>
Date:       2019-06-26 14:25:50
Message-ID: kamailio/kamailio/issues/1993/505899274 () github ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Originally i had everything being backed by ODBC tables, but could never get the \
hangs to stop, usually presenting it self as an inability to auth registrations \
randomly.  I think i also stumbled upon some  hard coded MySQL syntax specific \
queries in various modules typically using the MySQL specific REPLACE (upsert) \
keyword.  Getting around the lack of USE keyword validity in SQL Azure was acheived \
like i said by specifying on the server login and user entities rather than in the \
connection string.

As a result of the random nature of the hangs we re-architected to using intermediate \
API for our dynamic data access and for infrequently changing data (dispatcher for \
example) generated textdb files, when a change is submitted through the back end.  At \
its simplest we just set a flag saying file has changed, and poll the api, if the \
flag is set local copy is overritten by the downloaded generated file, and the data \
gets reloaded via kamcmd.  Since having done that all our relational data stays in \
sql azure, but is never directly accessed by kamailio, and have not had a single hang \
like we were experiencing.  Like i said the odd thing was if i pointed the connection \
string to a local SQL server it would work perfectly, just undermined our long \
established SQL Azure consolidation project...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1993#issuecomment-505899274


[Attachment #5 (text/html)]

<p>Originally i had everything being backed by ODBC tables, but could never get the \
hangs to stop, usually presenting it self as an inability to auth registrations \
randomly.  I think i also stumbled upon some  hard coded MySQL syntax specific \
queries in various modules typically using the MySQL specific REPLACE (upsert) \
keyword.  Getting around the lack of USE keyword validity in SQL Azure was acheived \
like i said by specifying on the server login and user entities rather than in the \
connection string.</p> <p>As a result of the random nature of the hangs we \
re-architected to using intermediate API for our dynamic data access and for \
infrequently changing data (dispatcher for example) generated textdb files, when a \
change is submitted through the back end.  At its simplest we just set a flag saying \
file has changed, and poll the api, if the flag is set local copy is overritten by \
the downloaded generated file, and the data gets reloaded via kamcmd.  Since having \
done that all our relational data stays in sql azure, but is never directly accessed \
by kamailio, and have not had a single hang like we were experiencing.  Like i said \
the odd thing was if i pointed the connection string to a local SQL server it would \
work perfectly, just undermined our long established SQL Azure consolidation \
project...</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You \
are receiving this because you are subscribed to this thread.<br />Reply to this \
email directly, <a href="https://github.com/kamailio/kamailio/issues/1993?email_source \
=notifications&amp;email_token=ABO7UZMAIORWULZ6SRDXRTLP4N365A5CNFSM4H3LN6E2YY3PNVWWK3T \
UL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTWSCQ#issuecomment-505899274">view \
it on GitHub</a>, or <a \
href="https://github.com/notifications/unsubscribe-auth/ABO7UZIUSDO55DOZRES3CLDP4N365ANCNFSM4H3LN6EQ">mute \
the thread</a>.<img src="https://github.com/notifications/beacon/ABO7UZP6RLHEJ6XDMYLHI \
JDP4N365A5CNFSM4H3LN6E2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTWSCQ.gif" \
height="1" width="1" alt="" /></p> <script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/1993?email_source=notifications \
\u0026email_token=ABO7UZMAIORWULZ6SRDXRTLP4N365A5CNFSM4H3LN6E2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTWSCQ#issuecomment-505899274",
 "url": "https://github.com/kamailio/kamailio/issues/1993?email_source=notifications\u \
0026email_token=ABO7UZMAIORWULZ6SRDXRTLP4N365A5CNFSM4H3LN6E2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYTWSCQ#issuecomment-505899274",
 "name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>


[Attachment #6 (text/plain)]

_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev


[prev in list] [next in list] [prev in thread] [next in thread]