Hi Nico,
Good question. That project is actually an older copy of an
internal GeoMesa Docker project here at CCRi. We haven't been
actively working on it for awhile. Today I learned about a more
active project here:
https://github.com/pomadchin/geo-env; it may be
worth a look. I'm in the GeoTrellis gitter
(
https://gitter.im/geotrellis/geotrellis) and you could likely get
support from 'pomadchin' with the general use of the project.
That aside, to answer your final question, from what I know about
Docker, each running Docker image has some amount of network
virtualization. If you have a shell in the Docker image, you can
probably ping 172.17.0.5 and the server-domain name may resolve to
that.
Said differently, it is quite easy to have a one-node VM/Docker
image where the masters/slaves/monitor/traces files point to a
reference which has different resolution from 'inside' and 'outside'
the environment. For example, if those files contain 'localhost',
then things will likely work from 'inside', but not 'outside'. In a
Docker example, there may need to be some fiddling to get the same
code to work in both scopes.
I hope that helped. If not, lemme know and let's iterate!
Cheers,
Jim
On 02/08/2016 06:00 PM, Nico Kreiling
wrote:
Hello,
I used a GeoMesa Docker installation (
https://github.com/rheilgm/testgeo)
and updated the links for it to work (Hadoop 2.2, Accumulo
1.5.2, Geomesa 1.1.0-rc.7, zk 3.4.6. It all works great and i
can insert data from geomesa tools locally, but when I try to
connect to it via Java `
DataStoreFinder.getDataStore(dsConf);` I get the message: Failed
to find an available server in the list of servers:
[172.17.0.5:9997 (120000)]
The Java Code itself should be fine since I can
connect to another, native installed geomesa instance. Also the
connection parameters should be correct, I tested them with
Geomesa tools and was able to create a catalog via remote
access. I guess my installation configuration is somehow wrong.
I inserted the server-domain name in the masters,
slaves, monitor and tracers conf file. The other configurations
should be the same as in the repo.
Any ideas what I can do? I also don’t really
understand why the tablet server gets the ip 172.17.0.5.
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
