Could be too. I forgot to add to the list:
HBASE-2277 Update branch to hadoop 0.20.2 J-D On Mon, Apr 5, 2010 at 5:41 PM, Todd Lipcon <t...@cloudera.com> wrote: > +1, I think all of these are solid improvements to known bugs. Only > question: why not just make this 0.20.4, and then make the next one be > 0.20.5? > > -Todd > > On Mon, Apr 5, 2010 at 5:37 PM, Jean-Daniel Cryans <jdcry...@apache.org>wrote: > >> Hey devs, >> >> There are a good bunch of fixes in the branch that lots of people >> could have used recently. It's hard to tell exactly when 0.20.4 will >> be released but I think we need a bug fix release ASAP. >> >> I propose that we tag rev# 919707 (just before the backport of group >> commit) and apply a couple of the other biggest fixes that happened >> after that: >> >> HBASE-2174 Stop from resolving HRegionServer addresses to names using >> DNS on every heartbeat >> HBASE-2308 Fix the bin/rename_table.rb script, make it work again >> HBASE-2023 Client sync block can cause 1 thread of a multi-threaded >> client to block all others >> HBASE-2305 Client port for ZK has no default >> HBASE-2323 filter.RegexStringComparator does not work with certain bytes >> HBASE-2147 run zookeeper in the same jvm as master during non-distributed >> mode >> HBASE-2355 Unsynchronized logWriters map is mutated from several >> threads in HLog splitting >> HBASE-2358 Store doReconstructionLog will fail if oldlogfile.log is >> empty and won't load region >> HBASE-2365 Double-assignment around split >> HBASE-2087 The wait on compaction because "Too many store files" >> holds up all flushing >> HBASE-2252 Mapping a very big table kills region servers >> >> We could do without 2308,2305,2147 but the rest is pretty important. >> The work would be done at StumbleUpon to generate the RC. What do you >> guys think? >> >> J-D >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera >
