When running the MapReduceExample (with no changes) I see the
following message and the Usage message:

  Was passed main parameter 'miniInstance' but no main parameter was defined

What other parameters need to be provided? I searched all files but do
not see any documentation for this program.

Should probably have documentation and a working example prior to 1.5.0. Is
there already a ticket for it?
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Fri, Feb 8, 2013 at 10:19 PM, David Medinets <[EMAIL PROTECTED]>wrote:

> When running the MapReduceExample (with no changes) I see the
> following message and the Usage message:
>
>   Was passed main parameter 'miniInstance' but no main parameter was
> defined
>
> What other parameters need to be provided? I searched all files but do
> not see any documentation for this program.
>

https://issues.apache.org/jira/browse/ACCUMULO-1058

On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]> wrote:
> Should probably have documentation and a working example prior to 1.5.0. Is there already a ticket for it?

I wonder if it is just because you're starting and stopping so quickly. I
know the Tserver processes take a second to come up, perhaps put a sleep in
for a few seconds and see if that works.
On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <[EMAIL PROTECTED]>wrote:

> https://issues.apache.org/jira/browse/ACCUMULO-1058
>
> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]> wrote:
> > Should probably have documentation and a working example prior to 1.5.0.
> Is there already a ticket for it?
>

Adding a Thread.sleep(1) after the start() method does seem to
consistently resolve the 'Stream Closed' issue.

      MiniAccumuloCluster la = new MiniAccumuloCluster(tmpDir, "pass1234");
      la.start();
      Thread.sleep(1);

Which raises a question. Should the start method wait for the
processes to start before returning? Any reason I shouldn't create a
jira ticket for this?

On Sat, Feb 9, 2013 at 8:45 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:
> I wonder if it is just because you're starting and stopping so quickly. I
> know the Tserver processes take a second to come up, perhaps put a sleep in
> for a few seconds and see if that works.
>
>
> On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <[EMAIL PROTECTED]>wrote:
>
>> https://issues.apache.org/jira/browse/ACCUMULO-1058
>>
>> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]> wrote:
>> > Should probably have documentation and a working example prior to 1.5.0.
>> Is there already a ticket for it?
>>

I don't think so, all of our client processes are designed to wait a bit
for the server to come up, and this process a similar behavior as our
start-all script.

Sent from my phone, please pardon the typos and brevity.
On Feb 10, 2013 10:59 PM, "David Medinets" <[EMAIL PROTECTED]> wrote:

> Adding a Thread.sleep(1) after the start() method does seem to
> consistently resolve the 'Stream Closed' issue.
>
>       MiniAccumuloCluster la = new MiniAccumuloCluster(tmpDir, "pass1234");
>       la.start();
>       Thread.sleep(1);
>
> Which raises a question. Should the start method wait for the
> processes to start before returning? Any reason I shouldn't create a
> jira ticket for this?
>
> On Sat, Feb 9, 2013 at 8:45 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:
> > I wonder if it is just because you're starting and stopping so quickly. I
> > know the Tserver processes take a second to come up, perhaps put a sleep
> in
> > for a few seconds and see if that works.
> >
> >
> > On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <[EMAIL PROTECTED]
> >wrote:
> >
> >> https://issues.apache.org/jira/browse/ACCUMULO-1058
> >>
> >> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]>
> wrote:
> >> > Should probably have documentation and a working example prior to
> 1.5.0.
> >> Is there already a ticket for it?
> >>
>

But if people start using the MiniAccumuloCluster without knowing
their client processing need to wait? What's the harm in letting
start() do the waiting? Wouldn't that ensure a minimum wait time and
consistent behavior?

