Hello, we have this one table what about 12 regions, that is super hot
with writes, for some reason most of the regions were assigned to a
single server, which cause it to flush and compact every 10 minutes,
causing suboptimal performance.  We do use random row_keys, so I don't
see how sorted ROWs can land on single region anyway, the issue was
that each region was assigned to the same region server, is there a
way to mitigate the issue?  I closed closing the regions manually, but
they went right back to the same server, finally I shutdown RS
process, and that table's regions went in random places around the
cluster, but still its puzzling, anyone had issues like that?

-Jack

Reply via email to