In our system, the RowKey of Hbase is written in binary, so the regular expression based on RowKey is useless, so a custom comparator is used to match the content of the row key at the specified location. There is no problem in the development and testing stages, and in the production environment, it always prompts an error that the class cannot be found after running. I have carefully confirmed that the jar package I typed is indeed placed in the lib directory of Hbase. Why is this error reported?
restart the cluster, invalid
Deleting the jar package is invalid, and re-adding it is invalid
Is it really hell?
Suddenly I found a problem. In the production environment, the account that started Hbase is the hadoop account, and the root account is used to upload files. Is it possible that the hadoop account cannot find the jar package passed in by the root account?
So execute chown, chgrp and then restart the cluster, the problem is solved.