Hi Rishi,
Yes, you can do this by implementing your own AffinityFunction and then add
it to CacheConfiguration with CacheConfigucation.setAffinity(..) method.
On Fri, Dec 16, 2016 at 12:34 AM, rishireddy.bokka <
rishireddy.bo...@gmail.com> wrote:
> Hi Ignite Team,
> I recently started using Igni
Hi,
This could be if in client discovery configuration only one server node
address set, that is restarted. In this case clients are unsuccessful in
connecting to stopped node and are shutting down.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObjectExc
Dmitry,
You can to try execute build() for the specific object:
BinaryObject operation = ignite.binary()
.builder("SomeObject")
.setField("FIELD", value)
.build();
(or something similar for java object)
after the client reconnected. In
In case the performance of a fix rate is appropriate for you I think your
solution make sense because it is very simple and robust.
Also, you can use IgniteScheduler (
https://ignite.apache.org/releases/mobile/org/apache/ignite/IgniteScheduler.html)
instead of spring scheduler.
On Wed, Dec 14, 20
Hi Anil,
Right, you get stopping the node by the cause of segmentation.
Call chain:
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.DiscoveryWorker#onSegmentation
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager#stopNode
org.apache.ignite.Ignition#stop(java.l
Vladislav,
Actually I don't know the exact object that causes the deserialization
problem. For me it looks like a remote call fails.
If I have to use some workaround, I prefer switching off the compact
footers.
Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabbl
Hi,
I have an application which uses apache ignite cache in an embedded mode. On
each GC cycle, I am seeing lot of memory getting retained. Cache has around 10K
entries and each entry is an object containing a map of 500 entries. The key
and value in the map within an object is string of less t
I think, simplest AffinityKeyMapper[1] will be sufficient:
public Object affinityKey(Object key) {
if (key instanceof Integer)
return ((Integer)key) % 2;
}
and configuration like this:
...
[1]: org.apache.ignite.cache.affinity.AffinityKeyMapper
Hi
As I understand you have many short-lived Maps as values in cache.
Yes, in your case, you can get a lot of garbage due to Map will be
marshal\unmarshal along with each of its content at every cache entry
access.
On Fri, Dec 16, 2016 at 4:26 PM, Pradeep Badiger
wrote:
> Hi,
>
>
>
> I have an
Hi!
In your case key and value classes are not deployed on server nodes. You
need to deploy classes on all nodes or to use IgniteCache.withKeepBinary.
Also you don't need to implement visitUsingMapKeysToNodes methods. You can
use IgniteCompute#affinityRun or IgniteCompute#affinityCall methods. The
Hi Andrey,
Thanks for your response. Is there a way I can disable it or reduce it? Do I
need to use BinaryObject?
Thanks,
Pradeep V.B.
From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
Sent: Friday, December 16, 2016 9:41 AM
To: user@ignite.apache.org
Subject: Re: Binary Marshalling is
Thanks for the reply Nikolai. I am new to Ignite, So could you please tell me
how to deploy classes on all nodes and about IgniteCache.withKeepBinary.
Thanks,
Rishi
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Issue-while-using-Affinity-function-for-mapping-
Below is my configuration file :
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>
Hi,
Unfortunatelly ignite does not support keepBinary option for Maps [1].
Best way is try to avoid using short-lived Maps.
But you can try to implementation of BinaryObject that implements
Externalizable interface where you will free to choose the way to access
map entries.
For example, such imp
Thanks Andrey.
From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
Sent: Friday, December 16, 2016 11:30 AM
To: user@ignite.apache.org
Subject: Re: Binary Marshalling issue
Hi,
Unfortunatelly ignite does not support keepBinary option for Maps [1].
Best way is try to avoid using short-live
Hi. I have 2 questions regarding Ignite & Cassandra.
I'm using Ignite v1.8
I'm trying to get a very simple example working with read/write through to
c*, but I'm having some difficulty.
First, I'm trying to use the POJO strategy of configuration for both the key
& value persistence with the cla
Hi,
@QuerySqlField is annotation for Ignite SQL [1], it has nothing to do with
Cassandra integration. To specify column name which differs from Java field
name, you should use 'field' tags inside 'valuePersistence', like shown in
the example [2].
[1]
https://apacheignite.readme.io/v1.8/docs/index
Hi Rishi,
You job is executed on a server node, which doesn't have Person class on
classpath. To deploy your code on server side simply create a JAR with
required classes and put it into IGNITE_HOME/libs folder before starting the
nodes.
Another way to overcome the issue is utilize BinaryObject A
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-can-I-save-the-job-result-which-was-ran-on-server-which-lost-the-connection-tp9462p9610.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
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.
vahan wrote
> Imagine we have cluster of nodes with replicate
Can you show your configuration?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-connect-tp9556p9613.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
This happens because Ignite adds predefined _key and _val fields to every
table. They represent whole key and value objects and deserialize on the
client when you select them. Now they are also selected when you do 'select
*'. This will improved in future, but for now you should avoid doing this
an
Are you sure that all of them are in this map? What is the size of rmtCfgs
map?
Actually this map can be non-empty only on a node which is not fully started
yet. Basically, when a new node joins a topology, it collects the
configuration from all nodes for validation check, does the check and clean
Hi Sam,
I reproduced the issue using your code and created a ticket:
https://issues.apache.org/jira/browse/IGNITE-4450
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9616.html
Sent from the Apache Ignite Users maili
Hi all,
I'm seeking a fuller understanding of how Apache ignite manages datasets,
both for indexes and for the underlying data.
In particular, I'm looking at what practical constraints exist for overall
data size (beyond the obvious 'how much memory do you have?'), and
functional characteristics
Hi,
By a project on GitHub I actually meant that something that I can run right
away and be sure that I do absolutely the same that you do. Basically, a
unit test.
I tried to run your code anyway, but it works fine for me. Attached is the
test I created, please try to run it and check what you're
Hi,
This is not actually 100% true - Cassandra integration supports
@QuerySqlField annotations to create tables and doing mapping between
object fields and table columns.
Kenan, have you tried Cassandra DDL generator
https://apacheignite-mix.readme.io/docs/ddl-generator for your persistence
descr
27 matches
Mail list logo