The calculation of cardinality estimation is wrong in some cases

[Reminiscent]

Bug Report

Please answer these questions before submitting your issue. Thanks!

We shouldn't scale the totalCount here, we only scale the expBackoffCnt here.

You can reproduce it through
create tablet t(id int, a int, b int, primary key(a, b) nonclustered);
select * from t where id in (..); // Here the number of in expression should be as much as possible.

And the modifyCount != 0.

You can run the above SQL and check the estimate row count of the dataSource operator which use the index.