Re: Looking for information on these methods

wt, you are talking about over here writing the whole security plugin. Looks like the community also need a plugin for security as well. Now it really depends how you want to authenticate the user when a specific operation is performed on a specific cache. I have already started to write the se

Re: What happens during network failure?

-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Service Grid

James, this can be resolved by either putting all the classes which are required by your Service in the lib folder of ignite or enable peer class loading. See [1] for peer class loading [1] peer-class-loading -- Sent fr

Re: Load balancing ignite get requests

Anirudha, also see [1] for built-in load balancing which could be useful [1] AdaptiveLoadProbe -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: keep old cache value than new value

Nice, that might work - thanks Denis -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Service Grid

James, can you show us how you are trying to invoke the services from continuous queries and spring boot as well? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: keep old cache value than new value

Thanks Denis for getting back to me much appreciated. The use case we have is we have millions of data points which is updated by the other teams in separate databases. Whenever this happens we receive a message upon update and it triggers the load cache process in ignite. Until now we did not h

Re: What happens during network failure?

Lokesh, looking at the javadocs of [1] you can subscribe for EVT_NODE_FAILED and EVT_NODE_SEGMENTED events. >From my personal experience SegmentationPolicy.NOOP is required in very rare cases. My approach would be to STOP the node in most of the cases when the segment happens or you can RESTART de

Re: What happens during network failure?

Lokesh, see [1] how node will act when the segmentation will occur. You have to register for EVT_NODE_SEGMENTED events. Ignite plugins contains all this information as well. [1] SegmentationPolicy

Re: keep old cache value than new value

anyone from anyone would be highly appreciated -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: What happens during network failure?

Lokesh, this is a pure split brain scenarios see [1] how you can overcome this problem. [1] Ignite plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

keep old cache value than new value

Hi, Is there any feature in ignite through which I can decide whether to keep the old value or new value in a cache? We have few cases when the update comes from the persistence store we want do not want to update the cache value and want to keep the old one. Thanks, Luqman -- Sent from: http:

Re: how to automatically exit JVM when the node stops?

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite cluster recovery after network partition

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to overcome short-time network problems?

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How many nodes within your ignite cluster

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Timed out waiting for message delivery receipt

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node fails to recover

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: split-brain problem and GridSegmentationProcessor

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite cluster

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local node failure starts cluster-wide procedure

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cluster breaks down on network failure

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Two Ignite Clusters formed after network disturbance

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Behaviour of Apache Ignite instances in case of network isolation

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Segmentation fault (JVM crash) while memory restoring on start with native persistance

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local node SEGMENTED. Data Lost on a Partitioned Cache with backups of 3

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Stopping local node according to configured segmentation policy.

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Stopping local node according to configured segmentation policy.

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Easy way to determine a node has been segmented

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Node failure - Node out of topology (SEGMENTED)

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite node not stopping after segmentation

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Network Segmentation configuarion

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Segmentation policy.

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Segmentation policy configuration

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: RESTART_JVM Segmentation Policy

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Segmentation policy configuration

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cluster segmentation

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: network segmentation

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Network Segmentation

See [1] for free network segmentation plugin [1] https://github.com/luqmanahmad/ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Free Network Segmentation (aka split brain) plugin available

Thanks Dmitry. I have also added the initial version of TcpIpSegmentation - Still not sure about it but hopefully it should fill the purpose - So far I have tested it with postgres, sql server and tomcat -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: The Apache Ignite Book

Dear Shamim, I have recently developed a network segmentation plugin for Apache Ignite project. It would be nice if you can add some stuff related to plugins as well. Please see [1] for more information. [1] Post

Free Network Segmentation (akas split brain) plugin available

[1] ignite-plugins <https://github.com/luqmanahmad/ignite-plugins> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite performance

Hi Val, Thanks for the quick response. I was checking at the network throughput for the redis cache for one minute and the traffic is around 5GB, I can bet it is not optimised, with one farm which has got 10 nodes. Lets say if we have an Ignite cluster of 100 nodes how you would and check the ma

