{"action":"opened","issue":{"url":"https://api.github.com/repos/apache/trafficserver/issues/6237","repository_url":"https://api.github.com/repos/apache/trafficserver","labels_url":"https://api.github.com/repos/apache/trafficserver/issues/6237/labels{/name}","comments_url":"https://api.github.com/repos/apache/trafficserver/issues/6237/comments","events_url":"https://api.github.com/repos/apache/trafficserver/issues/6237/events","html_url":"https://github.com/apache/trafficserver/issues/6237","id":531569582,"node_id":"MDU6SXNzdWU1MzE1Njk1ODI=","number":6237,"title":"remap_stats: wrong stat id's getting assigned after hard traffic_server crash","user":{"login":"traeak","id":23385997,"node_id":"MDQ6VXNlcjIzMzg1OTk3","avatar_url":"https://avatars2.githubusercontent.com/u/23385997?v=4","gravatar_id":"","url":"https://api.github.com/users/traeak","html_url":"https://github.com/traeak","followers_url":"https://api.github.com/users/traeak/followers","following_url":"https://api.github.com/users/traeak/following{/other_user}","gists_url":"https://api.github.com/users/traeak/gists{/gist_id}","starred_url":"https://api.github.com/users/traeak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/traeak/subscriptions","organizations_url":"https://api.github.com/users/traeak/orgs","repos_url":"https://api.github.com/users/traeak/repos","events_url":"https://api.github.com/users/traeak/events{/privacy}","received_events_url":"https://api.github.com/users/traeak/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-12-02T22:06:12Z","updated_at":"2019-12-02T22:06:12Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Recreated with 0cf7e5953aec06d4dafb183861afe918763cbf33\r\n\r\nUsing the remap_stats plugin in production we have observed the remap_stats::stats_add() TSStatsCreate() getting the id from another stats.  This happens only after a hard ATS crash and restart by traffic_manager.  We've never seen an invalid id assigned, just an id from another stat.  This may result in a bytes transferred counter incrementing a status_5xx like so (from *traffic_ctl metric match remap_stats*)\r\n\r\n```\r\n...\r\n82704 plugin.remap_stats.foo1.status_2xx\r\n727229625 plugin.remap_stats.loopback.status_5xx\r\n```\r\n\r\nWe've found that making the remap_stats persistent (param '-p') seems to mitigate whatever race condition there is.\r\n"}}
{"actor":{"display_login":"traeak"}}