We also see a lot of "responseTooLarge for: multi". Not sure what this is...
On Tue, Jun 7, 2011 at 9:50 AM, Wayne <[email protected]> wrote: > We are seeing "responseTooLarge for: next..." errors in our region server > logs. If I understand correctly is this caused by opening a scanner and the > rows are too big to be returned? If the scan batch size is set to 1 this > tells me these are rows too big to actually read. Is this correct? Why would > this error occur? The size are listed as 120m+ when we see this error. > > We have been getting timeouts (60s) on our scans even with a scan batch > size of 1. I assume this may be part of the explanation why? What is causing > this and how do we get around it? > > Thanks. >
