Earlier quoted context omitted.
And unfortunately the kind of thing that compliance flags as a big no-no once you've got any kind of filing or privacy requirements.
This sort of thing doesn’t have to be a compliance breach, but you will likely need some way of ensuring there’s a second person in the loop, typically that would take the form of having someone in a separate production infrastructure team actually driving a while you talk them through what needs to happen.
We used Elixir's Observer to hunt down bottlenecks
41–43 of 43 posts
You also need a way of recording what changed. when committing to git it's easy, but live eval-ing into prod sounds harder.
Re: We used Elixir's Observer to hunt down bottlenecks
#42Re: We used Elixir's Observer to hunt down bottlenecks
#43Earlier quoted context omitted.
For us we have our app deployed to $N containers with a load balancer in front (pretty standard stuff I think?) In Erlang/Elixir you can actually override how instances of the BEAM find each other (instead of the standard EPMD daemon), so we have a module that does some DNS queries, finds the IPs of the other containers and says “hi, here’s your cluster, discovery done.” (Your setup may preclude all that, I know this…
Can you speak more to how you bypass EPMD and send the IPs of the containers to each other? That would be great for a problem we’re seeing where I work
Other replies are a bit outdated. It got a lot easier in OTP-23 to go without EPMD, https://blog.erlware.org/epmdlessless/ -- if you run with the same port. If not using the same port across nodes then you may want to look at epmdless https://github.com/tsloughter/epmdless