Re: logging

[Jonathon Bell]

Yes, thanks, exactly what I needed. j

 On Jun 12, 2015, at 10:06 PM, Valentin Kulichenko 
 valentin.kuliche...@gmail.com wrote:
 
 Jonathon,
 
 IgniteMessaging facade can be created for a cluster group (see 
 message(ClusterGroup grp) method). So you can create a cluster group with 
 only one receiver node and create IgniteMessaging instance for this group. 
 All messages sent through this instance will be sent to that node only. The 
 receiver node should have a listener for correct topic, of course.
 
 Is this what you're looking for?
 
 -Val
 
 On Fri, Jun 12, 2015 at 3:00 PM, Jonathon Bell jonathon.a.b...@gmail.com 
 wrote:
 Hi All,
 
 I have a question about the way the publish-subscribe topic based messaging 
 system is implemented in ignite.
 
 I wish to send a large number of messages to n different tasks, each 
 potentially running on its own node. When sending each message, i know the 
 exact unique task that should receive it (so perhaps what i really want is a 
 peer-to-peer model?). It occurs to me that i can achieve this effect by 
 establishing a distinct topic for each of the n receiving tasks, and have 
 the reciting task listening on its very own topic.
 
 Will this approach scale? Is it reasonably efficient? May i assume that a 
 message M published for topic T is only transmitted across the network to 
 those nodes that have ​expressed interest in topic T (which in my case would 
 be just one node)? 
 
 If not, can i achieve what i want by somehow assigning each receiving task 
 to a separate cluster group?
 
 Many thanks,
 
 Jonathon 
 

Client reconnect problems

[Mario Ivankovits]

Hi list!

I started to use Ignite (1.1.0-incubating) for a network message bus where I 
have a server node and several client nodes using the TcpClientDiscoverySpi.

On first startup, it does not matter in which order I start my Ignite sever or 
client. Each other waits as expected to have the grid running. But if I kill 
the server, the client fails to reconnect to it.

I have a simple test for this. 
Just start the class TestIgniteClient with program parameter „s“ and again with 
„c“ so you have two instances running. Then you should see the message „I am 
here“ flowing from the server to the client.
Once you kill the server process („s“) and restart it, you will get a lot of 
exception on the client and it will not reconnect.

Is there something I do wrong, or should I file a JIRA about that?

Thanks for your help.


===exception==
SCHWERWIEGEND: Failed to refresh partition map 
[oldest=--0001--0001, rmts=[], 
loc=445a949f-dd26-4998-8c1c-4faa05ceed81]
class org.apache.ignite.IgniteCheckedException: Failed to send message (node 
may have left the grid or TCP connection cannot be established due to firewall 
issues) [node=TcpDiscoveryNode [id=--0001--0001, 
addrs=[10.0.0.102, 0:0:0:0:0:0:0:1, 127.0.0.1], sockAddrs=[/10.0.0.102:8025, 
/0:0:0:0:0:0:0:1:8025, /127.0.0.1:8025], discPort=8025, order=1, intOrder=1, 
loc=false, ver=1.1.0#20150520-sha1:6da491f4, isClient=false], 
topic=TOPIC_CACHE, msg=GridDhtPartitionsSingleMessage 
[parts={-2100569601=GridDhtPartitionMap 
[nodeId=445a949f-dd26-4998-8c1c-4faa05ceed81, updateSeq=4, size=0], 
689859866=GridDhtPartitionMap [nodeId=445a949f-dd26-4998-8c1c-4faa05ceed81, 
updateSeq=4, size=0], 1325947219=GridDhtPartitionMap 
[nodeId=445a949f-dd26-4998-8c1c-4faa05ceed81, updateSeq=4, size=0]}, 
super=GridDhtPartitionsAbstractMessage [exchId=null, lastVer=GridCacheVersion 
[topVer=0, nodeOrderDrId=0, globalTime=0, order=1434179630276], 
super=GridCacheMessage [msgId=4, depInfo=null, err=null, skipPrepare=false]]], 
policy=SYSTEM_POOL]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:952)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1016)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:389)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.sendLocalPartitions(GridCachePartitionExchangeManager.java:664)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.refreshPartitions(GridCachePartitionExchangeManager.java:579)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.refreshPartitions(GridCachePartitionExchangeManager.java:603)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1700(GridCachePartitionExchangeManager.java:57)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:967)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send 
message to remote node: TcpDiscoveryNode 
[id=--0001--0001, addrs=[10.0.0.102, 0:0:0:0:0:0:0:1, 
127.0.0.1], sockAddrs=[/10.0.0.102:8025, /0:0:0:0:0:0:0:1:8025, 
/127.0.0.1:8025], discPort=8025, order=1, intOrder=1, loc=false, 
ver=1.1.0#20150520-sha1:6da491f4, isClient=false]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1574)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:138)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:949)
... 9 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to connect to 
node (is node still alive?). Make sure that each GridComputeTask and 
GridCacheTransaction has a timeout set in order to prevent parties from waiting 
forever in case of network issues [nodeId=--0001--0001, 
addrs=[/0:0:0:0:0:0:0:1:47100, /127.0.0.1:47100, /10.0.0.102:47100]]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:1842)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:1671)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1612)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$4000(TcpCommunicationSpi.java:140)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$RecoveryWorker.body(TcpCommunicationSpi.java:2452)
at 

Re: Trouble Enabling Query Indexing

[fluffy]

Val,

never mind, I think that did it. I had to make a couple of other changes in
my environment, but that I think allowed indexing to work again.

I never realized that the Spring XML definition and the java DSL of a Cache
are mutually exclusive? From GridGain I was used to specifying the basics in
Spring XML and then just modifying it in Java when necessary

The documentation says that XMl and Java are mutually exclusive for the
Index MetaData stuff, but in terms of CacheConfiguration, does it pick a
Spring XML configuration over a Java configuration and then ignore Java?

Thanks much




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Trouble-Enabling-Query-Indexing-tp377p490.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.