ps -aef |grep Ignite
Use this command and kill Ignite process
On Tue, Aug 7, 2018, 10:39 AM arunkjn wrote:
> Thanks for the suggestion srecon. I will try that out.
>
> But is there any way I can find out and kill that ignite node? I have tried
> deleting the configured wal and persistance
Hello same issue occurred when trying to put object in cache using
cache.put method.after changing put to putAsync issue was solved.
I have read about when you using putAll methode pass sorted collection to
it so it avoid deadlock. So is it true?
On Tue, Jul 17, 2018, 8:22 PM ilya.kasnacheev
try using
ignite.getOrCreateCache("cacheName");
On Thu, Jul 5, 2018 at 3:49 PM, Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:
> Hi,
>
> I have provided the cache configurations on ignite node which is started
> in server mode,but other ignite node which started in client mode does not
>
Hello,
I am getting confused to use Ignite Thin client when I have read following
article about.please let me know is this true
Thin client is up to 50% slower than Ignite client node
Unlike Ignite client node, which knows the latest partition assignments and
gets/puts data right from/to the
An issue occurred when we abnormally stop Spark Java application which
having Ignite client running inside that Spark context.So when we kill
spark application its abnormally stop Ignite client and then when we
restart our application and client try to connect with Ignite cluster then
it getting
I have 3 node cluster with 20+ client and it's running in spark
context.Initially it working fine but randomly get issue whenever new node
i.e. client try to connect with cluster.The cluster getting inoperative.I
have got following logs when its stuck.If I restart any Ignite server
explicitly then
