{"action":"opened","issue":{"url":"https://api.github.com/repos/c-rack/quantum-elixir/issues/311","repository_url":"https://api.github.com/repos/c-rack/quantum-elixir","labels_url":"https://api.github.com/repos/c-rack/quantum-elixir/issues/311/labels{/name}","comments_url":"https://api.github.com/repos/c-rack/quantum-elixir/issues/311/comments","events_url":"https://api.github.com/repos/c-rack/quantum-elixir/issues/311/events","html_url":"https://github.com/c-rack/quantum-elixir/issues/311","id":300488677,"number":311,"title":"Problem: Name conflict terminating TaskStagesSupervisor in cluster","user":{"login":"xinz","id":1047704,"avatar_url":"https://avatars0.githubusercontent.com/u/1047704?v=4","gravatar_id":"","url":"https://api.github.com/users/xinz","html_url":"https://github.com/xinz","followers_url":"https://api.github.com/users/xinz/followers","following_url":"https://api.github.com/users/xinz/following{/other_user}","gists_url":"https://api.github.com/users/xinz/gists{/gist_id}","starred_url":"https://api.github.com/users/xinz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xinz/subscriptions","organizations_url":"https://api.github.com/users/xinz/orgs","repos_url":"https://api.github.com/users/xinz/repos","events_url":"https://api.github.com/users/xinz/events{/privacy}","received_events_url":"https://api.github.com/users/xinz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-27T04:20:03Z","updated_at":"2018-02-27T04:20:03Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\n\r\nI'm using `libcluster` to maintain the cluster nodes, here is the error log when start more than two nodes.\r\n\r\n```\r\n2018-02-27 11:56:19.422 [info] global: Name conflict terminating {QuantumDemo.Scheduler.TaskStagesSupervisor, #PID<20556.214.0>}\r\n\r\n2018-02-27 11:56:19.441 [error] GenServer QuantumDemo.Scheduler.ExecutorSupervisor terminating\r\n** (stop) killed\r\nLast message: {:EXIT, #PID<0.214.0>, :killed}\r\nState: %ConsumerSupervisor{args: {QuantumDemo.Scheduler.ExecutionBroadcaster, QuantumDemo.Scheduler.Task.Supervisor, QuantumDemo.Scheduler.TaskRegistry}, children: %{}, max_restarts: 3, max_seconds: 5, mod: Quantum.ExecutorSupervisor, name: QuantumDemo.Scheduler.ExecutorSupervisor, producers: %{#Reference<0.3152433937.331874307.203647> => {{#PID<0.217.0>, #Reference<0.3152433937.331874307.203647>}, 0, 0, 25, 50}}, restarting: 0, restarts: [], strategy: :one_for_one, template: {Quantum.Executor, {Quantum.Executor, :start_link, [{QuantumDemo.Scheduler.Task.Supervisor, QuantumDemo.Scheduler.TaskRegistry}]}, :temporary, 5000, :worker, [Quantum.Executor]}}\r\n```\r\n\r\nReproduce steps:\r\n\r\n1. Here is a reproduce repo https://github.com/xinz/quantum_demo\r\n2. After the deps installed, start node ac1 as `$ iex --name ac1@127.0.0.1 -S mix`, and then start another node ac2 as `$ iex --name ac2@127.0.0.1 -S mix`, we will see the above error message.\r\n\r\nI also found the related discussion https://github.com/c-rack/quantum-elixir/issues/272, could you please advice any about this issue?\r\n\r\nThanks a lot!\r\n\r\n"}}
{"actor":{"display_login":"xinz"}}