<div dir="ltr">Hi,<div>it's an understandable point of view.</div><div><br></div><div>My need is to be able to start/restart kamailio even if redis is just temporarily unavailable, and manage the "connection refused" errors accordingly. I have a failover strategy for those cases, but want to keep processing calls. When redis then returns available, kamailio will connect correctly. It's really an edge case, but I feel safer.<br></div><div><br></div><div>Configurations that depend more strongly on redis being available should not use this optional configuration item, keeping the current behaviour.</div><div><br></div><div>Cheers,</div><div>Giacomo</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 13 April 2015 at 16:49, Vicente Hernando <span dir="ltr"><<a href="mailto:vhernando@systemonenoc.com" target="_blank">vhernando@systemonenoc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello,<br>
<br>
I do not like the idea behind the patch. If redis database is
down, what is the point of launching kamailio anyway?<br>
If you need redis to run you should fix it, or not to use the
ndb_redis module if you want to run without redis.<br>
<br>
Any other opinions are welcome.<br>
<br>
Cheers,<br>
Vicente.<div><div class="h5"><br>
<br>
<br>
<br>
On 04/13/2015 04:24 PM, Giacomo Vacca wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div class="h5">
<hr>
<h4>You can view, comment on, or merge this pull request online
at:</h4>
<p> <a href="https://github.com/kamailio/kamailio/pull/121" target="_blank">https://github.com/kamailio/kamailio/pull/121</a></p>
<h4>Commit Summary</h4>
<ul>
<li>ndb_redis: optionally allow mod init with redis unavailable</li>
<li>ndb_redis: update doc with init_without_redis</li>
<li>ndb_redis: update README with init_without_redis</li>
</ul>
<h4>File Changes</h4>
<ul>
<li> <strong>M</strong> <a href="https://github.com/kamailio/kamailio/pull/121/files#diff-0" target="_blank">modules/ndb_redis/README</a>
(28) </li>
<li> <strong>M</strong> <a href="https://github.com/kamailio/kamailio/pull/121/files#diff-1" target="_blank">modules/ndb_redis/doc/ndb_redis_admin.xml</a>
(19) </li>
<li> <strong>M</strong> <a href="https://github.com/kamailio/kamailio/pull/121/files#diff-2" target="_blank">modules/ndb_redis/ndb_redis_mod.c</a>
(13) </li>
</ul>
<h4>Patch Links:</h4>
<ul>
<li><a href="https://github.com/kamailio/kamailio/pull/121.patch" target="_blank">https://github.com/kamailio/kamailio/pull/121.patch</a></li>
<li><a href="https://github.com/kamailio/kamailio/pull/121.diff" target="_blank">https://github.com/kamailio/kamailio/pull/121.diff</a></li>
</ul>
<p style="font-size:small;color:#666">—<br>
Reply to this email directly or <a href="https://github.com/kamailio/kamailio/pull/121" target="_blank">view it
on GitHub</a>.<img alt="" src="https://github.com/notifications/beacon/AF36ZZop9fhtMFD5OO34LcPnMaG9CuPkks5n-8kQgaJpZM4D_ciZ.gif" height="1" width="1"></p>
<div>
<div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
sr-dev mailing list
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br></div>