Implement the Ignite LifeCycleBean [1] and stop the JVM on receiving the
event [2]
[1]:
https://ignite.apache.org/releases/mobile/org/apache/ignite/lifecycle/LifecycleBean.html
[2]:
https://ignite.apache.org/releases/mobile/org/apache/ignite/lifecycle/LifecycleEventType.html#AFTER_NODE_STOP
-- Ka
Bumping up this thread. I've a similar requirement. What is the outcome of
this thread ?
My cache re-balance mode is Synchronous. How to know the cache re-balance
is completed ?
-- Kamal
On Fri, Jun 24, 2016 at 2:25 PM, Vladislav Pyatkov
wrote:
> Hello, Andrew.
>
> You are right.
>
> I have cr
Understood. Thanks!
Regards
Kamal C
On Tue, Aug 16, 2016 at 3:47 PM, Taras Ledkov wrote:
> Hi,
>
> Affinity job doesn't block rebalance. We reserve partition to prevent
> remove data from the node while job is running.
> So, topology is changed, partitions are moved to an
eadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[?:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [?:1.7.0_40]
Val,
I've posted the same issue in the Cassandra forums
http://www.mail-archive.com/user@cassandra.apache.org/msg48370.html
Regards,
Kamal C
On Sat, Aug 13, 2016 at
[1]: https://gist.github.com/Kamal15/0a4066de152b8ebc856fc264f7b4037d
Regards,
Kamal C
On Sat, Aug 13, 2016 at 12:15 AM, vkulichenko wrote:
> Note that this was changed recently [1] and the change was not released in
> 1.7. Kamal, can you try the nightly build [2] and check if it works as yo
calAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
[apache-cassandra-3.7.jar:3.7]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[apache-cassandra-3.7.jar:3.7]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]
Is anyone faced similar exceptions ? How to resolve it ?
Regards,
Kamal C
ke to throw `ComputeJobFailOverException` if interrupted.
Regards,
Kamal C
After enabling the Atomic backups to "1". It worked. Thanks Ross!
Regards,
Kamal
On Thu, Aug 4, 2016 at 2:03 PM, ross.anderson
wrote:
> Hi Kamal, I think I found something similar yesterday.
>
> In your Ignite configuration, try setting Atomic backups to 1 (it defaults
> to 0, so when the node
roduce the exception and the code in a gist[1]
[1]: https://gist.github.com/Kamal15/f83e0d17c4a21caf15ec4486406b2c12
Regards,
Kamal C
Val,
To reproduce the exception, I've made a simple example. Actually, I'm
creating state objects
in the Service#init block.
I've updated my approach. It doesn't makes sense to make initialization as
asynchronous.
Regards,
Kamal C
On Thu, Aug 4, 2016 at 6:21 AM, vkuliche
Val.
In real use-case, all the initialization are done in the *init* block. Due
to the above
mentioned behavior, I want to deploy the services locally / manually after
initialization.
The suggested approach to deploy a service only in the local node is not
working.
Do you have any alternate solut
Have anyone looked at this gist [1]. I'm facing issues with rolling startup.
[1]: https://gist.github.com/Kamal15/0f4175fdcfd2c4ef909150be5d896c56
On Sat, Jul 30, 2016 at 6:41 PM, Kamal C wrote:
> Thanks for providing the answers Val!
>
> A. Actually, I forgot that Ignite s
test, IgniteService starts to process the request before it gets
initialized
which may leads to incorrect results. I've listed the steps to reproduce the
issue and exception thrown in a gist[1]
[1] https://gist.github.com/Kamal15/0f4175fdcfd2c4ef909150be5d896c56
Regards,
Kamal C
On Sat, J
loyed or not.
Two instances of ServiceX is created in Node 2. How to overcome that?
Regards,
Kamal C
On Wed, Apr 13, 2016 at 9:40 AM, vkulichenko
wrote:
> This is already fixed in master. You can build from there and try it out,
> should work without implementation classes in the clien
Apologies, for the spam! Found it.
On Thu, Jul 21, 2016 at 10:15 AM, Kamal C wrote:
> Could someone please explain how to configure *nodeFilter* in the spring
> cache configuration file ?
>
> Regards,
> Kamal C
>
> On Wed, Apr 20, 2016 at 12:27 PM, Alexey
Could someone please explain how to configure *nodeFilter* in the spring
cache configuration file ?
Regards,
Kamal C
On Wed, Apr 20, 2016 at 12:27 PM, Alexey Kuznetsov
wrote:
> Kamal, I created an issue for this, you can track in JIRA.
>
> https://issues.apache.org/jira/browse/IG
It's clear now. Thanks for the information Igor.
Regards,
Kamal C
On Fri, Jul 15, 2016 at 9:32 PM, Igor Rudyak wrote:
> Hi Kamal,
>
> Partitions in Cassandra are controlled by the partition key you selected.
> Using Ignite-Cassandra module you have two options to specify Cass
able.
Regards,
Kamal C
On Fri, Jul 15, 2016 at 5:13 AM, Igor Rudyak wrote:
> Hi Kamal,
>
> Ignite Cassandra module takes into account AffinityFunction when
> persisting values into Cassandra(
> https://apacheignite.readme.io/docs/overview). Thus key/values having the
> sa
t;
> Please create a ticket in JIRA for that and share a link to it over there.
> Hope that someone from the community will pick it up and implement. If
> you’re interested in this kind of contribution then it would be perfect.
>
> —
> Denis
>
> On Jul 11, 2016, at 3:05 PM,
Val,
When a new node joins the cluster, should I have to call loadCache() or
localLoadCache() method ?
>From docs,
1. loadCache() - executes localLoadCache() on all the nodes
2. localLoadCache() - will trigger data loading only in the local node.
--Kamal
On Thu, Jul 14, 2016 at 4:12 AM, vkulic
Hi,
Can anyone add Cassandra CacheStore example in the examples[1] like
JDBC CacheStore example?
It will be useful to configure and test the feature quickly.
[1]:
https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store
--Kamal
he cluster node on which the service was deployed crashes or
> stops, Ignite will automatically redeploy it on another node. [1]
>
> [1]: https://apacheignite.readme.io/docs/cluster-singletons
>
> On Mon, Jul 11, 2016 at 7:48 AM, Kamal C wrote:
>
>> Sorry for polluting the mailing
Sorry for polluting the mailing list.
Ignition.stop(false); // internally stops / cancels the local Ignite
service.
Can anyone answer for the 2nd question?
--Kamal
On Mon, Jul 11, 2016 at 10:00 AM, Kamal C wrote:
> Vladislav,
>
> I've applied your suggestion. Still, Ignite clos
rp)
> for local node group.
>
>
> *Ignition.ignite().services(Ignition.ignite().cluster().localNode()).cancel(serviceName);*
>
> On Fri, Jul 8, 2016 at 9:48 AM, Kamal C wrote:
>
>> Hi,
>>
>> I have a 3 node Ignite cluster and deployed a service using Node
>
Hi,
I have a 3 node Ignite cluster and deployed a service using Node
Singleton approach. The service started to run in all the 3 nodes.
Whenever a node stopped, the below line gets called as I'm doing resource
cleanups inside *IgniteService.cancel(ServiceContext context)* method.
*Ignition.i
ite.readme.io/docs/jvm-and-system-tuning
>
> —
> Denis
>
> On Jun 30, 2016, at 2:18 PM, Kamal C wrote:
>
> Hi,
>
> In my setup, sometimes due to network problems local node gets
> segmented and stopped.
> How to tell Ignite to retry continuously to connect with
, isClient=false]
Regards,
Kamal C
ted for NPE you got when were using a wrong key
> https://issues.apache.org/jira/browse/IGNITE-3263
>
> —
> Denis
>
> On Jun 7, 2016, at 7:40 AM, Kamal C wrote:
>
> Thanks for your response Vladislav.
>
> Both ScanQuery and Iterator traverses the whole cache to find t
Thanks for your response Vladislav.
Both ScanQuery and Iterator traverses the whole cache to find the value.
It may not be suitable in my environment as there can be huge number of
hits.
I understand that for fast retrieval `key-to-partition` mapping is done.
But, In AffinityKey documentation, it
ns-logging-1.1.1.jar
b. ignite-spring-1.6.0.jar
c. spring-aop-4.1.0.RELEASE.jar
d. spring-beans-4.1.0.RELEASE.jar
e. spring-context-4.1.0.RELEASE.jar
f. spring-core-4.1.0.RELEASE.jar
g. spring-expression-4.1.0.RELEASE.jar
h. spring-jdbc-4.1.0.RELEASE.jar
i. spring-tx-4.1.0.RELEASE.jar
Regards,
Kamal C
Hi,
In the CacheJdbcPersonStore example[1], why *IgniteDataStreamer* is
never used while loading the bulk elements from the persistent store.
What is the purpose of using IgniteBiInClosure in the example ?
[1]
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ign
Thanks Denis!
On Wed, May 4, 2016 at 5:55 PM, Denis Magda wrote:
> Yes, it does. But it’s available as a part of paid enterprise version
> delivered by GridGain. It’s not a part of Apache Ignite.
>
> —
> Denis
>
> On May 4, 2016, at 3:12 PM, Kamal C wrote:
>
> Deni
disk.
> You should implement it on your own or use the one that is provided by
> other vendors (i.e. GridGain delivers Local Store [1] as a part of it
> enterprise product built on top of Ignite).
>
> [1] https://gridgain.readme.io/docs/local-recoverable-store
>
> —
> Denis
>
Hi,
I have a requirement in which state of the caches should be preserved
during application restart.
I've gone through the [1] link. But, I don't want to store my contents
in the database. How to store the contents of cache in the disk ?
[1] https://apacheignite.readme.io/docs/persistent-sto
Thanks Vladimir!
On Wed, Apr 27, 2016 at 2:31 PM, Vladimir Ozerov
wrote:
> Hi,
>
> There should not be any problems with config like this because all
> Organization entries will be located on all nodes in the cluster.
>
> Vladimir.
>
> On Wed, Apr 27, 2016 at 9:47 AM, K
Ok val.
On Wed, Apr 27, 2016 at 3:19 AM, vkulichenko
wrote:
> Hi Kamal,
>
> If ignite-log4j module is enabled, Log4JLogger is set into configuration
> automatically. This is actually done because we enable this module
> automatically in the binary build.
>
> ignite-slf4j is always optional, so y
What do you mean by cache configuration?
If I go with the below configuration, will it create any problem ?
Person cache - Partitioned, Atomic Mode
Organization / Company cache - Replicated, Transactional Mode
--Kamal
On Wed, Apr 27, 2016 at 10:46 AM, Alexey Goncharuk <
Hi all,
In the example provided for affinity collocation [1], how the keys
of different caches gets collocate together ?
Say, there are two caches:
1. Person cache
2. Organization cache
While inserting the elements into Person cache, I've to use either the
annotation *AffinityKeyMapped *or*
Val,
How log4j enabled automatically after adding the dependency?
Shouldn't we need to set the grid logger IgniteConfiguration#setGridLogger?
And, why slf4j logger is not enabled by default?
--Kamal
On 26-Apr-2016 4:10 AM, "vkulichenko" wrote:
> Hi,
>
> Can you please properly subscribe to th
Binti,
Have you enabled log4j logger in Ignite Configuration ?
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setGridLogger(new Log4JLogger());
--Kamal
On Thu, Apr 21, 2016 at 12:38 AM, vkulichenko wrote:
> Binti,
>
> This doesn't depend on whether it's a client or server. Do you ha
You could try web console
> https://ignite.apache.org/addons.html#web-console
> It will generate XML and Java code for you.
>
> On Mon, Apr 18, 2016 at 8:19 PM, Kamal C wrote:
>
>> Hi,
>>
>> Ignite can be configured either through IgniteConfiguration or by
>&
Hi,
Ignite can be configured either through IgniteConfiguration or by
passing bean XML file.
In XML file approach, typing the property keys seems to be error-prone.
e.g.
*...
*
**
How to auto-generate the configuration file using the bean object ?
[or]
Is any sample file availabl
f/ignite/ignite-server.xml");
After adding the environmental variable, the issue resolved.
--Kamal
On Mon, Apr 18, 2016 at 10:55 AM, Kamal C wrote:
> Alexei,
>
> Thanks for your response!
>
> I've used slf4j to re-direct the logs
>
> Ign
gger(U.resolveIgniteUrl("log4j2.xml",
> false)));
> Ignition.start(cfg);
>
> The key point here is to tell Ignite to use Log4J2 implementation for
> logging.
> Make sure you have log4j2.xml on your classpath.
>
>
> 2016-04-16 15:40 GMT+03:00 Kamal C :
>
>>
Hi
I'm not able to re-direct the Ignite logs to log4j2. I tried it by
adding the optional `ignite-log4j2` directory to the class path and added
the log4j2.xml. Still, the logs thrown to the console.
Can anyone tell how to re-direct the logs?
--Kamal
Thanks for your quick response Val!
I'll test throughly and update here.
--Kamal
On Thu, Apr 14, 2016 at 11:57 PM, vkulichenko wrote:
> Kamal,
>
> I'm not sure I understood what you're trying to achieve. When you use cache
> API, all affinity mappings are done automatically, so you don't need
Hi all,
I've a cluster of 2 ignite server nodes + 1 client node (non-ignite).
I've collocated the data resides in ignite cache based on affinity key.
e.g.
Server 1 - contains all the data related to the affinity key (A, C, E)
Server 2 - contains all the data related to the affinity key (B, D,
Val,
Can you explain with use-case when to use Binary, Optimized, GridOptimized
and JDK Marshallers ?
--Kamal
On Tue, Apr 5, 2016 at 3:41 AM, edwardkblk
wrote:
> Yes, it works with OptimizedMarshaller. Thank you.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6
Ravi,
Check whether you have multiple versions of hibernate in your class path.
--Kamal
On 13-Apr-2016 4:42 AM, "vkulichenko" wrote:
> Ravi,
>
> You should double-check your classpath. This is the same or very similar
> issue, which is not about Ignite, but about your project structure.
>
> -Va
Yes. I took a similar approach except I had state variables in my services.
I'll update it.
In RMI mode, clients don't need to have the implementation classes as it
works on the stub. In Ignite, client node expects the implementation
classes to present on the class path.
On 13-Apr-2016 7:52 AM, "v
Thanks for your response Val.
Is service grid can be seen as a replacement for RMI?
My existing legacy code provides RMI support for the external
system to access it. I have a requirement to distribute the
application by running it in more than one node. I'm looking for
a way to provide the API S
run on the same host
> (Inter-process communication). This lets to avoid transferring data over a
> network interface.
>
> So this lib is optional and it’s being rebuilt quite rare.
>
> —
> Denis
>
> On Apr 12, 2016, at 12:12 PM, Kamal C wrote:
>
> Hi all,
>
>
Hi all,
In the http://apacheignite.gridgain.org/v1.2/docs/maven-setup page,
it's stated that ignite-core-1.5.0.final.jar is the only mandatory. All the
other jars are optional.
By default, in build ignite-core-1.5.0.final.jar, cache-api-1.0.0.jar,
ignite-shmem-1.0.0.jar, ignite-spring/* and i
Hi all,
While I'm using the Ignite Service Grid, I found a weird behavior in
which values of local variables are getting overridden.
I have two ignite nodes and I deployed the service in node singleton
approach. When the second node comes up and joins the cluster, it's local
variable values a
36 PM, Pavel Tupitsyn
wrote:
> Kamal,
>
> In replicated mode all data is already on every node, so there is no need
> to rebalance.
> http://apacheignite.gridgain.org/docs/cache-modes
>
> On Tue, Mar 1, 2016 at 6:58 PM, Kamal C wrote:
>
>> Vladimir,
>>
>&g
You can access the data as primary node is up.
When cache mode is set to partitioned, each node acts as primary node for
some partitions and as backup node for other partitions.
Refer https://apacheignite.readme.io/docs/cache-modes#partitioned-mode
On Tue, Mar 1, 2016 at 8:26 PM, 上帝已死 <527901...
ot; wrote:
> Kamal,
>
> You should enable these event type in configuration. See
> IgniteConfiguration.setIncludeEventTypes(int
> ...) method.
>
> Vladimir.
>
> On Mon, Feb 29, 2016 at 12:00 PM, Kamal C wrote:
>
>> Hi,
>>
>> I have a replicat
Partitioned cache default backup is 0. So, you lose the data when a node
goes down.
To not to lose data, configure the backup >= 1.
On 01-Mar-2016 8:03 PM, "上帝已死" <527901...@qq.com> wrote:
> Do not be a part of the cache cannot be obtained?
>
>
>
> --
> View this message in context:
> http://apac
Hi,
I have a replicated ignite cache with 3 nodes. I want to listen for
data rebalance notifications in all the nodes whenever a new node joined /
left the cluster.
Using Ignite Events, I'd tried to register for cache re-balance
notifications. But, I'm unable to receive any notifications.
Ca
59 matches
Mail list logo
