I think perhaps our test produres are Inconsistent.
My test produre as following:
Test RemoteFilterFactory without parameter.
1. In host 192.168.137.6, run ignite.sh -i(choose the example-cache.xml)
2. In host 192.168.137.31, run jar -cp continueclient.jar
Hi Igor,
thanks for your reply. I've both tried building ignite from source and
removing CassandraAdminCredentials class specifying username and password
in the bean's properties. Anyway, I cannot get it work. Ignite still cannot
find the required classes, this time
Hi,
Yes, you're right, this is a cache that holds data for distributed
datastructures, and IgniteQueue as well. Is it possible that you add items
to queue faster than poll?
TxCommittedVersionsSize and TxRolledbackVersionsSize are common for all
caches and just store versions of finished
I solved the problem by myself.
Is it ignite's bug? Though I have set the following variable in .bashrc,
ignite still can't get the related hadoop jar.
*export IGNITE_LIBS=$IGNITE_LIBS:"$IGNITE_HOME/libs/*":$HADOOP_CLASSPATH*
Now I have solved this problem by copying related hadoop jars
Done, any idea when this bug might be resolved? It's kind of a deal breaker
for our microservice architecture.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Throwing-and-catching-user-exceptions-in-Ignite-Services-tp9143p9183.html
Sent from the Apache Ignite
Hi,
Thanks for the reproducer, but it works for both tests. I think your issue
entails in too large timeouts, for example, you set 5 min timeout for join,
so it may take too long to connect. Is there any reason for such decision?
--
View this message in context:
Hi, I'm new to Ignite and I'm looking for some basic getting started advice
for an architecture on the scenario below.
My use case is; I want to load data from 3 SQL Server databases into an
Ignite data grid and be able to do distributed SQL queries across the 3 sets
of data from client apps.
The book is in the web site: https://leanpub.com/ignite
Bob
---
Confidentiality Notice: The information contained in this e-mail and any
accompanying attachment(s)
is intended only for the