On Sun, Feb 10, 2013 at 11:23 PM, John Vines <[EMAIL PROTECTED]> wrote:
> I don't think so, all of our client processes are designed to wait a bit
> for the server to come up, and this process a similar behavior as our
> start-all script.
>
> Sent from my phone, please pardon the typos and brevity.
> On Feb 10, 2013 10:59 PM, "David Medinets" <[EMAIL PROTECTED]> wrote:
>
>> Adding a Thread.sleep(1) after the start() method does seem to
>> consistently resolve the 'Stream Closed' issue.
>>
>>       MiniAccumuloCluster la = new MiniAccumuloCluster(tmpDir, "pass1234");
>>       la.start();
>>       Thread.sleep(1);
>>
>> Which raises a question. Should the start method wait for the
>> processes to start before returning? Any reason I shouldn't create a
>> jira ticket for this?
>>
>> On Sat, Feb 9, 2013 at 8:45 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:
>> > I wonder if it is just because you're starting and stopping so quickly. I
>> > know the Tserver processes take a second to come up, perhaps put a sleep
>> in
>> > for a few seconds and see if that works.
>> >
>> >
>> > On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <[EMAIL PROTECTED]
>> >wrote:
>> >
>> >> https://issues.apache.org/jira/browse/ACCUMULO-1058
>> >>
>> >> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]>
>> wrote:
>> >> > Should probably have documentation and a working example prior to
>> 1.5.0.
>> >> Is there already a ticket for it?
>> >>
>>

Because emulating the same behavior as start-all allows us to test the
client wait behavior. I would rather see the stop behavior changed to be
more like stop-all, in that it waits for it to be fully up before shutting
down.

Sent from my phone, please pardon the typos and brevity.
On Feb 10, 2013 11:28 PM, "David Medinets" <[EMAIL PROTECTED]> wrote:

> But if people start using the MiniAccumuloCluster without knowing
> their client processing need to wait? What's the harm in letting
> start() do the waiting? Wouldn't that ensure a minimum wait time and
> consistent behavior?
>
> On Sun, Feb 10, 2013 at 11:23 PM, John Vines <[EMAIL PROTECTED]> wrote:
> > I don't think so, all of our client processes are designed to wait a bit
> > for the server to come up, and this process a similar behavior as our
> > start-all script.
> >
> > Sent from my phone, please pardon the typos and brevity.
> > On Feb 10, 2013 10:59 PM, "David Medinets" <[EMAIL PROTECTED]>
> wrote:
> >
> >> Adding a Thread.sleep(1) after the start() method does seem to
> >> consistently resolve the 'Stream Closed' issue.
> >>
> >>       MiniAccumuloCluster la = new MiniAccumuloCluster(tmpDir,
> "pass1234");
> >>       la.start();
> >>       Thread.sleep(1);
> >>
> >> Which raises a question. Should the start method wait for the
> >> processes to start before returning? Any reason I shouldn't create a
> >> jira ticket for this?
> >>
> >> On Sat, Feb 9, 2013 at 8:45 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:
> >> > I wonder if it is just because you're starting and stopping so
> quickly. I
> >> > know the Tserver processes take a second to come up, perhaps put a
> sleep
> >> in
> >> > for a few seconds and see if that works.
> >> >
> >> >
> >> > On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <
> [EMAIL PROTECTED]
> >> >wrote:
> >> >
> >> >> https://issues.apache.org/jira/browse/ACCUMULO-1058
> >> >>
> >> >> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]>
> >> wrote:
> >> >> > Should probably have documentation and a working example prior to
> >> 1.5.0.
> >> >> Is there already a ticket for it?
> >> >>
> >>
>

I'd have to agree with you, David. I like MiniAccumuloCluster and think
there is great worth to be had from it. We should do the most we can to
make it easy to use.

I will say that I imagine it to be difficult to pinpoint exactly when
Accumulo is "up". If there isn't a good way to avoid your exception by
blocking internally, some documentation/warning is a good idea.