Ignite performance

Hi Igniters, I will try to keep it short as much as I can. We have 8 caches total size is around 6GB to 8GB in redis and the cluster is made up of 1200 nodes. All the operations are read-only. It is a very low latency system where each request doesn't need to be more than 2ms, in very rare cases 3

Peer to peer class loading + deployment modes

Hi there, We have several hundred ignite server nodes and few clients which are loading classes to ignite on demand. Now from time to time we need to redeploy the client with some new changes, which could include changes in the classes which are already loaded to ignite worker nodes through ignite

Re: affinityRun and affinityCall trace

Thanks Val. I thought so but worth giving it a shot :) Luqman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

affinityRun and affinityCall trace

Hi there, Is there any functionality in Ignite or some internal helper class through which we can figure out at any moment of time whether the call was made from affinityRun or affinityCall? Thanks, Luqman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Computation best practices

Hi Christos, Thanks for getting back to me. There is no specific need for it - I am just trying to get my head around for the best practices in that case data nodes does make sense to me to perform the computation. To be honest just a bit confused with the Cluster groups and trying to find a use

Computation best practices

Hi there, Just trying to clarify few bits in my head around data nodes and compute nodes. Let's say we have 10 data nodes which are solely storing the data using affinity collocation and we have 10 compute nodes as well for computing different tasks on the cluster. Now we know that if we want to

Re: split-brain problem and GridSegmentationProcessor

Hi Amit, Correct you have to provide implementation for both. Your custom segmentation will just be validating something and that method of your segmentation resolver will be called inside the implementation of GridSegmentationProcess which can be overriden through your plugin. By default GridOsS

Re: split-brain problem and GridSegmentationProcessor

Hi Amit, Sorry I missed that part that you have to provide the GridSegmentationProcessor implementation for both cases. I did it through the plugin and it worked out of the box - I tested it internally with 3 machines and through docker components as well. See [1] for more information - it will

Re: split-brain problem and GridSegmentationProcessor

Hi Amit, There was no ticket raised for this one so I implemented the solution for the company I worked in the past but dont have a copy with me. Its pretty easy. You can implement your custom segmentation resolvers (depending on your needs) by implementing SegmentationResolver interface. They a

Re: Cron expression in agnite-schedulers

Underneath Ignite uses cron4j to schedule tasks on each node, and looking at your patter it is not compatible with it. You can refer to [1] for more information about the schedule patterns. Anyway your pattern would be something like : 00 18 27 8 * You can also validate on using [2] [1] http://

persistence data store

Hi there, As of 2.0 data can be persisted to SSD I was wondering is there anything which can be used to store the data from it, save it somewhere and then load the data again on some other machine with the same configuration. Thanks, Luqman -- View this message in context: http://apache-ign

Re: docker external libs

Thanks Nikolai for coming back. That's what I am doing and I needed one based on the centos anyway. So had to create one from scratch. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/docker-external-libs-tp16254p16330.html Sent from the Apache Ignite Users mailin

docker external libs

Hi there, In docker deployment can we provide jars from our local system to EXTERNAL_LIBS parameter. Let say we have 10 different jars on our local system how do we provide them to the EXTERNAL_LIBS parameter. Thanks, Luqman -- View this message in context: http://apache-ignite-users.70518.x6

Calling service methods from servlets

Hi there, Let say we have a node singleton service with a method called doSomething() Now if we want to call the service from a servlet we can either inject the service in the servlet directly like: MyService service = ignite.services().serviceProxy("myService", "MyService.class", false); servic

Re: Platform updates

Hi Val, Indeed, it does make sense. Thanks for all your help. - Luqman -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16074.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Platform updates

Thanks Val, that's much more similar to what I was looking for. With respect to [1] when you say "get class to create instance during deployment" do you mean during the server startup time ? [1] If a change is in service, then there is no built in mechanism for now. But you can create a wrapper

