JDBC connection issue from remote machine

classic Classic list List threaded Threaded
3 messages Options
Eric Lafleur Eric Lafleur
Reply | Threaded
Open this post in threaded view
|

JDBC connection issue from remote machine

I have an Ignite 1.2.0-incubating node running in a Docker container and Apache Zeppelin running in another one. When both containers run on the same machine, Zeppelin's Ignite SQL interpreter can connect through jdbc and access a given cache on Ignite.

However when I run the Zeppelin container on a different machine, I get a "Client is invalid. Probably cache name is wrong." exception although it's trying to access the exact same cache.

It doesn't seem like it's a networking issue since I guess I would get the "Failed to establish connection." exception in that case.

Do you have an idea about what could be causing that?
Thanks

-Eric
agura-2 agura-2
Reply | Threaded
Open this post in threaded view
|

Re: JDBC connection issue from remote machine

CONTENTS DELETED
The author has deleted this message.
Eric Lafleur Eric Lafleur
Reply | Threaded
Open this post in threaded view
|

Re: JDBC connection issue from remote machine

Hi Andrey,

Adding the "--net=host" parameter when I start my Ignite container did the trick. I was running it with just the "-p 11211:11211" flag to bind the container’s port to host. I thought that exposing the JDBC API to the host using port mapping would suffice.

Thank you

-Eric

-----Original Message-----
From: Andrey Gura <[hidden email]>
To: user <[hidden email]>
Sent: Tue, Jul 21, 2015 12:22 pm
Subject: Re: JDBC connection issue from remote machine

Eric,

could you please provide details about how do you start Docker containers in case of different machines?
Do you use "--net=host" parameter?

On Tue, Jul 21, 2015 at 11:24 AM, Eric Lafleur <[hidden email]> wrote:
I have an Ignite 1.2.0-incubating node running in a Docker container and Apache Zeppelin running in another one. When both containers run on the same machine, Zeppelin's Ignite SQL interpreter can connect through jdbc and access a given cache on Ignite.

However when I run the Zeppelin container on a different machine, I get a "Client is invalid. Probably cache name is wrong." exception although it's trying to access the exact same cache.

It doesn't seem like it's a networking issue since I guess I would get the "Failed to establish connection." exception in that case.

Do you have an idea about what could be causing that?
Thanks

-Eric



--
Andrey Gura
GridGain Systems, Inc.