{"action":"opened","issue":{"url":"https://api.github.com/repos/grobian/carbon-c-relay/issues/204","repository_url":"https://api.github.com/repos/grobian/carbon-c-relay","labels_url":"https://api.github.com/repos/grobian/carbon-c-relay/issues/204/labels{/name}","comments_url":"https://api.github.com/repos/grobian/carbon-c-relay/issues/204/comments","events_url":"https://api.github.com/repos/grobian/carbon-c-relay/issues/204/events","html_url":"https://github.com/grobian/carbon-c-relay/issues/204","id":166033709,"number":204,"title":"relay is sending data randomly while kill -HUP happens","user":{"login":"toni-moreno","id":5883405,"avatar_url":"https://avatars.githubusercontent.com/u/5883405?v=3","gravatar_id":"","url":"https://api.github.com/users/toni-moreno","html_url":"https://github.com/toni-moreno","followers_url":"https://api.github.com/users/toni-moreno/followers","following_url":"https://api.github.com/users/toni-moreno/following{/other_user}","gists_url":"https://api.github.com/users/toni-moreno/gists{/gist_id}","starred_url":"https://api.github.com/users/toni-moreno/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toni-moreno/subscriptions","organizations_url":"https://api.github.com/users/toni-moreno/orgs","repos_url":"https://api.github.com/users/toni-moreno/repos","events_url":"https://api.github.com/users/toni-moreno/events{/privacy}","received_events_url":"https://api.github.com/users/toni-moreno/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-18T07:21:10Z","updated_at":"2016-07-18T07:21:10Z","closed_at":null,"body":"Hi @grobian , I've updated to carbon-c-relay v2.1 (b8e663), last week, and I 've found a unpleasant surprise when I have added a new match line and sent kill -HUP to the process.\r\n\r\nWe are currently processing 940K input metrics  with 425 matching rules over 5 clusters,  all matching  rules follows the same format.\r\n\r\n````\r\nmatch ^m0001\\. send to cluster01 stop ;\r\nmatch ^m0002\\. send to cluster01 stop ;\r\nmatch ^m0003\\. send to cluster02 stop ;\r\nmatch ^m0004\\. send to cluster03 stop ;\r\nmatch ^m0005\\. send to cluster03 stop ;\r\nmatch ^m0006\\. send to cluster05 stop ;\r\n..\r\n..\r\nmatch ^m0425\\. send to cluster02 stop ;\r\n````\r\n\r\nAnd all cluster are forward clusters like that\r\n\r\n````\r\ncluster  cluster01\r\nforward\r\nmycluster01.mydomain.es:2003\r\n;\r\n````\r\n\r\nAfter my kill -HUP <PID> , and only during one little moment ( in the exact second on witch I did the -HUP signal) carbon-c-relay sended randomly .\r\n\r\nBy example:\r\n\r\nOn cluster04 we have received metrics from 10 match rules configured to send to cluster03, ( no all metrics only a 886 metrics , and only for this moment).\r\nOn cluster03 we have received metrics from 3 match rules configured to sent to cluster04 (191 metrics)\r\nOn cluster05 we have received metrics from 7 match rules configured to send to cluster02 (823 metrics) \r\n\r\nalthough very few metrics erroneously sent. There is enough to avoid kill -HUP in the future. And I will need this feature to allow dinamic configuration for new systems.\r\n\r\nThank you very much for your patience."}}
{"actor":{"display_login":"toni-moreno"}}