Re: setMaxResultSize on Gets
On Mon, Aug 22, 2016 at 3:02 PM, Bryan Beaudreaultwrote: > In HBase 1.2.x and higher you can call setMaxResultSize on a Scan to limit > the impact of scans that are too aggressive, by bailing out at a certain > size response. The client side will nicely splice together all of the > isPartial responses to create a full one as well, pushing the danger to the > client side where it belongs. > > However, there doesn't appear to be any way to do similar on Gets, despite > Gets being backed by Scans under the covers. I do notice > a setMaxResultsPerColumnFamily, but this seems much less straightforward > than setMaxResultSize. > > Was there a reason that Gets did not get the same treatment that Scans got? > We regularly see issues where someone has a large row and does a > too-aggressive Get against it. We're currently looking to build a wrapper > using setMaxResultsPerColumnFamily or adding support for setMaxResultSize > to Gets, but I want to make sure there wasn't a reason it was avoided in > the first place. > A simple case of Scan myopia/focus I'd say Bryan. Oversight. I don't see any reason why we shouldn't do Get in same way. In fact it came up recently in an internal conversation. The difficult part might the protocol going back and forth adding in an incremental. A Get is a Scan but only after it arrives at the server. I've not looked but hopefully it could be the same as Scan. St.Ack
Re: Row length is 0 at org.apache.hadoop.hbase.client.Mutation.checkRow(Mutation.java:503)
Thank you man, you are right, and i solve this problem with your information -- View this message in context: http://apache-hbase.679495.n3.nabble.com/Row-length-is-0-at-org-apache-hadoop-hbase-client-Mutation-checkRow-Mutation-java-503-tp4077663p4081995.html Sent from the HBase User mailing list archive at Nabble.com.
A quick survey from the Apache HBase project
The Apache HBase project would like just a moment of your time to complete a four question usage survey: https://www.surveymonkey.com/r/NJFKKGW All results will be completely anonymous, we have turned off all data collection options on SurveyMonkey except the tally of answers. This is a quick and easy opportunity to influence the project. Thanks in advance for your participation! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
setMaxResultSize on Gets
In HBase 1.2.x and higher you can call setMaxResultSize on a Scan to limit the impact of scans that are too aggressive, by bailing out at a certain size response. The client side will nicely splice together all of the isPartial responses to create a full one as well, pushing the danger to the client side where it belongs. However, there doesn't appear to be any way to do similar on Gets, despite Gets being backed by Scans under the covers. I do notice a setMaxResultsPerColumnFamily, but this seems much less straightforward than setMaxResultSize. Was there a reason that Gets did not get the same treatment that Scans got? We regularly see issues where someone has a large row and does a too-aggressive Get against it. We're currently looking to build a wrapper using setMaxResultsPerColumnFamily or adding support for setMaxResultSize to Gets, but I want to make sure there wasn't a reason it was avoided in the first place. Thanks!
Re: (BUG)ShortCircuitLocalReads Failed when enabled replication
Can anybody test it again,to verify whether there is a problem. Thanks! -- View this message in context: http://apache-hbase.679495.n3.nabble.com/BUG-ShortCircuitLocalReads-Failed-when-enabled-replication-tp4081733p4081968.html Sent from the HBase User mailing list archive at Nabble.com.