Hi JD,
I tried without success to hack our test architecture to evaluate the
effect of those configs. I stopped to avoid diverging to a kind of
'hbase performance testing'.
Definitely good to note that hbase.client.pause and
hbase.master.event.waiting.time can be tuned for tests speed.
Thx.
On 29/08/11 11:08, Jean-Daniel Cryans wrote:
(cleaning up my unread emails hehe)
We are using 0.90.x. Which exact timing param can we set? (I'm not sure
which one looking http://hbase.apache.org/book/config.files.html#hbase.site)
We set configuration via htu.getConfiguration().set... and not via
hbase-default.xml. Is it OK to do like that?
As long as the minicluster isn't started when you do those changes
it's ok, else it's too late.
You could set hbase.client.pause to something smaller than 1000, this
way the client would be more aggressive.
It seems a smaller value of hbase.master.event.waiting.time would also
make table changes snappier, the HBase unit tests use a value of 50.
J-D
--
Eric
http://about.echarles.net