On Sunday, February 10, 2013, David Medinets <[EMAIL PROTECTED]>
wrote:
> But if people start using the MiniAccumuloCluster without knowing
> their client processing need to wait? What's the harm in letting
> start() do the waiting? Wouldn't that ensure a minimum wait time and
> consistent behavior?
>
> On Sun, Feb 10, 2013 at 11:23 PM, John Vines <[EMAIL PROTECTED]> wrote:
>> I don't think so, all of our client processes are designed to wait a bit
>> for the server to come up, and this process a similar behavior as our
>> start-all script.
>>
>> Sent from my phone, please pardon the typos and brevity.
>> On Feb 10, 2013 10:59 PM, "David Medinets" <[EMAIL PROTECTED]>
wrote:
>>
>>> Adding a Thread.sleep(1) after the start() method does seem to
>>> consistently resolve the 'Stream Closed' issue.
>>>
>>>       MiniAccumuloCluster la = new MiniAccumuloCluster(tmpDir,
"pass1234");
>>>       la.start();
>>>       Thread.sleep(1);
>>>
>>> Which raises a question. Should the start method wait for the
>>> processes to start before returning? Any reason I shouldn't create a
>>> jira ticket for this?
>>>
>>> On Sat, Feb 9, 2013 at 8:45 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:
>>> > I wonder if it is just because you're starting and stopping so
quickly. I
>>> > know the Tserver processes take a second to come up, perhaps put a
sleep
>>> in
>>> > for a few seconds and see if that works.
>>> >
>>> >
>>> > On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <
[EMAIL PROTECTED]
>>> >wrote:
>>> >
>>> >> https://issues.apache.org/jira/browse/ACCUMULO-1058
>>> >>
>>> >> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]>
>>> wrote:
>>> >> > Should probably have documentation and a working example prior to
>>> 1.5.0.
>>> >> Is there already a ticket for it?
>>> >>
>>>
>

I think having MiniAccumuloCluster.start() block until all the services are
up is a good thing. I've been seeing somewhat unpredictable behavior also,
and this could avoid a lot of questions in the future. The use case of
starting the cluster and using a client on it immediately is not typical.
On Mon, Feb 11, 2013 at 5:51 AM, Josh Elser <[EMAIL PROTECTED]> wrote:

> I'd have to agree with you, David. I like MiniAccumuloCluster and think
> there is great worth to be had from it. We should do the most we can to
> make it easy to use.
>
> I will say that I imagine it to be difficult to pinpoint exactly when
> Accumulo is "up". If there isn't a good way to avoid your exception by
> blocking internally, some documentation/warning is a good idea.
>
> On Sunday, February 10, 2013, David Medinets <[EMAIL PROTECTED]>
> wrote:
> > But if people start using the MiniAccumuloCluster without knowing
> > their client processing need to wait? What's the harm in letting
> > start() do the waiting? Wouldn't that ensure a minimum wait time and
> > consistent behavior?
> >
> > On Sun, Feb 10, 2013 at 11:23 PM, John Vines <[EMAIL PROTECTED]> wrote:
> >> I don't think so, all of our client processes are designed to wait a bit
> >> for the server to come up, and this process a similar behavior as our
> >> start-all script.
> >>
> >> Sent from my phone, please pardon the typos and brevity.
> >> On Feb 10, 2013 10:59 PM, "David Medinets" <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> Adding a Thread.sleep(1) after the start() method does seem to
> >>> consistently resolve the 'Stream Closed' issue.
> >>>
> >>>       MiniAccumuloCluster la = new MiniAccumuloCluster(tmpDir,
> "pass1234");
> >>>       la.start();
> >>>       Thread.sleep(1);
> >>>
> >>> Which raises a question. Should the start method wait for the
> >>> processes to start before returning? Any reason I shouldn't create a
> >>> jira ticket for this?
> >>>
> >>> On Sat, Feb 9, 2013 at 8:45 PM, Jim Klucar <[EMAIL PROTECTED]> wrote:
> >>> > I wonder if it is just because you're starting and stopping so
> quickly. I
> >>> > know the Tserver processes take a second to come up, perhaps put a
> sleep
> >>> in
> >>> > for a few seconds and see if that works.
> >>> >
> >>> >
> >>> > On Sat, Feb 9, 2013 at 8:40 PM, David Medinets <
> [EMAIL PROTECTED]
> >>> >wrote:
> >>> >
> >>> >> https://issues.apache.org/jira/browse/ACCUMULO-1058
> >>> >>
> >>> >> On Sat, Feb 9, 2013 at 8:04 PM, Christopher <[EMAIL PROTECTED]>
> >>> wrote:
> >>> >> > Should probably have documentation and a working example prior to
> >>> 1.5.0.
> >>> >> Is there already a ticket for it?
> >>> >>
> >>>
> >
>

On Fri, Feb 8, 2013 at 10:19 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> When running the MapReduceExample (with no changes) I see the
> following message and the Usage message:
>
>   Was passed main parameter 'miniInstance' but no main parameter was defined
>
> What other parameters need to be provided? I searched all files but do
> not see any documentation for this program.

The command line options for ContinuousIngest where changed in
ACCUMULO-745.  This example was not updated to use the new command
line options, I will fix it..

