Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-users] Bootstrapping GeoMesa HBase on AWS S3
Hey,

@Emilio
You were right, the jar from s3 could not be copied. The problem was in the conf/hbase-site.xml.
I have set the hbase.rootdir to s3://<my-bucket>/root/ like this:

<property>
    <name>hbase.rootdir</name>
    <value>s3://<my-bucket>/root/</value>
  </property>

I had to remove the last backslash, than it worked just right (correct way for me: s3://<my-bucket>/root).
When the backslash was appended, the bootstrap script would create a new directory called " " in S3.

So the jar was saved to s3://<my-bucket>/root//lib/geomesa-hbase-distributed-runtime_2.11-2.0.2.jar
Later geomesa-hbase tried go get the jar from s3://<my-bucket>/root/lib/geomesa-hbase-distributed-runtime_2.11-2.0.2.jar, which obviously does not work.

Thanks for the help.
Martin


Am Mo., 15. Okt. 2018 um 14:53 Uhr schrieb Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx>:
Hello,

I believe the script tries to copy that jar to s3, and then expects it to be there. Can you check that bucket and see if the jar is there? Are you using the 2.0.2 tag? Possibly the jar version is different, which could cause a problem.

The underlying issue is that the script is trying to register the GeoMesa coprocessors on your tables, and it doesn't seem to be doing it quite right. There are more details on coprocessors here, which may help you debug the issue:

https://www.geomesa.org/documentation/user/hbase/install.html#deploying-the-geomesa-hbase-distributed-runtime-jar
https://www.geomesa.org/documentation/user/hbase/install.html#register-the-coprocessors

Thanks,

Emilio

On 10/15/2018 07:17 AM, Martin Kellner wrote:
Hey,

I got another question to the tutorial "Bootstrapping GeoMesa HBase on AWS S3".
I have setup the EMR Cluster and the S3 Bucket. 
Then I executed the shell script, that bootstraps Geomesa on Hbase.

Finally I tried the given gdelt example.
But when I execute the geomesa-hbase ingest command, I get the following errror:

ERROR org.apache.hadoop.hbase.DoNotRetryIOException: s3://<my-bucket>/lib/geomesa-hbase-distributed-runtime_2.11-2.0.2.jar Set hbase.table.sanity.checks to false at conf or table descriptor if you want to bypass sanity checks
        at org.apache.hadoop.hbase.master.HMaster.warnOrThrowExceptionForFailure(HMaster.java:2006)
        at org.apache.hadoop.hbase.master.HMaster.sanityCheckTableDescriptor(HMaster.java:1859)
        at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1761)
        at org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:483)
        at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:64096)
        at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2354)
        at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124)
        at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:297)
        at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:277)

Has anybody experienced that before?

Thank you,
Martin



_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users

_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users

Back to the top