Re: Ignite running on JDK10?

[Vladimir Ozerov]

HI,

Please try adding add these flags to JVM startup arguments.

On Fri, Aug 10, 2018 at 5:31 PM KJQ  wrote:

> As a note, I downgraded all of the Docker containers to use JDK 9 (9.0.4)
> and
> I still get the same problem running the SpringBoot 2 application.  Running
> in my IDE a test case works perfectly fine.
>
> *Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess
> class is unavailable.*
>
> *Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @78a89eea*
>
>
>
> -
> KJQ
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite running on JDK10?

[KimJohn Quinn]

I am able to get it running in JDK 10 and so far have not seen any issues
with the functionality I need to use currently.  This is still
early/experimental but since we are already on the JDK9, then JDK10
bandwagon it was important to see if it would even work in our platform.

@Dmitriy, i added the same exports required for JDK9 to get it working on
JDK10.

On Wed, Aug 15, 2018 at 9:48 PM, Dmitriy Setrakyan 
wrote:

> I believe JDK9 is supported, but you need to add certain JVM parameters.
>
> Vladimir, can you comment?
>
> D.
>
> On Fri, Aug 10, 2018, 07:31 KJQ  wrote:
>
>> As a note, I downgraded all of the Docker containers to use JDK 9 (9.0.4)
>> and
>> I still get the same problem running the SpringBoot 2 application.
>> Running
>> in my IDE a test case works perfectly fine.
>>
>> *Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess
>> class is unavailable.*
>>
>> *Caused by: java.lang.IllegalAccessException: class
>> org.apache.ignite.internal.util.GridUnsafe cannot access class
>> jdk.internal.misc.SharedSecrets (in module java.base) because module
>> java.base does not export jdk.internal.misc to unnamed module @78a89eea*
>>
>>
>>
>> -
>> KJQ
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>


-- 


*KimJohn Quinn**k...@logicdrop.com *


*Logicdrop*22620 Woodward Avenue - Suite D
Ferndale, MI 48220
*O* 888.229.2817
*M* 248.882.0728
*www.logicdrop.com *

Re: Ignite running on JDK10?

[Dmitriy Setrakyan]

I believe JDK9 is supported, but you need to add certain JVM parameters.

Vladimir, can you comment?

D.

On Fri, Aug 10, 2018, 07:31 KJQ  wrote:

> As a note, I downgraded all of the Docker containers to use JDK 9 (9.0.4)
> and
> I still get the same problem running the SpringBoot 2 application.  Running
> in my IDE a test case works perfectly fine.
>
> *Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess
> class is unavailable.*
>
> *Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @78a89eea*
>
>
>
> -
> KJQ
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: H2 performs better than ignite !!?

[Denis Magda]

Please share the queries you are running and their execution plans. How
much RAM is allocated to Ignite and what's the overall data size?

--
Denis

On Thu, Aug 9, 2018 at 5:39 AM the_palakkaran  wrote:

> Yes, I am running on a single node. Still ignite being in-memory, I
> expected
> it to perform better than H2. Is there anything I can do to make it faster?
> Like right now I have a single data region, does having multiple data
> regions give me better performance? Something like that?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite running on JDK10?

[Denis Magda]

Please keep using JDK 8 for now. JDK 9/10/11 is planned to be fully
supported in the nearest time.

--
Denis

On Fri, Aug 10, 2018 at 7:31 AM KJQ  wrote:

> As a note, I downgraded all of the Docker containers to use JDK 9 (9.0.4)
> and
> I still get the same problem running the SpringBoot 2 application.  Running
> in my IDE a test case works perfectly fine.
>
> *Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess
> class is unavailable.*
>
> *Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @78a89eea*
>
>
>
> -
> KJQ
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite running on JDK10? (Maybe Solved)

[Denis Magda]

JDK 10/11 is planned to be supported in the nearest time. Stay tuned.

--
Denis

On Fri, Aug 10, 2018 at 8:47 AM KJQ  wrote:

> Added the exports to the SpringBoot plugin seem to work for me in addition
> to
> having them in my compiler and surefire plugins...it at least starts up
> Ignite and I see the Ignite banner.
>
> 
> org.springframework.boot
> spring-boot-maven-plugin
> 
> 
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED
> 
> 
> 
>
>
>
> -
> KJQ
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite persistence to local disk vs to cassandra

[Denis Magda]

This article might be exactly what you're looking for:
https://dzone.com/articles/apachereg-ignite-and-apachereg-cassandra-benchmark

--
Denis

On Fri, Aug 10, 2018 at 9:24 AM Wlodek, Tomasz 
wrote:

