Re: Issues running Minicluster in o.a.a.start.Main

2013-10-09 Thread Keith Turner
I have "accumulo minicluster" working now. I changed the way MAC determines what classpath to use. I pushed a commit [1] to a branch on github[2] if you want to take a look. I am still experimenting with the change. I ran into some other bugs in master while working on this and fixed those.

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-09 Thread Corey Nolet
Looking at the commit history in master using gitk/gitx shows duplicated history. It looks like January through July 2013 occur at least twice in the commit history (with 2012 in between them). I'm suspecting this may have been why bisect wasn't working for me On Wed, Oct 9, 2013 at 1:25 PM, Kei

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-09 Thread Keith Turner
On Tue, Oct 8, 2013 at 9:45 PM, Corey Nolet wrote: > Keith, > > It appears that the proxy's useMini and the minicluster command broke > somewhere between > > 1edccf6b30541841bb08329317c6289aca8c8d73 > ACCUMULO-1707 applying Steve's patch > > and > > 98d7a9efc6d07e71d3803b3830bf9dc9ce8dec9d > ACCU

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-09 Thread Keith Turner
I am working on a fix for this. On Tue, Oct 8, 2013 at 10:18 PM, Corey Nolet wrote: > I had started my bisect at the first commit at which it was introduced, > though it looks like it still took me on a similar path as where it took > you- needless to say, after the 9 or so steps that it allowe

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Keith Turner
On Tue, Oct 8, 2013 at 10:18 PM, Corey Nolet wrote: > I had started my bisect at the first commit at which it was introduced, > though it looks like it still took me on a similar path as where it took > you- needless to say, after the 9 or so steps that it allowed me to take, > the minicuster com

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Corey Nolet
I had started my bisect at the first commit at which it was introduced, though it looks like it still took me on a similar path as where it took you- needless to say, after the 9 or so steps that it allowed me to take, the minicuster command was still broken. On Tue, Oct 8, 2013 at 10:12 PM, Keit

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Keith Turner
On Tue, Oct 8, 2013 at 10:06 PM, Corey Nolet wrote: > With risk of making this more complicated- I just noticed that the first > commit posted was still broken- though it didn't lock up like the version > currently in master, it appeared to run but threw the ClassNotFound > exception in the Main.

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Keith Turner
On Tue, Oct 8, 2013 at 9:45 PM, Corey Nolet wrote: > Keith, > > It appears that the proxy's useMini and the minicluster command broke > somewhere between > > 1edccf6b30541841bb08329317c6289aca8c8d73 > ACCUMULO-1707 applying Steve's patch > > and > > 98d7a9efc6d07e71d3803b3830bf9dc9ce8dec9d > ACCU

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Corey Nolet
With risk of making this more complicated- I just noticed that the first commit posted was still broken- though it didn't lock up like the version currently in master, it appeared to run but threw the ClassNotFound exception in the Main.err log. I'm still poking at this as well. On Tue, Oct 8, 2

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Keith Turner
I tried using git bisect (for the second time) to tackle this issue and ran into an interesting issue. git bisect took me from master to 1.4. This was unexpected at first, but I understand why git is doing this. I would like to avoid this and only consider commits in master. $ grep -A 5 org.ap

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-08 Thread Corey Nolet
Keith, It appears that the proxy's useMini and the minicluster command broke somewhere between 1edccf6b30541841bb08329317c6289aca8c8d73 ACCUMULO-1707 applying Steve's patch and 98d7a9efc6d07e71d3803b3830bf9dc9ce8dec9d ACCUMULO-1558 made import table fail when files do not exist There was some

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-07 Thread Corey Nolet
Keith, You are right- I mistyped. I meant Main.err not Master.err. I just verified this feature worked during the time of this commit: 6965a8aaa2f53ec796a3487c1639affe0dfc6bfa. On Mon, Oct 7, 2013 at 11:39 PM, Keith Turner wrote: > I just tried running "accumulo miniscluster" and saw the same

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-07 Thread Keith Turner
I just tried running "accumulo miniscluster" and saw the same thing. But in Main.err, not Master.err are you sure you saw this in Master.err? Has this ever worked? By default the accumulo scripts construct a very minimal classpath w/ accumulo-start.jar, log4j-1.2.15.jar, and the conf dir. If

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-07 Thread Corey Nolet
The MiniAccumuloRunner class that's wired up to o.o.a.start.Main. I was specifically wondering if anyone else is experiencing issues running 'accumulo minicluster' as both the proxy with useMini=true and the minicluster command seem broken for me. I'm building from remote HEAD in master. On Oct 6,

Re: Issues running Minicluster in o.a.a.start.Main

2013-10-06 Thread John Vines
How are you running minicluster? On Sun, Oct 6, 2013 at 8:36 AM, Corey Nolet wrote: > I'm having issues running the minicluster both in the 'accumulo proxy -p > proxy.properties' and via 'accumulo minicluster'. It looks like the > Zookeeper process is not starting and the MAC is going into an i

Issues running Minicluster in o.a.a.start.Main

2013-10-06 Thread Corey Nolet
I'm having issues running the minicluster both in the 'accumulo proxy -p proxy.properties' and via 'accumulo minicluster'. It looks like the Zookeeper process is not starting and the MAC is going into an infinite loop waiting for it to start. I checked the Master.err logs for the minicluster comma