unsubscribe

2017-10-19 Thread Anand Kumar Sankaran

Re: Simulating network outage in tests

2016-08-30 Thread Anand Kumar Sankaran
Thanks again, Val. On 8/29/16, 3:48 PM, "vkulichenko" wrote: Hi Anand, I recommend you to ask on the dev@ list about this. Most likely you will get better guidance there. -Val -- View this message in context: https://urldefense.proofpoint.com/v2

Re: SPI has already been started (always create new configuration instance for each starting Ignite instances) Error

2016-08-29 Thread Anand Kumar Sankaran
Hi Val Got it. Thanks. On 8/29/16, 1:24 PM, "vkulichenko" wrote: Anand, Copy constructor does not make a deep copy, so instances of SPIs is the same. This is by design, because I'm not sure this is even possible in general case (SPIs can be provided by users and in this c

Re: failureDetectionTimeout tuning

2016-08-29 Thread Anand Kumar Sankaran
http://apacheignite.gridgain.org/v1.7/docs/cluster-config#failure-detection-timeout Most likely a hardware or network issue (or your node could be very busy as well). On 8/29/16, 8:54 AM, "bintisepaha" wrote: We see this message logged in our logs from time to time. Is this a potential

Simulating network outage in tests

2016-08-29 Thread Anand Kumar Sankaran
Hi I am implementing a segmentation resolver to handle split brain scenarios. I need to simulate network outages to unit test this behavior. Any suggestions on how to simulate this? I see that the TcpDiscoverySpi has timeouts, is there a way to mock TcpDiscoverySpi to think that there is a n

Re: SPI has already been started (always create new configuration instance for each starting Ignite instances) Error

2016-08-29 Thread Anand Kumar Sankaran
, using Spring scope bean attribute (if youuse Spring configuration) like this: On Sun, Aug 28, 2016 at 7:19 PM, Anand Kumar Sankaran mailto:anand.sanka...@workday.com>> wrote: Hi I am coding a segmentation resolver that’s restarting Ignite in the case of a Segmentation Event.

SPI has already been started (always create new configuration instance for each starting Ignite instances) Error

2016-08-28 Thread Anand Kumar Sankaran
Hi I am coding a segmentation resolver that’s restarting Ignite in the case of a Segmentation Event. I copy the current Ignite Configuration and use it to start a new Ignite. this.ignite.close(); final org.apache.ignite.configuration.IgniteConfiguration copy = new org.apache.ignite.configura

cluster node attribute based authorization

2016-06-06 Thread Anand Kumar Sankaran
All I implemented a ClusterNode.userAttributes() based authorization mechanism. I used a JWT Token to establish trust (passed via the userAttribute). This works fine. The problem I have is that the JWT Token expires shortly after initial use. Now, if the node leaves the cluster and joins it

Re: Custom GridSecurityProcessor plugin question

2016-05-16 Thread Anand Kumar Sankaran
enticator is set and places where DiscoverySpiNodeAuthenticator.authenticateNode is used and share the results with us. — Denis On May 16, 2016, at 12:01 AM, Anand Kumar Sankaran mailto:anand.sanka...@workday.com>> wrote: I went past this. Turns out if everything is ok, validateNode ha

Re: Custom GridSecurityProcessor plugin question

2016-05-15 Thread Anand Kumar Sankaran
: Anand Kumar Sankaran Reply-To: "user@ignite.apache.org" Date: Friday, May 13, 2016 at 10:22 PM To: "user@ignite.apache.org" Subject: Custom GridSecurityProcessor plugin question Hi I following the instructions in http://smartkey.co.uk/development/securing-an-apache-i

Custom GridSecurityProcessor plugin question

2016-05-13 Thread Anand Kumar Sankaran
Hi I following the instructions in http://smartkey.co.uk/development/securing-an-apache-ignite-cluster/ and implemented a custom GridSecurityProcessor plugin. I got Ignite to recognize the custom provider and the provider is returning my custom GridSecurityProcessor like this: @Nullable @Ove