My cluster can't activate after restart

[yangjiajun]

Hi.

I have a cluster which has 2 data nodes of version 2.6.I use it as a
database with persistence.It stores tens of millions size data and all data
are replicated.I try to recover it after one node failed but I still can not
operate on it by jdbc thin connection. So I try to do a full cluster restart
one node by one.But the cluster block in activate stage.I don't see any
error logs so I have no idea now.

What's wrong with my cluster?
According to my understanding,jdbc thin connection can fail over but it
seems not work in my application.How to correctly use  fail over feature in
jdbc thin connection?
How to restart a cluster in a safe way？

Thanks for your replies. 



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

Re: time series

[Denis Magda]

Ignite can store the whole data set on disk and X% in RAM thanks to the
native persistence. So, you decide how much data you'd like to keep in RAM:
https://ignite.apache.org/arch/memorycentric.html

As per times series, I heard that Ignite is being used for that use case.
However, you might need more. My suggestion is to start and see how it goes.

--
Denis

On Tue, Nov 6, 2018 at 4:05 AM Mikhail  wrote:

> Hi Igniters,
>
>Are there any best practices of storing time series
> data in Ignite? We need it for extremely high load IoT system. Cassandra is
> likely to be an appropriate solution, but slow speed of analytical SQL
> queries are not acceptable for us. We can implement Ignite over Cassandra,
> but we need to access the hole data in Ignite and the cache shouldn't be
> extremely huge (e.g. it should be cache per day).
>We want to have the similar approach, as for example in
> [1]. However, writing such functionality from scratch has a lot of
> pitfalls. Are there any out-of-the-box features for time series data in
> Ignite? Does it sound reasonable to implement rollover pattern in Ignite
> (like in ES)? Or there could be another options?
>
> [1] - https://www.elastic.co/blog/managing-time-based-indices-efficiently
>
> --
> Best Regards,
> Mikhail

Re: How does Ignite provides load balancing?

[Denis Magda]

Hi,

In general, the load is balanced because the data is distributed evenly
across a cluster of machines. For instance, if you utilize key-value calls
then each request goes to a specific node. If you're on SQL then a query
might be broadcasted or sent to a specific node as well.

Overall, yes, Ignite is the right solution if you need to scale and
accelerate performance.

--
Denis

On Tue, Nov 6, 2018 at 6:55 AM Alejandro Santos  wrote:

> Hi all,
>
> I've been reading the Ignite documentation and have some technical
> questions. I need to evaluate massive storage systems for some
> specific application and I would like to understand how ignite works.
>
> My application needs a buffering space that write arbitrary values,
> but then reads on average half of the values at most once. This is a
> random process, and we can't really predict which keys will be read.
>
> Is ignite the right tool for this application? Do you need more
> information?
>
> Thank you,
>
> --
> Alejandro Santos
>

Re: Suppressing reflective serialisation in Ignite

[Denis Magda]

Hi Raymond,

If to believe this page, the reflective serialization converts an object to
the binary format (sort of marked with IBaniralizable interface implicitly):
https://apacheignite-net.readme.io/docs/serialization#section-ignite-reflective-serialization

--
Denis


On Tue, Nov 6, 2018 at 1:01 PM Raymond Wilson 
wrote:

