Closed mkacper closed 7 years ago
@mkacper I've conected two nodes together with net_kernel:connect('a@127.0.0.1').
(and connect_node
) but erlangpl shows warrning in console:
=WARNING REPORT==== 21-Jun-2017::14:54:47 ===
global: 'erlangpl@127.0.0.1' failed to connect to 'a@127.0.0.1'
Why can be that? Am I doing something wrong?
EDIT: They are perfectly connected within /traffic
view.
It's not related to this PR but previously we were displaying erlangpl
node only in development mode but after release it wasn't part of the cluster. Did something changed in this matter?
@Baransu This warning is normal :) I haven't figured out yet why it is showed. What does the /ets
view show in your browser? I've followed the steps you described and ets cluster view seems to work fine.
Here is the proper view:
When it comes to displaying erlangpl
node in the cluster view in /traffic
section I have not changed a way of creating Vizceral map for \traffic
view. I've made a release from master branch and erlangpl
node is also displayed in /traffic
view. Asking your question - I haven't got a clue if somethig changed in this matter or not.
Thanks for your engagement! :)
EDIT: Something is wrong with ets cluster view when erlangpl
is started from script. I will try to fix it.
I have 3 nodes in cluster. Every one connected with net_kernel:connect(node).
/ets
view/traffic
viewThanks for point the issue :) As I said in the previous comment something goes wrong when erlangpl is started from erlangpl
script. I am working on it right now.
Sorry, I didn't saw your edit.
Also, did you managed to fix with switching between etc
and traffic
view?
@Baransu
did you managed to fix with switching between etc and traffic view?
Yes, I did. It seems to work nice :)
Please try the \ets
view now. Does it work correctly?
This PR introduces ETS cluster view. It appears as a new tab in the web UI. The view shows all nodes in the cluster with basic infromation about ETS tables on a particular node.