You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Swetad90 <sw...@gmail.com> on 2017/05/22 19:16:34 UTC
Port Range in JDBC Discovery
Hi
We are trying to set up non-interfering cluster group using JDBC Discovery.
We have assigned different table names for each cluster group and they are
not discovering one another.
But all nodes are taking available ports in the VM starting from 47500. Is
there any way we can set a port range for 1 cluster in JDBC Discovery or
local port.
I looked at registerAddresses in TcpDiscoveryJdbcIpFinder. Does this serve
the same purpose as we set multiple addresses with port range in
TcpDiscoveryVmIpFinder?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Port-Range-in-JDBC-Discovery-tp13076.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Port Range in JDBC Discovery
Posted by afedotov <al...@gmail.com>.
Hi.
It's not supported out of box for TcpDiscoveryJdbcIpFinder.
You could extend it and implement your own method similar to
TcpDiscoveryVmIpFinder#setAddresses
Kind regards,
Alex.
On Thu, May 25, 2017 at 10:42 PM, Swetad90 [via Apache Ignite Users] <
ml+s70518n13150h84@n6.nabble.com> wrote:
> Hi Alex,
>
> We are setting up separate tables for each cluster group.
> What I wanted to check was if we can give a port range rather than
> assigning each nodes host:port in JDBC Discovery?
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Port-
> Range-in-JDBC-Discovery-tp13076p13150.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1h65@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YWxleGFuZGVyLmZlZG90b2ZmQGdtYWlsLmNvbXwxfC0xMzYxNTU0NTg=>
> .
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Port-Range-in-JDBC-Discovery-tp13076p13154.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Port Range in JDBC Discovery
Posted by Swetad90 <sw...@gmail.com>.
Hi Alex,
We are setting up separate tables for each cluster group.
What I wanted to check was if we can give a port range rather than assigning
each nodes host:port in JDBC Discovery?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Port-Range-in-JDBC-Discovery-tp13076p13150.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Port Range in JDBC Discovery
Posted by afedotov <al...@gmail.com>.
Hi.
Regarding hints on the configuring isolated clusters please take a look at
the following
https://apacheignite.readme.io/v2.0/docs/cluster-config#
section-isolated-ignite-clusters-on-same-set-of-machines
TcpDiscoveryJdbcIpFinder#registerAddresses will register the specified
addresses in the underlying DB so that they
will become available for discovery by other nodes that use the same data
source.
To avoid nodes from one cluster being discovered by nodes from other
clusters
you need to route them to different tables. For that, you could pass into
TcpDiscoveryJdbcIpfinder constructor
a custom implementation of JdbcIpFinderDialect that will return a specific
table name.
Kind regards,
Alex.
On Mon, May 22, 2017 at 10:16 PM, Swetad90 [via Apache Ignite Users] <
ml+s70518n13076h90@n6.nabble.com> wrote:
> Hi
> We are trying to set up non-interfering cluster group using JDBC
> Discovery. We have assigned different table names for each cluster group
> and they are not discovering one another.
>
> But all nodes are taking available ports in the VM starting from 47500. Is
> there any way we can set a port range for 1 cluster in JDBC Discovery or
> local port.
>
> I looked at registerAddresses in TcpDiscoveryJdbcIpFinder. Does this serve
> the same purpose as we set multiple addresses with port range in
> TcpDiscoveryVmIpFinder?
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Port-
> Range-in-JDBC-Discovery-tp13076.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1h65@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YWxleGFuZGVyLmZlZG90b2ZmQGdtYWlsLmNvbXwxfC0xMzYxNTU0NTg=>
> .
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Port-Range-in-JDBC-Discovery-tp13076p13119.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.