1.6.1版本使用redis模式回滚成功但redis中存在SEATA_ROW_LOCK_jdbc不会自动删除

1.6.1版本使用redis存储模式回滚成功，seata和服务都没报错，都显示回滚成功，数据也没问题，但redis中会存在SEATA_ROW_LOCK_jdbc开头的key不会自动删除。改用mysl后，回滚后seata的四个表中均无脏数据，全部自动删除，为什么redis会存在这种问题呢？

No files, tests, or entry points are named. Reproduce a successful rollback on Seata 1.6.1 with Redis storage, inspect the remaining SEATA_ROW_LOCK_jdbc keys, and compare the result with MySQL storage; the issue is done when the cause of the leftover keys and the expected cleanup behavior are established.

Written by the indexing model from the issue text.