{"action":"created","issue":{"url":"https://api.github.com/repos/dpkp/kafka-python/issues/571","repository_url":"https://api.github.com/repos/dpkp/kafka-python","labels_url":"https://api.github.com/repos/dpkp/kafka-python/issues/571/labels{/name}","comments_url":"https://api.github.com/repos/dpkp/kafka-python/issues/571/comments","events_url":"https://api.github.com/repos/dpkp/kafka-python/issues/571/events","html_url":"https://github.com/dpkp/kafka-python/issues/571","id":137204852,"number":571,"title":"OffsetCommit failed for group XXX due to group error","user":{"login":"abc100m","id":4769764,"avatar_url":"https://avatars.githubusercontent.com/u/4769764?v=3","gravatar_id":"","url":"https://api.github.com/users/abc100m","html_url":"https://github.com/abc100m","followers_url":"https://api.github.com/users/abc100m/followers","following_url":"https://api.github.com/users/abc100m/following{/other_user}","gists_url":"https://api.github.com/users/abc100m/gists{/gist_id}","starred_url":"https://api.github.com/users/abc100m/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abc100m/subscriptions","organizations_url":"https://api.github.com/users/abc100m/orgs","repos_url":"https://api.github.com/users/abc100m/repos","events_url":"https://api.github.com/users/abc100m/events{/privacy}","received_events_url":"https://api.github.com/users/abc100m/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":26,"created_at":"2016-02-29T09:55:58Z","updated_at":"2016-03-14T06:10:49Z","closed_at":"2016-03-14T06:10:49Z","body":"while running producer send test with key, the consumer  output some error message:\r\n\r\n```python\r\n[2016-02-29 17:20:56,243] [ERROR] [Thread-2] OffsetCommit failed for group XXX due to group error (IllegalGenerationError - 22 - Returned from group membership requests (such as heartbeats) when the generation id provided in the request is not the current generation.), will rejoin\r\n[2016-02-29 17:20:56,787] [ERROR] [Thread-2] OffsetCommit failed for group XXX due to group error (IllegalGenerationError - 22 - Returned from group membership requests (such as heartbeats) when the generation id provided in the request is not the current generation.), will rejoin\r\n```\r\n\r\nthe consumer can still work\r\n\r\nI mentioned there is a similar issue #498, and it's fixed.  after upgraded from 1.0 to 1.01 and also to 1.02-dev,  my test script still output the error message.\r\n\r\nso, what's this message mean?  does it make some wrong?\r\n"},"comment":{"url":"https://api.github.com/repos/dpkp/kafka-python/issues/comments/196161712","html_url":"https://github.com/dpkp/kafka-python/issues/571#issuecomment-196161712","issue_url":"https://api.github.com/repos/dpkp/kafka-python/issues/571","id":196161712,"user":{"login":"dpkp","id":843444,"avatar_url":"https://avatars.githubusercontent.com/u/843444?v=3","gravatar_id":"","url":"https://api.github.com/users/dpkp","html_url":"https://github.com/dpkp","followers_url":"https://api.github.com/users/dpkp/followers","following_url":"https://api.github.com/users/dpkp/following{/other_user}","gists_url":"https://api.github.com/users/dpkp/gists{/gist_id}","starred_url":"https://api.github.com/users/dpkp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dpkp/subscriptions","organizations_url":"https://api.github.com/users/dpkp/orgs","repos_url":"https://api.github.com/users/dpkp/repos","events_url":"https://api.github.com/users/dpkp/events{/privacy}","received_events_url":"https://api.github.com/users/dpkp/received_events","type":"User","site_admin":false},"created_at":"2016-03-14T06:10:49Z","updated_at":"2016-03-14T06:10:49Z","body":"Logs are as expected, and the warnings you see there can be ignored for now.\r\n\r\nThe \"coordinator_unknown\" is a bit confusing and I have a patch in the works to improve it. As it is now, \"unknown\" also includes \"not ready\", which means it can be treated as unknown even when we are actually connected if it is not available for additional traffic. Currently that happens when we need to do a metadata refresh (treating metadata refreshes as top priority) or when the number of pipelined requests to the node is maxed out (see max_in_flight_requests_per_connection)."}}