tree 55954f756bcf55166ed6cfa6a9b6a30bcf37d4a2
parent c32b52454ae5677bc61e15047d56ee3702b38300
author lipenghui <penghui@apache.org> 1631860502 +0800
committer GitHub <noreply@github.com> 1631860502 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhRDcWCRBK7hj4Ov3rIwAAniEIAHBSbeOfHoHdhjydL2i2rS4I
 UVvZcaZBLXX/LvADKZZ2OJdu9rZd8OYhFdBs2GVBkmvLb9dSldVdZ525bVTB1q5f
 p/DWXLCAx1T+HtnhlTvn9MfNFN1JB+dK1RjTgwKTLhTsu0aD1XHqz2jaCstB5gOo
 17tT9X91k1tWp/WfGp/M6WtgnwuOz6GKCYeLKXwyQT+9sDJwzlJTJ8jIJH1T+wUG
 zQrOgt8/dsXtg5rUJZIvHQMbmQ+saHJ44dlWXjTbGL2nkhVTZYnv8GfNgda8guMm
 YISjSSQe4RgscRiMv3FbfAFx2j49Yq7HBOlrzdJ9dnUGkBGmc7TqEMLCw6WTTQk=
 =GQw7
 -----END PGP SIGNATURE-----
 

Fix wrong key-hash selector used for new consumers after all the previous consumers disconnected (#12035)

We will encounter the issue after all the previous consumers disconnected and the new consumers connect
to the topic with different key_shared policy.

The root cause is we are using the previous dispatcher after the key_shared policy changed, so the fix
is to use a new dispatcher after a new consumer with a different key-shared policy