I just checked in a fix.  Can you try running it now?

On Fri, Feb 8, 2013 at 10:19 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> When running the MapReduceExample (with no changes) I see the
> following message and the Usage message:
>
>   Was passed main parameter 'miniInstance' but no main parameter was defined
>
> What other parameters need to be provided? I searched all files but do
> not see any documentation for this program.

On Fri, Feb 8, 2013 at 10:19 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> When running the MapReduceExample (with no changes) I see the
> following message and the Usage message:
>
>   Was passed main parameter 'miniInstance' but no main parameter was defined
>
> What other parameters need to be provided? I searched all files but do
> not see any documentation for this program.

There is  some documentation at examples/instamo/README.md

After 1.5.0 is released I want to put something like the following on
the Accumulo web page using examples instamo.

https://github.com/keith-turner/instamo

The basic idea is to offer something where someone could be writing
code against 1.5.0 in minutes.  I should probably look into including
support for the proxy in instamo 1.5.0.  It would be nice if someone
could be writing python programs that use Accumulo in a few minutes.

I pulled the latest Accumulo code, compiled it so I have new jar
files. Then ran the MapReduceExample with no modifications. Here is
the output ... note the stacktrace:

   ---- Running Mapred Against Accumulo

13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:zookeeper.version=3.3.1-942149, built on 05/07/2010 17:14
GMT
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:host.name=ubuntu20gb
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.version=1.7.0_09
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.vendor=Oracle Corporation
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.home=/usr/local/jdk1.7.0_09/jre
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.class.path=/home/medined/workspace/accumulo_playground/target/classes:/home/medined/workspace/accumulo_playground/target/test-classes:/home/medined/springsource/sts-3.1.0.RELEASE/plugins/org.junit_4.10.0.v4_10_0_v20120426-0900/junit.jar:/home/medined/springsource/sts-3.1.0.RELEASE/plugins/org.hamcrest.core_1.1.0.v20090501071000.jar:/home/medined/workspace/accumulo_playground/lib/commons-cli-1.2.jar:/home/medined/workspace/accumulo_playground/lib/commons-codec-1.5.jar:/home/medined/workspace/accumulo_playground/lib/commons-logging-1.0.4.jar:/home/medined/workspace/accumulo_playground/lib/commons-logging-api-1.0.4.jar:/home/medined/workspace/accumulo_playground/lib/hadoop-core-0.20.2.jar:/home/medined/workspace/accumulo_playground/lib/libthrift-0.6.1.jar:/home/medined/workspace/accumulo_playground/lib/log4j-1.2.16.jar:/home/medined/workspace/accumulo_playground/lib/slf4j-api-1.5.6.jar:/home/medined/workspace/accumulo_playground/lib/slf4j-log4j12-1.4.3.jar:/home/medined/workspace/accumulo_playground/lib/zookeeper-3.3.1.jar:/home/medined/workspace/accumulo_playground/lib/commons-jci-fam-1.0.jar:/home/medined/workspace/accumulo_playground/lib/commons-jci-core-1.0.jar:/home/medined/workspace/accumulo_playground/lib/commons-math3-3.0.jar:/home/medined/workspace/accumulo_playground/lib/commons-lang-2.4.jar:/home/medined/workspace/accumulo_playground/lib/commons-collections-3.2.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-core-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-examples-simple-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-fate-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-proxy-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-server-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-start-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-test-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-trace-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/commons-io-2.4.jar:/home/medined/workspace/accumulo_playground/lib/jcommander-1.30.jar
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.library.path=/usr/local/jdk1.7.0_09/jre/lib/i386/client:/usr/local/jdk1.7.0_09/jre/lib/i386:/usr/local/jdk1.7.0_09/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386:/usr/lib/jvm/java-6-openjdk-i386/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.io.tmpdir=/tmp
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:java.compiler=<NA>
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client environment:os.name=Linux
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client environment:os.arch=i386
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:os.version=3.2.0-35-generic-pae
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client environment:user.name=medined
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:user.home=/home/medined
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
environment:user.dir=/home/medined/workspace/accumulo_playground
13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Initiating client
connection, connectString=localhost:3489 sessionTimeout=30000
watcher=org.apache.accumulo.fate.zookeeper.ZooSession$ZooWatcher@11b16
13/02/12 19:34:45 INFO zookeeper.ClientCnxn: Opening socket connection
to server localhost/127.0.0.1:3489
13/02/12 19:34:45 WARN zookeeper.ClientCnxn: Session 0x0 for server
null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1078)
I am using SVN#1445420 with Java v1.7.0_09-b05 on Ubuntu inside of Eclipse.

