GeoServer doesn't have to run on any particular machine, although it
needs to be able to access the hbase cluster.
The 's3 schema' error is probably related to not having the aws
hadoop jars in geoserver - you should be able to fix that just with
aws hadoop jars, without needing any hbase jars.
Thanks,
Emilio
On 06/29/2018 12:03 PM, Gaetano Perrone
wrote:
Hi Emilio, I forgot an important thing : geoserver is on
another machine different than geomachine, so I have uploaded
suggested libraries here; is this a problem? Must geoserver
run on the same machine of geomesa? (we should avoid this in
order to scale the application server)...
About the issue, could you try to see Catalina
and geoserver data logs to see if there is a 'Unable to
understand fs s3 schema' error? If there is this error,
geoserver seems to work, but the application is not able to
use the coprocessor dynamic library...
As I can I will send you all jars inside
geoserver web inf lib directory in order to solve the
issue...
Thanks in advance,
Gaetano
You can definitely
run against emr hbase 1.3, using the normal geomesa
shaded jar. I've done that before, but I don't have a
list of required jars handy. What additional jars are
you copying into the lib folder?
I would guess that if you can get it working against
1.3, it would also work against hbase 1.4 with the same
setup.
You might take a look at
http://www.geomesa.org/documentation/tutorials/geomesa-hbase-s3-on-aws.html,
which doesn't cover geoserver but might have some useful
details.
Thanks,
Emilio
On
06/29/2018 06:19 AM, Gaetano Perrone wrote:
Hi Emilio, thanks for the answer;
I have followed all your steps (by using the
built master git jar and the last release version
2.0.2) but unfortunately on emr environment I
always have the same error:
Caused by: java.lang.NoClassDefFoundError:
Could not initialize class
org.apache.hadoop.hbase.protobuf.ProtobufUtil
at
org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
at
org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
at
org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
at
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:907)
at
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.<init>(ConnectionManager.java:691)
I also have tried to change emr hbase version
to 1.3 as you suggested (and the opposite, compile
the plugin with 1.4 hbase version) ...
Do you have any other suggestion ?
Thanks in advance .
Gaetano
_______________________________________________
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
_______________________________________________
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
|