Re: Platform updates

Thanks Christos, it is for the application code. For upgrading the ignite version we can schedule the downtime that's why 99.9% :) -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16001.html Sent from the Apache Ignite Users mailing list a

Platform updates

Hi there, Lets say we have a distributed caching system which needs to be up 99.9% time unless we upgrade the version of ignite. Now let say we have found some bugs and needs to be updated on the production cluster without any downtime. How do we approach this scenario in ignite ? If we have a c

Re: benchmark

Thanks everyone that really helped. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/benchmark-tp15246p15939.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

benchmark

Hi, I am a user of ignite since 1.3 and know its much better than hazlecast. Now just need to convince it to the management, and they asked for the benchmarks. They are really keen on hazlecast but I have convinced them on most of the features. Is there a good place where I can find some informat

Re: multiple thread access in segment resolver

ut thread-safety. On Tue, Jul 18, 2017 at 8:51 PM, luqmanahmad <[hidden email] <http:///user/SendEmail.jtp?type=node&node=15080&i=0>> wrote: > Hi Andrey, > > Shouldnt that need to be sync. The reason I am saying because what happens > if two server nodes are starte

Re: multiple thread access in segment resolver

at should be used by GridSegmentationProcessor. > > > > On Tue, Jul 18, 2017 at 1:18 PM, luqmanahmad <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=15071&i=0>> wrote: > >> Hi all, >> >> Let say we have a segmentation re

multiple thread access in segment resolver

Hi all, Let say we have a segmentation resolver named "ApplicationSegmentationResolver" which is checking about the statuses of different applications but it needs to be initialised first time. For example something like this: public ApplicationSegmentationResolver implements SegmentationResolver

Re: database table polling

Val, This might work and adding continuous queries on top, it will fly. So silly I am using loadCache() every where in the new development but couldn't think of it for this one. Luqman On 17 Jul 2017 23:18, "vkulichenko [via Apache Ignite Users]" < ml+s70518n15037...@n6.nabble.com> wrote: Luqma

Re: database table polling

Hi Val, In our legacy system database polling is achieved through a separate table, let say P, in case employee is updated then a new row gets added to P table with the primary key of the employee which is updated and then a background process keeps polling that table for the update. In new syste

database table polling

Hi, We have a legacy system, 15 years old at-least, which we are working on and trying to bring everything inside the grid - but in the meanwhile we have to support our existing system as well. In the legacy system we have a database polling mechanism ( please don't roll your eyes :D ) which is con

Re: Ignite PlugingProvider

Thanks Dmitry that helps alot -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-PlugingProvider-tp14640p14887.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite PlugingProvider

Any help on this class would be highly appreciated org.apache.ignite.plugin.PluginProvider#initExtensions - org.apache.ignite.plugin.ExtensionRegistry -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-PlugingProvider-tp14640p14797.html Sent from the Apache

Re: Queue read/write Store

Matt, Someone already raised this issue before and there was some discussion on the @dev as well. See [1] and [2] for more information. [1] http://apache-ignite-users.70518.x6.nabble.com/Stupide-question-about-Queue-td2557.html

Re: Network Segmentation

Hi Yitzhak, Please see [1] for more information. [1] http://apache-ignite-users.70518.x6.nabble.com/Two-Ignite-Clusters-formed-after-network-disturbance-td3377.html#a3605 T

Ignite PlugingProvider

Hi, I have created my own plugin to override some defaults in the Ignite. For configuration purposes I have got a class xxxPluginConfiguration which is implementing PluginConfiguration. This class has got all the configuration related settings to my plugin. Custom plugin provider I have got a se

split-brain processors

Hi, I understand there is no functionality for split-brain problem in Apache Ignite and is only available from GridGain side in their paid versions. We have implemented our own SegmentationResolvers specific to our needs but just found a catch in the default implementations. I know we can provide