> I have a question: Does anyone have numbers which compare the speed of
> ignite when persistence is set to local file system as compared to when it
> is set to Cassandra?
>
> Tom
>
>
> This message may contain information that is confidential or privileged.
> If you are not the intended recipient, please advise the sender immediately
> and delete this message. See
> http://www.blackrock.com/corporate/en-us/compliance/email-disclaimers for
> further information.  Please refer to
> http://www.blackrock.com/corporate/en-us/compliance/privacy-policy for
> more information about BlackRock’s Privacy Policy.
>
> For a list of BlackRock's office addresses worldwide, see
> http://www.blackrock.com/corporate/en-us/about-us/contacts-locations.
>
> © 2018 BlackRock, Inc. All rights reserved.
>

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

[Denis Magda]

Hello Luqman,

That's an excellent plugin! Copying the dev list so that everyone knows.

--
Dneis

On Sun, Aug 12, 2018 at 3:08 PM luqmanahmad  wrote:

> Hi all,
>
> Recently I was working on a project which required a very large number of
> cluster over 700 nodes and we were encountering with split brain problem.
> To
> overcome that problem I have recently developed the plugin for network
> segmentation which can be downloaded from [1].
>
> This can be taken as a gift as it was a much needed functionality which was
> missing from the open source version. At the moment there are two
> segementation resolvers are available. I am still thinking of writing one
> for TcpIp depending on the time.
>
> Any problems with the plugin, please let me know. Happy coding
>
> [1]  ignite-plugins 
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Fwd: how ignite c++ node set baselinetopology

[Denis Magda]

Igor,

I think it's reasonable to add the baseline topology APIs to C++. Can you
plan this for the nearest releases?

Pave, do you have time to do the same for .Net?

--
Denis

-- Forwarded message -
From: aealexsandrov 
Date: Tue, Aug 14, 2018 at 3:23 AM
Subject: Re: how ignite c++ node set baselinetopology
To: 


Hi,

C++ API doesn't contain the methods to update the baseline. So, in this
case, you can use Java API for it:

Add the code that will listen to the EVT_NODE_JOINED event

private final IgniteEx ignite;

ignite.events().localListen(event -> {
DiscoveryEvent e = (DiscoveryEvent)event;

final long topVer = e.topologyVersion();

ignite.cluster().setBaselineTopology(topVer);

return true;
}, EventType.EVT_NODE_JOINED);

The whole example you can see here:

https://apacheignite.readme.io/docs/baseline-topology#section-triggering-rebalancing-programmatically

BR,
Andrei



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

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[bintisepaha]

Thanks for getting back, but we do not use Ignite's native persistence.
Anything else changed from 2.3 to 2.4 to cause this around SQL Queries? 




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

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[akurbanov]

Hi,

Do you use persistence? If so, please check and set up  Baseline topology
   for your cluster
which describes a set of server nodes that are used to store data. The
reason for this behaviour may be a simple fact that some of your nodes are
out of baseline topology.





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

Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

[bintisepaha]

Hi, we have used this query in ignite 2.3 for a while now. But we had some
data streamer exceptions that seemed to have been resolved on 2.4, so we
decided to upgrade. However, in 2.6 and also downgrading to 2.4 we have been
seeing this issue, that a SQL query does not return the data that is in
cache. when we go back to 2.3, it works as expected.

Here is the cache config for that cache.



 










































traderId

orderId






SORTED









traderId

insIid

clearAgent

strategy






SORTED




  




parentId






SORTED











and here is the query

