Restart RAM node without disc node in RabbitMQ about discussions

[michaelklishin]

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).

We get at least a dozen of questions through various venues every single day, often light on details.
At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.

Please post this to rabbitmq-users.

Thank you.

[michaelklishin]

I haven't tried it in years but such orphan RAM node would be able to start and have nowhere to sync tables from. Would you consider this a successful outcome or a safe operational scenario? I don't think so.

RAM nodes are not necessary for 99% of use cases and with a future schema data store in 4.0 or so will go away completely. So don't build your system around them.

[michaelklishin]

I think one change that affects this (multiple years old) doc section is the introduction of sync operation retries so while this is a guess (no logs from any nodes were provided), it would try N times periodically before giving up entirely.

[yaboong]

Thank you for letting me know that there is a Q&A group and sorry for posting a question here.

I didn't say that it was a safe operation scenario. I wanted to check if the document is correct.

When posting the same question to Google Groups, I'll also attach the logs.