ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Kozlov <skoz...@gridgain.com>
Subject Extend TcpDiscoveryVmIpFinder functionality
Date Mon, 09 Jan 2017 09:25:37 GMT
Hi Igniters

I found that TcpDiscoveryVmIpFinder could be improved for Spring
configuration by introducing new format: *address/mask:port(port range) or
address/prefix:port(port range)*. From my standpoint it will reduce the
efforts for ignite deployment and administration.
For instance if we've a dedicated network for the grid and not able to use
multicast way we should put each IP to the address list:

<property name="ipFinder">
  <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
    <property name="addresses">
      <list>
        <value>10.0.0.1:48500</value>
        <value>10.0.0.2:48500</value>
        <value>10.0.0.3:48500</value>
        ...
        <value>10.0.0.100:48500</value>
      </list>
    </property>
  </bean>
</property>

but can be simplified to

1) with using of the netmask

<property name="ipFinder">
  <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
    <property name="addresses">
      <list>
        <value>10.0.0.1/255.255.255.0:48500</value>
      </list>
    </property>
  </bean>
</property>

2) with using of the network prefix

<property name="ipFinder">
  <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
    <property name="addresses">
      <list>
        <value>10.0.0.1/24:48500</value>
      </list>
    </property>
  </bean>
</property>

Any comments/objections are welcome


-- 
Sergey Kozlov

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message