We will try this and get back to you. Does it mean that usually the node
recovers from it, if it were due to GC? Would we also have to remove
joinTimeout?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/failureDetectionTimeout-tuning-tp7374p7473.html
Sent from
Also, it was stuck like this for hours.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/IgniteCompute-broadcast-stuck-tp7255p7472.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Val, this dump was from the client node which I sent on the original email.
the zipped up dumps were from all the server nodes that participate in the
distributed cache.
anyways, changing it to run() fixed the issue. But we never understand the
root cause of the hanging, its always that the
IgniteCluster API provides startNodes() method that allows to do this
programmatically on the remote machines (it uses SSH connection).
Can you please give me full examples? or a link for this? thanks again
--
View this message in context:
but from yarn contains, i can't find any errors.
sometimes the yarn am ignite was shutdown down(and sometimes restart a new
AM, i don't know why)?
--
View this message in context:
Hi,
We have no global DB behind the grid. We marked our Store with
@CacheLocalStore annotation. But Ignite does not move stored entries when
rebalancig partitions. So we should have more control of partition
assignment to be able to change the assignment manually after storage
synchronization.
Hi,
Your Maven tries to access a repo which is not provided by Ignite build. I
guess it's somewhere in your Maven settings.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Fail-to-compile-apache-ignite-1-7-0-tp7458p7467.html
Sent from the Apache Ignite
Hi Scott,
How many caches are you going to have? Basically, the recommended way is to
have a cache per data type - this makes life easier in most cases. But keep
in mind that each cache will require around 20MB of *heap* memory per node
for its internals. So hundreds of caches can introduce high
Hi,
You can use CacheConfiguration.setNodeFilter(..) property to specify where
the particular cache will be deployed. If not set, it will be deployed on
all server nodes.
-Val
--
View this message in context:
Hi,
Can you please clarify why would you need this?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Reassign-partitions-tp7461p7464.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
You can try using Ignite C++ client. If you describe your use-case some
more I'll be able to provide you with some more specific advice.
What for are you using Ignite for and why do you need to make JNI calls?
Best Regards,
Igor
On Thu, Sep 1, 2016 at 10:21 PM, Caio Nishibe
Hi, I'm trying to implement a biometric identification system using Ignite.
The first version was not good enough because in my job, for each cache
entry, I was calling a C++ method through JNI to process that entry and the
time to transfer all the data from Java to C++ was killing the performance
The AffinityFunction.assignPartitions method is called when a server node
joins or left the topology. Is there a way to reassign partitions for a
cache without changing the topology (e.g. to move a backup partition from
one node to another)?
--
View this message in context:
Hi, I am trying to configure ignite that cache A data will be on all nodes
and cache B data on some subset of nodes. In other words for cache A ignite
will be in server mode for all nodes and for cache B ignite will in server
mode for some nodes and in client mode for others.
I think it could be
We will be employing a data grid off heap, replication implementation. We
are estimating with the 30% index cache alllowance that we will need 7 gig
of ram per ignite server node there will be two. We have two options.
Create many smaller caches or put everything in a collection using one
Hi,
This is first time I touch apache-ignite. When I try to comply it as by
instractions from https://apacheignite.readme.io/docs/getting-started
(without LGPL dependencies)
I am getting following error:
[INFO] ignite-jta . FAILURE [ 7.287
s]
...
[ERROR]
Hello,
If you specify type on IndexTypes property[1] SQL will be work, but without
indexes.
The resume field do not be visible from SQL.
Text query do not work together with SQL.
[1]:
https://apacheignite.readme.io/docs/sql-queries#configuring-sql-indexes-by-annotations
On Thu, Sep 1, 2016 at
If I have the classic POJO
class Person{
@QuerySqlField
private String genotype;
@QueryTextField
private String resume;
}
How do I query "where genotype = 'male' and resume like '%Hello%'" so that
it hits the lucene index?
--
View this message in context:
Hello,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
The reason of segmentation in most cases is a delays:
i was wrong.
i solved with cross-cache-query functions
-sy
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/jdbc-connection-URL-with-more-than-1-cache-tp7446p7451.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hello,
You can subscribe to event[1] and handle EVT_CACHE_REBALANCE_STARTED
and EVT_CACHE_REBALANCE_STOPPED events on client node.
[1]: https://apacheignite.readme.io/docs/events
On Thu, Sep 1, 2016 at 5:17 AM, bluehu wrote:
> for example, C is a client, X and Y are
Fix version suggest it is in 1.8 which is yet to be released. Is there any
interim solution meanwhile.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Can-not-find-schema-for-object-with-compact-footer-tp7406p7448.html
Sent from the Apache Ignite Users mailing
hi Alexey,
Thanks for logging the issue.
But still I am facing the same issue:
public class CacheConfig {
/**
* Create JDBC type for inventory_orders.
*
* @param cacheName Cache name.
* @return Configured JDBC type.
*/
private static JdbcType
hi,
i'm learing and testing ignite for feasibility. during test i met the
following problem.
when i define jdbc connection url with 2 params (2 caches) as follows, i got
errors at executeQuery.
however if i defie just 1 cache, it works fine.
try {
24 matches
Mail list logo