scanners this causes
a massive IO load on the name node of our cluster.
Would this be a valid use case for the snapshot scanner? Can we/do we already
have the capability to let the snapshot scanner only scan a given region rather
than the whole table?
Thanks,
Deepti Bhogle | Senior Software Engineer
We may not be able to upgrade to 5.4.8, since our 5.4.5 upgrade is pretty
recent. I will discuss the possibility if the patch doesn’t work for us.
Deepti Bhogle | Senior Software Engineer | Connexity, Inc.
Phone: 858.652.4318 | dbho...@connexity.com
On 1/8/16, 10:26 AM, "Matteo Ber
Yes I think its a similar issue. The JIRA mentions a patch created that should
have the fix for the TableSnapshotScanner, we will check if we can apply the
patch to our current version.
Thanks,
Deepti Bhogle | Senior Software Engineer | Connexity, Inc.
Phone: 858.652.4318 | dbho
We currently do exactly that. We create multiple instances of
TableSnapshotScanner each with a unique dir location against the same snapshot.
But doing so gives us the exception mentioned. Does that mean we can’t run
multiple instances at the same time?
Deepti Bhogle | Senior Software Engineer
