User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
Sounds good! Just to clarify, I meant the geoserver plugin
processing requirements are fairly different. It shouldn't matter
where/how the actual hbase and kafka clusters are installed.
Thanks,
Emilio
On 1/25/21 12:15 PM, Sangeetha S wrote:
Hi Emilio,
thanks for your reply. In my case, Kafka, HBase and
GeoServer are all installed in different machines. I'll try to
put both plugins in the same GeoServer and update here how it
goes.
Thanks,
Sangeetha
On Fri, Jan 22, 2021 at 10:44
PM Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx> wrote:
Hello,
I don't know of anything off the top of my head, but you
might be better off keeping them separate if possible, as
the memory and processing requirements are fairly different
between the two. Kafka requires a fairly large memory
overhead because it caches all the data in memory, while
HBase doesn't require much memory but tends to require more
threads and I/O. If you do put them in the same GeoServer,
it's possible you'll hit incompatible dependency conflicts -
if that happens, you could build shaded/relocated jars to
get around it.
Thanks,
Emilio
On 1/22/21 11:20 AM, Sangeetha S wrote:
Hi all,
I have been using GeoMesa HBase for almost a year
and now, I would like to use GeoMesa Kafka as well.
The question I have is: I plan to install the GeoMesa
Kafka plugin in the same GeoServer where I have
GeoMesa HBase plugin already installed. From your
knowledge and experience, are you aware of any issues
this might cause? I would just like to be sure that
the libraries that I newly install on the GeoServer do
not affect the GeoMesa HBase plugin which is already
installed and working.