Description
Noticed this issue in our internal test runs. It shows up when the test is run with replicas turned on. After the bulk load is complete, the test tries to modify the table with an intention of having the replicas load the new region files. But due to a bug in the way the test was waiting for the modifyTable operation to complete, it would not actually wait. Sometimes a replica wouldn't have loaded the new files yet and it might happen that the 'check' step of the test would go to that replica asking for data. It would give empty results back, and the test would fail.