public List getTradeOrdersForPSGroup(Integer traderId, Short
psRuleId, Integer tid, String clearAgent, String strategy, Integer pvId,
Date settlementDate, Date psTime) {
logger.info(String.format("Getting TradeOrders from the cache 
for
traderId: %s, tid: %s, clearAgent: %s, strategy: %s, pvId: %s, settlement:
%s, psTime: %s", traderId, tid, clearAgent, strategy, pvId, settlementDate,

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

[Вячеслав Коптилин]

Hi,

looks like your question is already answered here
http://apache-ignite-users.70518.x6.nabble.com/values-retrieved-from-the-cache-are-wrapped-with-JdkDynamicAopProxy-while-using-springboot-and-JCache-tp23258p23426.html

Thanks,
S.

пн, 13 авг. 2018 г. в 15:14, daya airody :

> Hi slava,
>
> I have uploaded my code at below link:
> https://github.com/daya-airody/ignite-caching
>
> You need uncomment below lines in application.properties before running
> startup.sh.
>
> spring.cache.jcache.config=classpath:example-cache.xml
> spring.cache.cache-names=users,cannedReports
>
> When you run startup.sh, it throws below error:
>
> org.apache.ignite.cache.CacheExistsException: Failed to start cache (a
> cache
> with the same name is already started): users
>
> Please review my code and help me debug this issue.
> Thanks in advance,
> --daya--
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: RequestWrapperV2.getSession(true) returns null

[Ilya Kasnacheev]

Hello again!

Can you please also provide a reproducer which demonstrates this problem?

As I can see from the code, session should be created beforehand in
doFilterV2().

Regards,

-- 
Ilya Kasnacheev

2018-08-15 19:13 GMT+03:00 Ilya Kasnacheev :

> Hello!
>
> I can see how it can be a problem. Do you care to fill a ticket against
> Apache Ignite JIRA?
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-08-15 19:10 GMT+03:00 nitin.phadnis :
>
>> org.apache.ignite.cache.websession.WebSessionFilter.RequestWrapperV2.java
>> getSession(true) should not return null.  If a session does not exist, it
>> should create a new session and return it.
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>

Re: RequestWrapperV2.getSession(true) returns null

[Ilya Kasnacheev]

Hello!

I can see how it can be a problem. Do you care to fill a ticket against
Apache Ignite JIRA?

Regards,

-- 
Ilya Kasnacheev

2018-08-15 19:10 GMT+03:00 nitin.phadnis :

> org.apache.ignite.cache.websession.WebSessionFilter.RequestWrapperV2.java
> getSession(true) should not return null.  If a session does not exist, it
> should create a new session and return it.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

RequestWrapperV2.getSession(true) returns null

[nitin.phadnis]

org.apache.ignite.cache.websession.WebSessionFilter.RequestWrapperV2.java
getSession(true) should not return null.  If a session does not exist, it
should create a new session and return it.



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

Re: distributed-ddl extended-parameters section showing 404 page not found

[Вячеслав Коптилин]

Hello Huang,

Both of them should work. In any way, I would suggest using 'AFFINITY-KEY'
instead of 'AFFINITYKEY'.
You can find the details here:
https://issues.apache.org/jira/browse/IGNITE-6270

By the way, I will try to update the docs.

Thanks,
S.


ср, 15 авг. 2018 г. в 14:19, Huang Meilong :

> thank you slava,
>
>
> it says that to specify an affinity key name we can use AFFINITI_KEY in
> the Parameters section,
>
> "
>
>- AFFINITY_KEY= - specifies an affinity key
> name which
>is a column of the PRIMARY KEY constraint.
>-
>
> "
>
>
> but in the example section, it uses affinityKey
>
>
>
>- SQL 
>
> Copy
>
> CREATE TABLE IF NOT EXISTS Person (
>   id int,
>   city_id int,
>   name varchar,
>   age int,
>   company varchar,
>   PRIMARY KEY (id, city_id)
> ) WITH "template=partitioned,backups=1,affinitykey=city_id, key_type=PersonKe
>
>
>
> which one works？
> --
> *发件人:* Вячеслав Коптилин 
> *发送时间:* 2018年8月15日 16:14:34
> *收件人:* user@ignite.apache.org
> *主题:* Re: distributed-ddl extended-parameters section showing 404 page
> not found
>
> Hello,
>
> Yep, the link is broken, unfortunately.
> It seems it should be the following
> https://apacheignite-sql.readme.io/docs/create-table#section-parameters
>
> Thanks,
> S.
>
> ср, 15 авг. 2018 г. в 10:17, Huang Meilong :
>
> I found it here: https://apacheignite-sql.readme.io/docs/getting-started
> Getting Started - Apache Ignite SQL Documentation
> 
> apacheignite-sql.readme.io
> Apache Ignite is a memory-centric distributed database, caching, and
> processing platform for transactional, analytical, and streaming workloads,
> delivering in-memory speeds at petabyte scale
>
>
> """
>
> to set other cache configurations for the table, you should use the
> template parameter and provide the name of the cache configuration
> previously registered(via XML or code). See extended parameters
> 
>  section
> for more details.
>
> """
> --
> *发件人:* dkarachentsev 
> *发送时间:* 2018年8月15日 14:48:56
> *收件人:* user@ignite.apache.org
> *主题:* Re: distributed-ddl extended-parameters section showing 404 page
> not found
>
> Hi,
>
> Where did you find it? It might be a broken link.
>
> Thanks!
> -Dmitry
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>

答复: distributed-ddl extended-parameters section showing 404 page not found

[Huang Meilong]

thank you slava,


it says that to specify an affinity key name we can use AFFINITI_KEY in the 
Parameters section,

"

  *   AFFINITY_KEY= - specifies an affinity 
key name which is a 
column of the PRIMARY KEY constraint.
  *

"


but in the example section, it uses affinityKey


  *   SQL

Copy

CREATE TABLE IF NOT EXISTS Person (
  id int,
  city_id int,
  name varchar,
  age int,
  company varchar,
  PRIMARY KEY (id, city_id)
) WITH "template=partitioned,backups=1,affinitykey=city_id, key_type=PersonKe



which one works？


发件人: Вячеслав Коптилин 
发送时间: 2018年8月15日 16:14:34
收件人: user@ignite.apache.org
主题: Re: distributed-ddl extended-parameters section showing 404 page not found

Hello,

Yep, the link is broken, unfortunately.
It seems it should be the following 
https://apacheignite-sql.readme.io/docs/create-table#section-parameters

Thanks,
S.

ср, 15 авг. 2018 г. в 10:17, Huang Meilong 
mailto:ims...@outlook.com>>:

I found it here: https://apacheignite-sql.readme.io/docs/getting-started

Getting Started - Apache Ignite SQL 
Documentation
apacheignite-sql.readme.io
Apache Ignite is a memory-centric distributed database, caching, and processing 
platform for transactional, analytical, and streaming workloads, delivering 
in-memory speeds at petabyte scale




"""

to set other cache configurations for the table, you should use the template 
parameter and provide the name of the cache configuration previously 
registered(via XML or code). See extended 
parameters
 section for more details.

"""


发件人: dkarachentsev 
mailto:dkarachent...@gridgain.com>>
发送时间: 2018年8月15日 14:48:56
收件人: user@ignite.apache.org
主题: Re: distributed-ddl extended-parameters section showing 404 page not found

Hi,

Where did you find it? It might be a broken link.

Thanks!
-Dmitry



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

Re: values retrieved from the cache are wrapped with JdkDynamicAopProxy while using springboot and JCache

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

Hi daya,

Yes it is a serialization issue. Field AdvisedSupport.methodCache is marked
transient and method readObject which should initialize this field on
deserialization is not called. So, it has value null and NPE is thrown. I
am not sure whether it is expected behavior or not.
Also, it does not look very nice for me that such proxy is stored into
cache. Perhaps it is better to store simple Java objects, like
ReportsRepDetails in your example.

2018-08-14 19:21 GMT+03:00 ipavlukhin :

> Hi daya,
>
> Sorry for delay. I hope I will have a minute tomorrow to check this case.
>
>
>
> On 13.08.2018 15:04, daya airody wrote:
>
>> HI Ivan,
>>
>> I have uploaded a simple spring application reproducing the issue at below
>> link:
>>
>> https://github.com/daya-airody/ignite-caching
>>
>> When I use ConcurrentMapCache to cache results from spring JPA native
>> query,
>> I am able to retrieve it correctly. However, once I enable ignite and
>> JCache, I run into proxy issues. Looks like I am hitting some
>> serialization
>> problem,
>>
>> Please review my code and help me troubleshoot this issue.
>>
>>
>> thanks in advance,
>>
>> --daya--
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>


-- 
Best regards,
Ivan Pavlukhin

Re: distributed-ddl extended-parameters section showing 404 page not found

[Вячеслав Коптилин]

Hello,

Yep, the link is broken, unfortunately.
It seems it should be the following
https://apacheignite-sql.readme.io/docs/create-table#section-parameters

Thanks,
S.

ср, 15 авг. 2018 г. в 10:17, Huang Meilong :

> I found it here: https://apacheignite-sql.readme.io/docs/getting-started
> Getting Started - Apache Ignite SQL Documentation
> 
> apacheignite-sql.readme.io
> Apache Ignite is a memory-centric distributed database, caching, and
> processing platform for transactional, analytical, and streaming workloads,
> delivering in-memory speeds at petabyte scale
>
>
> """
>
> to set other cache configurations for the table, you should use the
> template parameter and provide the name of the cache configuration
> previously registered(via XML or code). See extended parameters
> 
>  section
> for more details.
>
> """
> --
> *发件人:* dkarachentsev 
> *发送时间:* 2018年8月15日 14:48:56
> *收件人:* user@ignite.apache.org
> *主题:* Re: distributed-ddl extended-parameters section showing 404 page
> not found
>
> Hi,
>
> Where did you find it? It might be a broken link.
>
> Thanks!
> -Dmitry
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

答复: distributed-ddl extended-parameters section showing 404 page not found

[Huang Meilong]

I found it here: https://apacheignite-sql.readme.io/docs/getting-started

Getting Started - Apache Ignite SQL 
Documentation
apacheignite-sql.readme.io
Apache Ignite is a memory-centric distributed database, caching, and processing 
platform for transactional, analytical, and streaming workloads, delivering 
in-memory speeds at petabyte scale




"""

to set other cache configurations for the table, you should use the template 
parameter and provide the name of the cache configuration previously 
registered(via XML or code). See extended 
parameters
 section for more details.

"""


发件人: dkarachentsev 
发送时间: 2018年8月15日 14:48:56
收件人: user@ignite.apache.org
主题: Re: distributed-ddl extended-parameters section showing 404 page not found

Hi,

Where did you find it? It might be a broken link.

Thanks!
-Dmitry



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

Re: distributed-ddl extended-parameters section showing 404 page not found

[dkarachentsev]

Hi,

Where did you find it? It might be a broken link.

Thanks!
-Dmitry



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