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] < [email protected]> 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 > [email protected] > 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.
