-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to fetch the target s3 file #3
Comments
@kraviteja sorry for the trouble; I believe I fixed this issue this morning. I know it has been 2 and a half months; lemme know if you retry and are successful. |
@jnh5y Thank you for the fix, I could see the logs for the tablet servers. Can you please let me know where are the logs going for accumulo master. |
The logs for the Accumulo master process would be on the master AWS node. If you ssh there, I'd check /var/log/accumulo and $ACCUMULO_HOME/logs. (I can remember where Accumulo puts its logs in the GeoDocker version of things...) |
The issue is logs are not coming up in $ACCUMULO_HOME/logs directory. Can
you let me know how do I fix that ?
…On Thu, Oct 26, 2017 at 2:56 PM, James Hughes ***@***.***> wrote:
The logs for the Accumulo master process would be on the master AWS node.
If you ssh there, I'd check /var/log/accumulo and $ACCUMULO_HOME/logs. (I
can remember where Accumulo puts its logs in the GeoDocker version of
things...)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFDNoaZeVhP9Vw5MR7FON4jwCCglwG5iks5swOQGgaJpZM4MA7bx>
.
|
Hmm... where are you looking? You might have to attach a Bash shell to the Docker instance and check there... I'm not a Docker expert, you might be able to get a quicker answer here: https://gitter.im/geodocker/geodocker. |
I used the command
can anyone point me to the |
From the docs, http://www.geomesa.org/documentation/tutorials/geodocker-geomesa-spark-on-aws.html#bootstrap-an-emr-cluster
Unable to launch the cluster, as bootstrap action is not working
aws emr create-cluster
--name "GeoDocker GeoMesa"
--release-label emr-5.2.0
--output text
--use-default-roles
--ec2-attributes KeyName=KEY_NAME
--applications Name=Hadoop Name=Zookeeper Name=Spark
--instance-groups
Name=Master,InstanceCount=1,InstanceGroupType=MASTER,InstanceType=m3.xlarge
Name=Workers,InstanceCount=3,InstanceGroupType=CORE,InstanceType=m3.xlarge
--bootstrap-actions
Name=BootstrapGeoMesa,Path=s3://geomesa-docker/bootstrap-geodocker-accumulo.sh,Args=[-t=geomesa-$VERSION-accumulo-1.8.0,-n=gis,-p=secret,-e=TSERVER_XMX=10G,-e=TSERVER_CACHE_DATA_SIZE=6G,-e=TSERVER_CACHE_INDEX_SIZE=2G]
The text was updated successfully, but these errors were encountered: