Hello! Q1) This is because you can have more than one client or server node per host, that will make use of port range. Moreover, you only have to discovery one node via broadcast, and it will reveal the information of all other nodes it knows, along with addressed.
Q2) This is only possible with thin clients, such as JDBC or REST. Otherwise, "thick" Ignite client node will communicate to both node2 and node1. Regards, -- Ilya Kasnacheev 2018-07-16 9:09 GMT+03:00 monstereo <[email protected]>: > I have many question: > > - In local we have this line in config file: > > *bean > class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast. > TcpDiscoveryMulticastIpFinder"><property > name="addresses"><list><value>127.0.0.1:47500..47509</value> > </list></property>* > > If I understood properly, our node sends a broadcast to message to other > nodes which have address 127.0.0.1 and port numbers range is 47500-47509, > and those other nodes send their ip address to our nodes. > > *Q1) I have question about port number. Why port range is 47500-47509? We > can determine specific port number to specific node?* > > *Q2) Let's say I have 2 nodes, node 1 is holding all cache data, and node 2 > is holding also all cache data (REPLICATED), then I am creating clientNode3 > (which will be client), and I want clientNode3 to operate (insert,delete > ...) just on node2, and if there is an update on node2 caches, it will > delegate to node1 to uptade.(therefore database underlying these nodes will > be updated). Can I work on just one node?* > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