If I comment out the run() call inside main() as I did before, I am
still seeing this:

java.io.IOException: Stream closed
at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:162)
at java.io.BufferedInputStream.read(BufferedInputStream.java:325)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:154)
at java.io.BufferedReader.readLine(BufferedReader.java:317)
at java.io.BufferedReader.readLine(BufferedReader.java:382)
at org.apache.accumulo.test.MiniAccumuloCluster$LogWriter.run(MiniAccumuloCluster.java:88)

On Tue, Feb 12, 2013 at 9:03 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> I pulled the latest Accumulo code, compiled it so I have new jar
> files. Then ran the MapReduceExample with no modifications. Here is
> the output ... note the stacktrace:

Are you still seeing this issue?  How are you running the program?
Can you comment out the part of the test where it deletes it tmp dir
and look at the logs after the test?  Should be something like
/tmp/macc-<UUID>/logs.   I am wondering if the zookeeper server is
dying for some reason, there should be a log for the zookeeper server.

Thanks.

>
>    ---- Running Mapred Against Accumulo
>
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:zookeeper.version=3.3.1-942149, built on 05/07/2010 17:14
> GMT
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:host.name=ubuntu20gb
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.version=1.7.0_09
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.vendor=Oracle Corporation
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.home=/usr/local/jdk1.7.0_09/jre
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.class.path=/home/medined/workspace/accumulo_playground/target/classes:/home/medined/workspace/accumulo_playground/target/test-classes:/home/medined/springsource/sts-3.1.0.RELEASE/plugins/org.junit_4.10.0.v4_10_0_v20120426-0900/junit.jar:/home/medined/springsource/sts-3.1.0.RELEASE/plugins/org.hamcrest.core_1.1.0.v20090501071000.jar:/home/medined/workspace/accumulo_playground/lib/commons-cli-1.2.jar:/home/medined/workspace/accumulo_playground/lib/commons-codec-1.5.jar:/home/medined/workspace/accumulo_playground/lib/commons-logging-1.0.4.jar:/home/medined/workspace/accumulo_playground/lib/commons-logging-api-1.0.4.jar:/home/medined/workspace/accumulo_playground/lib/hadoop-core-0.20.2.jar:/home/medined/workspace/accumulo_playground/lib/libthrift-0.6.1.jar:/home/medined/workspace/accumulo_playground/lib/log4j-1.2.16.jar:/home/medined/workspace/accumulo_playground/lib/slf4j-api-1.5.6.jar:/home/medined/workspace/accumulo_playground/lib/slf4j-log4j12-1.4.3.jar:/home/medined/workspace/accumulo_playground/lib/zookeeper-3.3.1.jar:/home/medined/workspace/accumulo_playground/lib/commons-jci-fam-1.0.jar:/home/medined/workspace/accumulo_playground/lib/commons-jci-core-1.0.jar:/home/medined/workspace/accumulo_playground/lib/commons-math3-3.0.jar:/home/medined/workspace/accumulo_playground/lib/commons-lang-2.4.jar:/home/medined/workspace/accumulo_playground/lib/commons-collections-3.2.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-core-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-examples-simple-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-fate-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-proxy-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-server-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-start-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-test-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/accumulo-trace-1.5.0-SNAPSHOT.jar:/home/medined/workspace/accumulo_playground/lib/commons-io-2.4.jar:/home/medined/workspace/accumulo_playground/lib/jcommander-1.30.jar
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.library.path=/usr/local/jdk1.7.0_09/jre/lib/i386/client:/usr/local/jdk1.7.0_09/jre/lib/i386:/usr/local/jdk1.7.0_09/jre/../lib/i386:/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/client:/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386:/usr/lib/jvm/java-6-openjdk-i386/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.io.tmpdir=/tmp
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client
> environment:java.compiler=<NA>
> 13/02/12 19:34:45 INFO zookeeper.ZooKeeper: Client environment:os.name=Linux

