Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # user >> Running Helloworld from different host


Copy link to this message
-
Re: Running Helloworld from different host
Thanks guys.  Nevermind... I just found this link.
http://mail-archives.apache.org/mod_mbox/incubator-accumulo-user/201201.mbox/%[EMAIL PROTECTED]%3E

By putting the ipaddress (rather than "localhost.localdomain") into all the
conf/* files like master, slave, etc., it now works.  I didn't have any DNS
set up.  duh

On Fri, Dec 21, 2012 at 11:52 AM, John Vines <[EMAIL PROTECTED]> wrote:

> From the #Accumulo room, since you seem to have missed my response-
>
> (12:34:43 PM) vines: 127.0.0.1:9997 is the tserver
> (12:35:48 PM) vines: The tserver will list itself as what the scripts
> think it should be. So if you define your zookeeper as being at 127.0.0.1
> it will say it's there. It will put itself in as whatever the hostname maps
> to per ipconfig
> (12:36:13 PM) vines: This has resulted in some weird behavior when you
> have your loopback adapter listed before you real ones, though
>
>
> On Fri, Dec 21, 2012 at 12:49 PM, William Slacum <
> [EMAIL PROTECTED]> wrote:
>
>> On your accumulo master, what do you you in your conf/slaves file?
>>
>>
>> On Fri, Dec 21, 2012 at 9:43 AM, Kevin Pauli <[EMAIL PROTECTED]> wrote:
>>
>>> Hi, I'm trying to get my first Accumulo environment setup to evaluate
>>> it.  I've got it running within a CentOS VM, and I've setup the helloworld
>>> data.
>>>
>>> My CentOS guest IP is 192.168.254.130.  The helloworld examples work
>>> fine from an ssh attached to the guest OS.
>>>
>>> I'm now trying to access the helloworld data from my host OS, via the
>>> org.apache.accumulo.examples.simple.helloworld.ReadData program.  It gets
>>> this far:
>>>
>>> [11:04:41.868] INFO: Initiating client connection, connectString>>> 192.168.254.130:2181 sessionTimeout=30000
>>> watcher=org.apache.accumulo.core.zookeeper.ZooSession$AccumuloWatcher@3ca55242
>>>
>>> [11:04:46.432] INFO: Opening socket connection to server
>>> 192.168.254.130/192.168.254.130:2181. Will not attempt to authenticate
>>> using SASL (unknown error)
>>> [11:04:46.439] INFO: Socket connection established to
>>> 192.168.254.130/192.168.254.130:2181, initiating session
>>> [11:04:46.459] INFO: Session establishment complete on server
>>> 192.168.254.130/192.168.254.130:2181, sessionid = 0x13bba6809700691,
>>> negotiated timeout = 30000
>>> WARN [main] (ServerClient.java:156) - Failed to find an available server
>>> in the list of servers: [127.0.0.1:9997:9997 (120000)]
>>>
>>> I'm wondering where that that value 127.0.0.1:9997:9997 is coming from.
>>>  Is that Zookeeper trying to redirect me to the Accumulo server?  Do I want
>>> it to be 192.168.254.130:9997 instead, since from my host OS's
>>> perspective, 127.0.0.1 is the host OS localhost, not the guest OS?  If so,
>>> how do I configure accumulo's registration within Zookeeper?
>>>
>>> I have opened up port 9997 in the CentOS guest.
>>>
>>> Apologies as I am new to Zookeeper as well as Accumulo.
>>>
>>> --
>>> Regards,
>>> Kevin Pauli
>>
>>
>>
>
--
Regards,
Kevin Pauli