What would you need from us to test this on MapR? We can certainly spin you up a small cluster running MapR (2.1 or 3.0?). Would you then want to install Accumulo 1.5 and run the agitator test?
Keys ________________________________ Keys Botzum Senior Principal Technologist kbot...@maprtech.com 443-718-0098 MapR Technologies http://www.mapr.com On May 22, 2013, at 2:03 PM, John Vines wrote: > I'm just operating in the sandbox VM that MapR put out, not a cluster. I was > more concerned about general log writing/recovery. I'm wondering if MapR > folks could help with this test. > > > On Wed, May 22, 2013 at 1:40 PM, Eric Newton <eric.new...@gmail.com> wrote: > Can you verify that it works well in the presence of the agitator? That bit > of code is supposed to fence off a tablet server from its own logs after the > master determines that it is supposed to be dead. > > -Eric > > > > On Wed, May 22, 2013 at 1:27 PM, John Vines <vi...@apache.org> wrote: > And it works like a charm. Thanks Eric > > > On Tue, May 21, 2013 at 7:01 PM, John Vines <vi...@apache.org> wrote: > > > Sigh, I guess I could do that. I was rushing out the door, but I'll try > > that. > > > > Sent from my phone, please pardon the typos and brevity. > > Or you could configure the MapR log closer. > > > > > > > > On Tue, May 21, 2013 at 6:36 PM, John Vines <vi...@apache.org> wrote: > > > > > So I finally got around to testing MapR (well, finally got it running). > > > Gave RC4 a test run and, after seeing the stack trace, not surprised it > > > broke in HadoopLogCloser.close(). IllegalStateException gest thrown from > > > line 54 due to the filesystem being of type com.mapr.fs.MapRFileSystem. > > At > > > this point, I think this should be considered an acceptable break and > > > something we shoudl try to resolve first thing for 1.5.1. Thoughts? > > > > > > >
