Not a waste of time at all. :-)
Right, src/contrib/ec2/ becomes contrib/ec2/ after 'ant package' with
appropriate substitutions.
- Andy
> From: Tim Robertson
> Subject: Re: EC2 scripts
> To: apurt...@apache.org, hbase-user@hadoop.apache.org
> Date: Saturday, Ma
Should be better now:
% export EC2_URL="https://eu-west-1.ec2.amazonaws.com";
% ec2-describe-images
[...]
ami-0996bd7d apache-hbase-images-eu/hbase-0.20.3-i386.manifest.xml
available public i386
ami-0b96bd7f apache-hbase-images-eu/hbase-0.20.3-x86_64.manifest.xml
available public x86
Geez I'm stupid... HBASE_VERSION=0.20.3 was missing all along and
still set to %HBASE_VERSION%. I am using the scripts in the
src/contrib/ec2 but should have started with /contrib/ec2 which has it
set already right?
Sorry for wasting your time Andy, it's taking a while for each one but
ZK is now
Tim,
Try these scripts:
http://hbase.s3.amazonaws.com/hbase/hbase-ec2-eu.tar.gz
I'd appreciate it. They are what I'm working with now over in eu-west-1 with no
issues. I'll have AMIs for HBase 0.20.3 on Hadoop 0.20.2 ready to go in the EU
within the hour. Please let me know if you continue
> From: Tim Robertson
> I added to the ec2 env:
> EC2_URL=https://us-east-1.ec2.amazonaws.com
>
> and also:
> $ echo $EC2_URL
> https://us-east-1.ec2.amazonaws.com
>
> But the error remains:
>
> Required parameter 'AMI' missing (-h for usage)
> Waiting for instance to start: .[Deprecated
"I have also never seen the Xalan complaints. What OS?"
Mac OSX 10.5.8 (not leopard) and java 1.6.0_17
It is a known issue on Macs and Java 6 apparently. The recommendation
seems to be to hide the warning in the EC2 scripts themselves but I
didn't bother. I get it even on an ec2-describe-instanc
/* locally before doing anything will clear up any potential problem
with missing +x.
Meantime, I am finally getting around to building HBase AMIs in all EC2
regions. Sorry for the trouble.
- Andy
> From: Tim Robertson
> Subject: Re: EC2 scripts
> To: hbase-user@hadoop.apache.o
Hi Andy,
Thanks - appreciate that. I haven't used EC2 in a while and it was
always US-East last time despite me being in Europe, but I'll dig into
it.
Actually I started creating my own hbase AMI today using your scripts
but it failed on
/mnt/create-hbase-image-remote
with privileges error. I
Hi Tim,
Currently we only have public AMIs registered in the us-east-1 region. EC2 AMIs
are region-locked. So the scripts are not finding any public AMIs for the
region you are running in -- EU? -- hence the error.
I have also never seen the Xalan complaints. What OS?
I did replicate the AMI
[Copied to hbase-u...@]
Hi Lars,
> Required parameter 'AMI' missing (-h for usage)
> I guess that is OK?
No, that means the scripts are not picking up a valid public AMI.
I think you may be the first to attempt to use the EC2 scripts in the EU.
One thing I did not mention in my presentation i
mber 19, 2009 2:52:18 PM
Subject: Re: EC2 scripts
Thanks Andrew,
Your scripts are working fine. We restarted everything and tested, and they
are working fine. A few issues though :
- While starting, launch-hbase-cluster gives the following error.
error: "fs.epoll.max_user_instan
ort'?
Thanks for trying this out Naresh.
- Andy
From: Naresh Rapolu
To: hbase-user@hadoop.apache.org
Sent: Thu, November 19, 2009 9:09:54 AM
Subject: Re: EC2 scripts
Thanks Andrew,
We`ve made a private instance with our keys, by altering your public hbase AMI
and us
laves, and
also the full output of the cluster launch if you can capture that into a
buffer and save it to a file.
Thanks,
- Andy
From: Andrew Purtell
To: hbase-user@hadoop.apache.org
Sent: Thu, November 19, 2009 9:28:51 AM
Subject: Re: EC2 scripts
So it
- Andy
From: Naresh Rapolu
To: hbase-user@hadoop.apache.org
Sent: Thu, November 19, 2009 9:09:54 AM
Subject: Re: EC2 scripts
Thanks Andrew,
We`ve made a private instance with our keys, by altering your public hbase AMI
and used it to launch the cluster instances.
We are now able to do
Thanks Andrew,
We`ve made a private instance with our keys, by altering your public
hbase AMI and used it to launch the cluster instances.
We are now able to do "ssh slave" from master. But, still the problem
persists. From the hbase shell of master, "status 'simple' " returns
0 live ser
As for convenient ssh between master and slaves, that's an easy thing to set
up. I'll put up an issue for that.
On Wed Nov 18th, 2009 11:07 PM PST Andrew Purtell wrote:
>1) How long did you wait before logging on to the master and checking status?
>I bet if you checked the slave instances statu
1) How long did you wait before logging on to the master and checking status? I
bet if you checked the slave instances status at that time (e.g. using
elasticfox) they were still pending startup. The slaves are started last and
EC2 may not start them right away nor all at once.
2) The way priva
17 matches
Mail list logo