I am still seeing the Connection Refused message. However, inside the
error logs I see NoClassDefFoundError:
org/apache/commons/vfs2/FileSystemManager. I will start adding jars to
my classpath until I get a harder error to resolve :)  Will report my
results later.

I add the VFS2 jar to my classpath. Now this message is displaying:

Exception in thread "main" java.lang.RuntimeException: Initialize
process returned 1
at org.apache.accumulo.test.MiniAccumuloCluster.start(MiniAccumuloCluster.java:326)
at com.codebits.accumulo.MapReduceExample.main(MapReduceExample.java:55)

The code that generates this message is

    Process initProcess = exec(Initialize.class, "--instance-name",
INSTANCE_NAME, "--password", config.getRootPassword(), "--username",
"root");
    int ret = initProcess.waitFor();
    if (ret != 0) {
      throw new RuntimeException("Initialize process returned " + ret);
    }

There are no log files in the /tmp directory. Not sure what to do from
here. I will look at the Initialize class for clues.

On Wed, Feb 13, 2013 at 5:26 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> I am still seeing the Connection Refused message. However, inside the
> error logs I see NoClassDefFoundError:
> org/apache/commons/vfs2/FileSystemManager. I will start adding jars to
> my classpath until I get a harder error to resolve :)  Will report my
> results later.

On Wed, Feb 13, 2013 at 5:51 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> I add the VFS2 jar to my classpath. Now this message is displaying:
>
> Exception in thread "main" java.lang.RuntimeException: Initialize
> process returned 1
>         at org.apache.accumulo.test.MiniAccumuloCluster.start(MiniAccumuloCluster.java:326)
>         at com.codebits.accumulo.MapReduceExample.main(MapReduceExample.java:55)
>
> The code that generates this message is
>
>     Process initProcess = exec(Initialize.class, "--instance-name",
> INSTANCE_NAME, "--password", config.getRootPassword(), "--username",
> "root");
>     int ret = initProcess.waitFor();
>     if (ret != 0) {
>       throw new RuntimeException("Initialize process returned " + ret);
>     }
>
> There are no log files in the /tmp directory. Not sure what to do from
> here. I will look at the Initialize class for clues.

Look in whatever directory you passed to the MiniAccumuloCluster constructor.

>
> On Wed, Feb 13, 2013 at 5:26 PM, David Medinets
> <[EMAIL PROTECTED]> wrote:
>> I am still seeing the Connection Refused message. However, inside the
>> error logs I see NoClassDefFoundError:
>> org/apache/commons/vfs2/FileSystemManager. I will start adding jars to
>> my classpath until I get a harder error to resolve :)  Will report my
>> results later.

I am sprinkling println statements around. I noticed in
MiniAccumuloCluster.exec my HADOOP_PREFIX is null. Is that OK?

    String env = System.getenv("HADOOP_PREFIX");
    if (env != null)
      builder.environment().put("HADOOP_PREFIX", env);
    System.out.println("HADOOP_PREFIX: " + env);

On Wed, Feb 13, 2013 at 5:51 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> I add the VFS2 jar to my classpath. Now this message is displaying:
>
> Exception in thread "main" java.lang.RuntimeException: Initialize
> process returned 1
>         at org.apache.accumulo.test.MiniAccumuloCluster.start(MiniAccumuloCluster.java:326)
>         at com.codebits.accumulo.MapReduceExample.main(MapReduceExample.java:55)
>
> The code that generates this message is
>
>     Process initProcess = exec(Initialize.class, "--instance-name",
> INSTANCE_NAME, "--password", config.getRootPassword(), "--username",
> "root");
>     int ret = initProcess.waitFor();
>     if (ret != 0) {
>       throw new RuntimeException("Initialize process returned " + ret);
>     }
>
> There are no log files in the /tmp directory. Not sure what to do from
> here. I will look at the Initialize class for clues.
>
> On Wed, Feb 13, 2013 at 5:26 PM, David Medinets
> <[EMAIL PROTECTED]> wrote:
>> I am still seeing the Connection Refused message. However, inside the
>> error logs I see NoClassDefFoundError:
>> org/apache/commons/vfs2/FileSystemManager. I will start adding jars to
>> my classpath until I get a harder error to resolve :)  Will report my
>> results later.