Did you see in the hadoop issue where Raghu talks of grizzly mayhaps been better suited because it has more accomodating community and its written more to the datanode level?
Would suggest keeping Raghu in the loop. Perhaps by posting intermediary patches up against the hadoop issue. I can help pre-review patches and with testing. You are a good man Andrew Purtell. St.Ack On Fri, Feb 6, 2009 at 11:00 AM, Andrew Purtell <[email protected]> wrote: > So it looks like a complete rewrite of the datanode network I/O > in the async model is necessary. I don't want to invest the time > if in the end it isn't enough to significantly affect HBase > stability in a positive way. > > Blocking in disk I/O will be out of scope. > > - Andy > > > > From: Andrew Purtell > > > > I have started work on this. The plan is to use selectable > > channels (set to blocking mode), a work queue, and a pool of > > worker threads to handle xceiver connections. > [...] > > However, it may be necessary to go fully async > [...] > > > > >
