VerneMQ does not reconnect to mongoDB if Database is restarted

[KnolBee]

Environment

• VerneMQ Version: 1.1.0
• OS: Ubuntu 16.04
• Erlang/OTP version (if building from source):

Expected behavior

• Restart of MongoDB shouldn't force restart of VerneMQ

Actual behaviour

• If MongoDB is restarted, VerneMQ stops authenticating until restarted.

[ioolkos]

@KnolBee thanks for pointing that out. That's totally unfortunate.
@larshesel @dergraf Is there some trick to restart the connection pool? or should it work out of the box anyway?

[larshesel]

This looks like a bug - I'll investigate soon.

[larshesel]

I can confirm this - the child connections are restarted until the supervisor reaches its max restart intensity and shuts down taking vmq_diversity with it.

[KnolBee]

Thanks @larshesel are there plans to fix this? This is definitely a blocker for production use of MongoDB authentication module.

[larshesel]

It will be fixed but I can't give a time frame ATM.

[larshesel]

Btw. I forgot to answer if there was some workaround to this. I would expect - but haven't tested it - that if you restart the vmq_diversity plugin then the pools should get reinitialized. I'll try to spend some time on this issue today.

[larshesel]

Hi @KnolBee , I've a branch in #491 which should fix this issue. Could you test that out? Next I'd try to bring in an upgraded mongodb driver.

[larshesel]

Merged

[KnolBee]

Hi @larshesel Ok great, Will test over the weekend.