> We are currently converting our use of Ignite reflective serialisation to
> use IBinarizable based serialisation [using Ignite 2.6 with c# client]
>
> What I would like to do is enforce a policy of not using reflective
> serialisation to ensure we have all the bases covered.
>
> Is there a way to do this in Ignite?
>
> Thanks,
> Raymond.
>
>

RE: LRU Evicts Most Recent Entries

[HEWA WIDANA GAMAGE, SUBASH]

Hi everyone,
I think I found how to recreate this. Please find this link

http://apache-ignite-users.70518.x6.nabble.com/LruEvictionPolicy-works-not-properly-with-IgniteCache-removeAll-td2313.html

The issue is reproduced in Ignite v1.9 with same code used in above thread.



-Original Message-
From: HEWA WIDANA GAMAGE, SUBASH [mailto:subash.hewawidanagam...@fmr.com] 
Sent: Thursday, October 04, 2018 10:32 AM
To: user@ignite.apache.org
Subject: RE: LRU Evicts Most Recent Entries

Little correction:
The actual value we have in production for the eviction policy is as 
follows(500MB)

evpl.setMaxMemorySize(524288000);


-Original Message-
From: HEWA WIDANA GAMAGE, SUBASH [mailto:subash.hewawidanagam...@fmr.com] 
Sent: Wednesday, October 03, 2018 10:47 PM
To: user@ignite.apache.org
Subject: RE: LRU Evicts Most Recent Entries

Hi Anton,
Here's the full configuration. 

==This is my grid config

IgniteConfiguration cfg = new IgniteConfiguration();

cfg.setPeerClassLoadingEnabled(false);

cfg.setLifecycleBeans(new LogLifecycleBean());

TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();

TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
Collection addressSet = new HashSet<>();
for (String address : ipList) {
addressSet.add(address);
}
ipFinder.setAddresses(addressSet);

discoverySpi.setJoinTimeout(1);
discoverySpi.setLocalPort(47500);
discoverySpi.setIpFinder(ipFinder);

cfg.setDiscoverySpi(discoverySpi);


And this is the cache config=.
 
CacheConfiguration cc = new CacheConfiguration();

cc.setName("mycache");
cc.setBackups(1);
cc.setCacheMode(CacheMode.PARTITIONED);
cc.setAtomicityMode(CacheAtomicityMode.ATOMIC);

LruEvictionPolicy evpl = new LruEvictionPolicy();
evpl.setMaxMemorySize (1);

cc.setEvictionPolicy(evpl);

cc.setExpiryPolicyFactory(CreatedExpiryPolicy.factoryOf(
new Duration(TimeUnit.SECONDS, 15)));

cc.setStatisticsEnabled(true);

-Original Message-
From: akurbanov [mailto:antkr@gmail.com] 
Sent: Tuesday, October 02, 2018 1:45 PM
To: user@ignite.apache.org
Subject: Re: LRU Evicts Most Recent Entries

This email is from an external source - exercise caution regarding links and 
attachments.

Hello,

Could you please share full Ignite configuration?

Regards,
Anton



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

unsubscribe

[Gautam Saxena]

unsubscribe

Re: Does Apache Ignite support java 8 and hibernate 5.2 NOW?

[daya airody]

Hibernate_5.2.x expects different Interface from Ignite for hibernate entity
cache and second level cache.

ignite-hibernate_5.1 library only supports the interface required by
hibernate 5.1. When is ignite going to support Hibernate 5.2.x.

On spring boot 2.0.1.RELEASE, only java method caching is working. This
issue is a blocker for all applications using Spring boot 2.0.1 and above.

Has anybody worked on supporting Hibernate 5.2.x ?



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

Re: @IgniteInstanceResource not working as expected

[Amir Akhmedov]

Hi,
Can you please show a code snippet? Small reproducer would be even better.

Thanks,
Amir


On Wed, Nov 7, 2018 at 6:20 AM the_palakkaran  wrote:

> Hi,
>
> I have a service from which I create a singleton IgniteQueue. I can get
> ignite instance using @IgniteInstanceResouce inside my service but cannot
> get it inside my singleton queue implementation. for queue creation. Why is
> this so?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

SB2 with Ignite 2.6 Sample Application

[ignite_user2016]

I have a sample application that works on Springboo2 with Ignite 2.6 version,
do let me know if any one more details OR will like to have sample app ? can
post it here on request.

Thanks..



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

Re: Spring upgrade on Ignite

[ignite_user2016]

I fixed the issue with following inclusion in my build gradle - 

configurations.all {
exclude group: "commons-logging", module: "commons-logging"
}

Thanks..
Rishi



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

Spring upgrade on Ignite

[ignite_user2016]

Is there a plan to upgrade spring lib to 5.0 for upcoming release ? 

Currently, Ignite-spring uses Spring 4.3.4 version so if I am running Ignite
with spring boot better to upgrade all the spring libs to 5.1 version.

I run into some weird logging issue since ignite using older version of
spring where it missed out following logs since Ignite using older version
of spring lib.

2018-11-07 09:46:34,098 INFO [main]
org.springframework.boot.web.embedded.undertow.UndertowServletWebServer
Undertow started on port(s) 8080 (http) with context path ''
2018-11-07 09:46:34,099 DEBUG [main]
org.springframework.beans.factory.support.DefaultListableBeanFactory
Returning cached instance of singleton bean 'delegatingApplicationListener'
2018-11-07 09:46:34,099 DEBUG [main]
org.springframework.web.context.support.StandardServletEnvironment Adding
PropertySource 'server.ports' with highest search precedence
2018-11-07 09:46:34,108 INFO [main] demo.SB20CacheApplication Started
SB20CacheApplication in 18.618 seconds (JVM running for 20.738)

The details are as follows - 

On the logging front, Spring Framework 5.0 comes out of the box with Commons
Logging bridge module, named spring-jcl instead of the standard Commons
Logging. Also, this new version will auto detect Log4j 2.x, SLF4J, JUL (
java.util.logging) without any extra bridges.

Thanks..
Rishi



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

@IgniteInstanceResource not working as expected

[the_palakkaran]

Hi,

I have a service from which I create a singleton IgniteQueue. I can get
ignite instance using @IgniteInstanceResouce inside my service but cannot
get it inside my singleton queue implementation. for queue creation. Why is
this so?



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

Re: Unable to load more than 5g data through sqlline

[Павлухин Иван]

Hi Debashis,

Sorry for late answer. How much RAM does your server have?
You configured your data region with 7 gb max size. This size
defines how much RAM could be allocated for the region. If your
server has not enough RAM the OS cannot allocate enough for
Ignite and kills it. With persistence enabled you can store as much
data into Ignite as your disk capacity allows. Try to decrease the data
region max size. I hope this will help.

чт, 1 нояб. 2018 г. в 16:41, debashissinha :

> Also at the same time the ignite node is restarting
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


-- 
Best regards,
Ivan Pavlukhin

persistence when disk full

[wangsan]

I have two nodes (server and persistence true) in different machines.That
node n1 in machine m1,node n2 in machine m2.  
When m1 disk full,Two node n1,n1 will be failed.Not only node n1?
How can I  only make node n1 failed?



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

FIFO Queue with POPs AND PUSHes - like REDIS LIST

[kommrad homer]

Hello , 
I've set up a single node of ignite , on SERVER Mode , running on a VPS of
it's own , so that i can use Bucket4j for rate limiting on some cases.

Now i need to use some List or Array that acts as a FIFO queue . Is there
such structure on Ignite ? 

I need to Asynchronously push to the end of queue , and pull from the start
of queue. I've checked BlockingQueue on Ignite but it doesn't help with what
i need. I need to loosely balance the workload between some workers.
So for every new job coming in I'm planning to consider picking the worker
at the start of the queue , and push the worker to the end of the queue
whenever the worker is done with the job.



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

Local node SEGMENTED error causing node goes down for no obvious reason

[Ray]

I'm running a six nodes Ignite 2.6 cluster.
The config for each server is as follows
































10.29.42.231:49500
10.29.42.233:49500
10.29.42.234:49500
10.29.42.235:49500
10.29.42.236:49500
10.29.42.232:49500














I also enabled direct io plugin.

When I try to ingest data into Ignite using Spark dataframe API, the cluster
will be very slow after the Spark driver connects to the cluster and some of
the server nodes will go down eventually with this error:

Local node SEGMENTED: TcpDiscoveryNode
[id=8ce23742-702e-4309-934a-affd80bf3653, addrs=[10.29.42.232, 127.0.0.1],
sockAddrs=[/10.29.42.232:49500, /127.0.0.1:49500], discPort=49500, order=2,
intOrder=2, lastExchangeTime=1541571124026, loc=true,
ver=2.6.0#20180709-sha1:5faffcee, isClient=false]
2018-11-07T06:12:04,032][INFO ][disco-pool-#457][TcpDiscoverySpi] Finished
node ping [nodeId=844fab1e-4189-4f10-bc84-b069bc18a267, res=true, time=6ms]
[2018-11-07T06:12:04,033][ERROR][tcp-disco-srvr-#2][] Critical system error
detected. Will be handled accordingly to configured handler [hnd=class
o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
tcp-disco-srvr-#2 is terminated unexpectedly.]]
java.lang.IllegalStateException: Thread tcp-disco-srvr-#2 is terminated
unexpectedly.
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:5687)
[ignite-core-2.6.0.jar:2.6.0]
at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[ignite-core-2.6.0.jar:2.6.0]
[2018-11-07T06:12:04,036][ERROR][tcp-disco-srvr-#2][] JVM will be halted
immediately due to the failure: [failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: Thread
tcp-disco-srvr-#2 is terminated unexpectedly.]]

I examined the GC log and all nodes don't have long GC pause.
The network interconnectivity between all these nodes is fine.

The complete logs for all six servers and client are in the attachment.


>From my observation, the PME process when a new thick client in Spark
dataframe API joins topology is very slow and can leads to many problems.
I think the proposal suggested by Nikolay to change thick clients to java
thin clients is a good way to improve this. 
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Spark-Data-Frame-through-Thin-Client-td36814.html

iglog.zip
  



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