Ignite SQL Grid Load

[Raja]

Hi,
I have a 12 node ignite cluster with node configuration of 8 core, 10g
memory
I am using the following JVM options as recommended by ignite docs

IGNITE_JVM_OPTS=-server \ 
-Xms8g \
-Xmx8g \
-XX:+UseParNewGC \
-XX:+UseConcMarkSweepGC \
-XX:+UseTLAB \
-XX:NewSize=128m \
-XX:MaxNewSize=128m \
-XX:MaxTenuringThreshold=0 \
-XX:SurvivorRatio=1024 \
-XX:+UseCMSInitiatingOccupancyOnly \
-XX:CMSInitiatingOccupancyFraction=40 \
-XX:MaxGCPauseMillis=1000  \
-XX:InitiatingHeapOccupancyPercent=50 \
-XX:+UseCompressedOops \
-XX:ParallelGCThreads=8 \
-XX:ConcGCThreads=8 \
-XX:+DisableExplicitGC


When I tried to load test ONE REST client, it just cannot handle more than 1
thread. If I hit it with 2 or more threads, some sql queries randomly fails.
Even after increasing cluster to 40 nodes. No difference. Just if hit with
more than 1 thread everything falls apart. 

Wondering if I'm missing something. We wanted to have cluster with a
configuration where 50 or more concurrent users will be hitting Ignite.

Is it possible with Ignite. BTW we are running geo-spatial sql queries on
ignite.

Appreciate any insights into this.  
 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-SQL-Grid-Load-tp11072.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

[Roman Shtykh]

MyBatis Ignite cache is updated. The new version is 
1.0.4.http://www.mybatis.org/ignite-cache/

Best regards,Roman


On Wednesday, March 8, 2017 4:50 AM, Denis Magda  wrote:
 

 Andrey,
Excellent! Thanks for keeping an eye on this. Please let us know what you do 
the same for Zeppelin.
*Raul*, *Roman*, could you update Camel and MyBatis integrations 
respectively?https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations
—Denis

On Mar 7, 2017, at 11:47 AM, Andrey Gura  wrote:
JFYI

Also today Vert.x 3.4.0 was released with Apache Ignite 1.9 based
cluster manager for Vert.x in HA/Clustered mode.

On Tue, Mar 7, 2017 at 3:10 AM, Denis Magda  wrote:

The Apache Ignite Community is pleased to announce the release of Apache Ignite 
1.9.0.

Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
distributed in-memory platform for computing and transacting on large-scale 
data sets in real-time, orders of magnitude faster than possible with 
traditional disk-based or flash-based technologies.

The Fabric is a collection of independent and well integrated components some 
of which are the following:
Data Grid
SQL Grid
Compute Grid
Streaming & CEP
Service Grid


In this release the community provided an integration with Kubernetes cluster 
manager, improved performance of core and SQL Grid components, expanded Data 
Modification Language support to the level of .NET and C++ API, integrated with 
.NET TransactionScope API and more.

Learn more details from our blog post: 
https://blogs.apache.org/ignite/entry/apache-ignite-1-9-released

The full list of the changes can be found here [2].

Please visit this page if you’re ready to try the release out:
https://ignite.apache.org/download.cgi

Please let us know [3] if you encounter any problems.

Regards,

The Apache Ignite Community

[1] https://ignite.apache.org
[2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
[3] https://ignite.apache.org/community/resources.html#ask





   

Upgrade to 1.8.0 problems

[Isaeed Mohanna]

Hi
I have a 1.7.0 cluster with two nodes with several caches in it, i tried
moving to Ignite 1.8.0 unfortunately i am facing two issues:
1. My query's stopped working against the cache. A simple SQL Query like
this
SqlQuery sql = new SqlQuery(Entity.class, "type
= ?");
type is part of the entity class its a simply enum, any idea why my query
now returns zero results?

2. In my efforts to resolve problem 1, i thought to start using binary
marshaller in my entities which implemented Externalizable interface, i
removed the interface to use the binary marshaller which actually  helped
and my query is working again however whenever i have two nodes in the
cluster i receive the following exception several times when I join the
second node to the cluster but it appears to go away afterwards. what is
causing this exception? and how do i resolve the problem?
Thanks

[2017-03-08 05:58:19] [ERROR]
[org.apache.ignite.internal.processors.task.GridTaskWorker:org.apache.ignite.logger.slf4j.Slf4jLogger.error(Slf4jLogger.java:112)]:
Failed to obtain remote job result policy for result from
ComputeTask.result(..) method (will fail the whole task): GridJobResultImpl
[job=C2V2 [c=com.hhh.Task@100853d8], sib=GridJobSiblingImpl
[sesId=a454e7caa51-9feeb429-75c5-4920-81a1-e95fdb12ebd5,
jobId=b454e7caa51-9feeb429-75c5-4920-81a1-e95fdb12ebd5,
nodeId=a02307c0-64d8-443f-83e5-2dbdca9ab259, isJobDone=false],
jobCtx=GridJobContextImpl
[jobId=b454e7caa51-9feeb429-75c5-4920-81a1-e95fdb12ebd5, timeoutObj=null,
attrs={}], node=TcpDiscoveryNode [id=a02307c0-64d8-443f-83e5-2dbdca9ab259,
addrs=[20.0.2.55], sockAddrs=[/20.0.2.55:47500], discPort=47500, order=2,
intOrder=2, lastExchangeTime=1488952697596, loc=false,
ver=1.8.0#20161205-sha1:9ca40dbe, isClient=false], ex=class
o.a.i.IgniteException: null, hasRes=true, isCancelled=false,
isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception
(override or implement ComputeTask.result(..) method if you would like to
have automatic failover for this exception).
at
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1030)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1023)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6596)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1023)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:841)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2V2.execute(GridClosureProcessor.java:2040)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:556)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6564)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:550)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:479)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1894)
... 7 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceTopology(GridServiceProcessor.java:700)
at
org.apache.ignite.internal.processors.service.GridServiceProxy.randomNodeForService(GridServiceProxy.java:249)
at
org.apache.ignite.internal.processors.service.GridServiceProxy.nodeForService(GridServiceProxy.java:226)
at

Define QuerySqlField in the config file instead of C# code

[mrinalkamboj]

This is how I declare an entity in C#, which needs to be persisted in the
Cache:

*
[Serializable]
public class OrderEntity
{
[QuerySqlField(IsIndexed = true)]
public int OrderId { get; set; }

[QuerySqlField]
public string OrderName { get; set; }
}
*

The same entity, I want to propagate further in the application, for
processing once its fetched from the Cache, but the challenge is attribute
*[QuerySqlField]* needs Apache ignite reference, which then needs to
propagate to higher layers, which is undesirable, so only options are:

1. Either I can define these details in the config file, since they are
mandatory for Sql querying the entity.

Not sure if the same can be defined under *cacheConfiguration -
queryEntities* as follows

* 
 
  


  
  

  

*

2. Define a separate business entity, do the explicit mapping post fetching
the Cache entity, which is the last option due to lot of extra work





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Define-QuerySqlField-in-the-config-file-instead-of-C-code-tp11067.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

[Anil]

Thank you Andrey for good news.

On 8 March 2017 at 01:17, Andrey Gura  wrote:

> JFYI
>
> Also today Vert.x 3.4.0 was released with Apache Ignite 1.9 based
> cluster manager for Vert.x in HA/Clustered mode.
>
> On Tue, Mar 7, 2017 at 3:10 AM, Denis Magda  wrote:
> > The Apache Ignite Community is pleased to announce the release of Apache
> Ignite 1.9.0.
> >
> > Apache Ignite In-Memory Data Fabric [1] is a high-performance,
> integrated and distributed in-memory platform for computing and transacting
> on large-scale data sets in real-time, orders of magnitude faster than
> possible with traditional disk-based or flash-based technologies.
> >
> > The Fabric is a collection of independent and well integrated components
> some of which are the following:
> > Data Grid
> > SQL Grid
> > Compute Grid
> > Streaming & CEP
> > Service Grid
> >
> >
> > In this release the community provided an integration with Kubernetes
> cluster manager, improved performance of core and SQL Grid components,
> expanded Data Modification Language support to the level of .NET and C++
> API, integrated with .NET TransactionScope API and more.
> >
> > Learn more details from our blog post: https://blogs.apache.org/
> ignite/entry/apache-ignite-1-9-released
> >
> > The full list of the changes can be found here [2].
> >
> > Please visit this page if you’re ready to try the release out:
> > https://ignite.apache.org/download.cgi
> >
> > Please let us know [3] if you encounter any problems.
> >
> > Regards,
> >
> > The Apache Ignite Community
> >
> > [1] https://ignite.apache.org
> > [2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
> > [3] https://ignite.apache.org/community/resources.html#ask
>

Re: getOrCreateCache hang

[bintisepaha]

Matt, I have not tried your code (not a committer to the community), but what
happens when you use Ignite.cache(), if the cache was already created on
server startup.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/getOrCreateCache-hang-tp10737p11065.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

[bintisepaha]

Could you please tell us what the logs would say if there was a deadlock?
we rollback the txn on any exception explicitly.

We are running 1.8 in UAT environment this week. It is not a simple upgrade
to production, we need to let it burn in. But in UAT we never saw this issue
with 1.7 either. It already happened in production, so far 3 times.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p11064.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

[Denis Magda]

Updated news section on the site and tweeted about the release:
https://twitter.com/ApacheIgnite/status/839208220841275392 


—
Denis

> On Mar 6, 2017, at 4:10 PM, Denis Magda  wrote:
> 
> The Apache Ignite Community is pleased to announce the release of Apache 
> Ignite 1.9.0.
> 
> Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
> distributed in-memory platform for computing and transacting on large-scale 
> data sets in real-time, orders of magnitude faster than possible with 
> traditional disk-based or flash-based technologies.
> 
> The Fabric is a collection of independent and well integrated components some 
> of which are the following:  
> Data Grid
> SQL Grid
> Compute Grid
> Streaming & CEP
> Service Grid
> 
> 
> In this release the community provided an integration with Kubernetes cluster 
> manager, improved performance of core and SQL Grid components, expanded Data 
> Modification Language support to the level of .NET and C++ API, integrated 
> with .NET TransactionScope API and more.
> 
> Learn more details from our blog post: 
> https://blogs.apache.org/ignite/entry/apache-ignite-1-9-released
> 
> The full list of the changes can be found here [2].
> 
> Please visit this page if you’re ready to try the release out:
> https://ignite.apache.org/download.cgi
> 
> Please let us know [3] if you encounter any problems.
> 
> Regards,
> 
> The Apache Ignite Community
> 
> [1] https://ignite.apache.org
> [2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
> [3] https://ignite.apache.org/community/resources.html#ask

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

[Denis Magda]

Andrey,

Excellent! Thanks for keeping an eye on this. Please let us know what you do 
the same for Zeppelin.

*Raul*, *Roman*, could you update Camel and MyBatis integrations respectively?
https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations 


—
Denis

> On Mar 7, 2017, at 11:47 AM, Andrey Gura  wrote:
> 
> JFYI
> 
> Also today Vert.x 3.4.0 was released with Apache Ignite 1.9 based
> cluster manager for Vert.x in HA/Clustered mode.
> 
> On Tue, Mar 7, 2017 at 3:10 AM, Denis Magda  wrote:
>> The Apache Ignite Community is pleased to announce the release of Apache 
>> Ignite 1.9.0.
>> 
>> Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated 
>> and distributed in-memory platform for computing and transacting on 
>> large-scale data sets in real-time, orders of magnitude faster than possible 
>> with traditional disk-based or flash-based technologies.
>> 
>> The Fabric is a collection of independent and well integrated components 
>> some of which are the following:
>> Data Grid
>> SQL Grid
>> Compute Grid
>> Streaming & CEP
>> Service Grid
>> 
>> 
>> In this release the community provided an integration with Kubernetes 
>> cluster manager, improved performance of core and SQL Grid components, 
>> expanded Data Modification Language support to the level of .NET and C++ 
>> API, integrated with .NET TransactionScope API and more.
>> 
>> Learn more details from our blog post: 
>> https://blogs.apache.org/ignite/entry/apache-ignite-1-9-released
>> 
>> The full list of the changes can be found here [2].
>> 
>> Please visit this page if you’re ready to try the release out:
>> https://ignite.apache.org/download.cgi
>> 
>> Please let us know [3] if you encounter any problems.
>> 
>> Regards,
>> 
>> The Apache Ignite Community
>> 
>> [1] https://ignite.apache.org
>> [2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
>> [3] https://ignite.apache.org/community/resources.html#ask

Re: [ANNOUNCE] Apache Ignite 1.9.0 Released

[Andrey Gura]

JFYI

Also today Vert.x 3.4.0 was released with Apache Ignite 1.9 based
cluster manager for Vert.x in HA/Clustered mode.

On Tue, Mar 7, 2017 at 3:10 AM, Denis Magda  wrote:
> The Apache Ignite Community is pleased to announce the release of Apache 
> Ignite 1.9.0.
>
> Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
> distributed in-memory platform for computing and transacting on large-scale 
> data sets in real-time, orders of magnitude faster than possible with 
> traditional disk-based or flash-based technologies.
>
> The Fabric is a collection of independent and well integrated components some 
> of which are the following:
> Data Grid
> SQL Grid
> Compute Grid
> Streaming & CEP
> Service Grid
>
>
> In this release the community provided an integration with Kubernetes cluster 
> manager, improved performance of core and SQL Grid components, expanded Data 
> Modification Language support to the level of .NET and C++ API, integrated 
> with .NET TransactionScope API and more.
>
> Learn more details from our blog post: 
> https://blogs.apache.org/ignite/entry/apache-ignite-1-9-released
>
> The full list of the changes can be found here [2].
>
> Please visit this page if you’re ready to try the release out:
> https://ignite.apache.org/download.cgi
>
> Please let us know [3] if you encounter any problems.
>
> Regards,
>
> The Apache Ignite Community
>
> [1] https://ignite.apache.org
> [2] https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
> [3] https://ignite.apache.org/community/resources.html#ask

Re: getOrCreateCache hang

[Matt Warner]

Nikolai, I feel disappointed with how this email chain seems to be going. I
spent time and effort to assemble sample code that exhibits the problem
consistently only to hear that it doesn't seem like you're even using that
code. That leaves me wondering what you were actually testing, when you
told me you couldn't reproduce this. It does not sound like you were using
the code I supplied.

I also sent thread dumps and logs early on in this process, and the current
thread dumps show the same as before—getOrCreateCache.

This problem does seem tied to the CacheJdbcStoreSessionListener data
source, but I've so far been unable to pin it down beyond that. No doubt
it's something simple I'm doing wrong, but whatever it is still eludes me.

Matt

On Tue, Feb 28, 2017 at 2:14 AM, Nikolai Tikhonov 
wrote:

> I am not able reproduce exactly your test (do not have Postgre instance),
>  but I do not get hangs on start caches. I suppose that issue related with
> your setup and for getting cause of problem I need full logs and thread
> dumps (by kill -3 PID or jstack) from all nodes. Could you please provide
> this data?
>
> On Mon, Feb 27, 2017 at 10:36 PM, Matt Warner 
> wrote:
>
>> Something's not right. I'm seeing this as 100% reproducible on two
>> different OSes.
>>
>> Are you running "mvn package" on both testIgnite1 and testIgnite2 and
>> then starting the shaded JARs simultaneously from two different shell
>> windows using "java-jar ignite?...-standalone.jar"?
>>
>> Matt
>>
>> On Feb 27, 2017, at 8:58 AM, Nikolai Tikhonov 
>> wrote:
>>
>> I was not able reproduce it. Could you share full logs and thread dumps
>> from all nodes?
>>
>> On Mon, Feb 27, 2017 at 7:45 PM, Matt Warner 
>> wrote:
>>
>>> Using the test code I sent previously, I changed the ports to be a range
>>> but both clients still deadlock on getOrCreateCache.
>>>
>>> Are you able to reproduce this using the test code I sent?
>>>
>>> Matt
>>>
>>>
>>> On Mon, Feb 27, 2017 at 3:02 AM, Nikolai Tikhonov 
>>> wrote:
>>>
 Hi Matt!

 Try to change ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500")); to
 ipFinder.setAddresses(Arrays.asList("127.0.0.1:47500..47505"));

 On Fri, Feb 24, 2017 at 4:00 PM, Matt Warner  wrote:

> Hi Nikolai.
>
> I discovered the reason the two applications weren't seeing each other
> was resolved by adding an explicit port number (Arrays.asList("
> 127.0.0.1:47500")). However, the two still deadlock when running
> concurrently.
>
> The latest test shows one application blocked in getOrCreateCache, the
> other blocked in Ignition.start. As soon as I kill the process stuck in
> Iginition.start the other process continues successfully. I've attached 
> the
> latest test code.
>
> Any ideas?
>
> Matt
>
> On Wed, Feb 22, 2017 at 10:30 AM, Matt Warner [via Apache Ignite
> Users] <[hidden email]
> > wrote:
>
>> One other observation: with the third application acting as just the
>> server, and just one of the clients running, there is no issue. Only when
>> there are multiple clients do I get the deadlock on getOrCreateCache.
>>
>> Matt
>>
>> --
>> If you reply to this email, your message will be added to the
>> discussion below:
>> http://apache-ignite-users.70518.x6.nabble.com/getOrCreateCa
>> che-hang-tp10737p10811.html
>> To unsubscribe from getOrCreateCache hang, click here.
>> NAML
>> 
>>
>
>
> *testIgnite.tar.gz* (14K) Download Attachment
> 
>
> --
> View this message in context: Re: getOrCreateCache hang
> 
>
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>


>>>
>>
>

Re: CacheStore.loadCache loading data for 1024 partitions for a single node

[Sumanta Ghosh]

It is not causing problems so to say; however I am concerned then we have
1024 queries executed per cache during startup; in case there is any
configuration to set up the total number of partitions, that would give us
more control I believe.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-loadCache-loading-data-for-1024-partitions-for-a-single-node-tp11028p11059.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: [EXTERNAL] Re: Failed to write class name to file: java.io.FileNotFoundException

[rjdamore]

This may be a Windows OS specific problem, I have the same issue and research
into it has shown this issue exists outside of Ignite as well.  There may be
(further down the stack trace) reference to the statement: "The requested
operation cannot be performed on a file with a user-mapped section open". 
I'm not certain how to solve this issue, but as I've seen during execution
the exception does not prevent further execution.  I'm not sure if this
helps, but I wanted to put it here anyway so others may have an idea of what
the "user-mapped section" info is about. Perhaps someone has seen this
elsewhere and come to a solution?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-write-class-name-to-file-java-io-FileNotFoundException-tp7855p11058.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

accurate offheap metrics

[lawrencefinn]

What's the best way to get accurate metrics of offheap memory used?  I've
tried a bunch of different ways such as utilizing jmx, utilizing the API and
iterating through each cache on each node to get offHeapAllocatedSize, using
rest api, etc...  None of the values add up right.  I see my ignite process
taking up 4GB, max heap is 2GB, and all the calculations are around 300MB. 
Are indexes not taken into account?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/accurate-offheap-metrics-tp11057.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache.Ignite.Core.Common.IgniteException: Failed to initialize JVM.

[Saifullah Zahid]

Hi,

My project is 64bit and I am using 64bit JVM

Still I need to specify above option?

Thanks,
Saif

On Tue, Mar 7, 2017 at 6:30 PM, davida  wrote:

> Have You checked "Prefer 32 bit" option in VS project properties ?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Apache-Ignite-Core-Common-IgniteException-Failed-to-
> initialize-JVM-tp11054p11055.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Apache.Ignite.Core.Common.IgniteException: Failed to initialize JVM.

[davida]

Have You checked "Prefer 32 bit" option in VS project properties ?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-Core-Common-IgniteException-Failed-to-initialize-JVM-tp11054p11055.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Apache.Ignite.Core.Common.IgniteException: Failed to initialize JVM.

[Saifullah Zahid]

Hi,

I have created an ignite server node using Ignite.Net.

When I run this node in windows service node I get following exception.

Apache.Ignite.Core.Common.IgniteException: Failed to initialize JVM. --->
Apache.Ignite.Core.Common.IgniteException: Java class is not found (did you
set IGNITE_HOME environment variable?):
org/apache/ignite/internal/processors/platform/utils/PlatformUtils
   --- End of inner exception stack trace ---
   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32
stackTraceCharsLen, Void* errData, Int32 errDataLen)
   at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.CreateContext(Void*
opts, Int32 optsLen, Void* cbs)
   at Apache.Ignite.Core.Impl.IgniteManager.CreateJvm(IgniteConfiguration
cfg, UnmanagedCallbacks cbs)
   at
Apache.Ignite.Core.Impl.IgniteManager.CreateJvmContext(IgniteConfiguration
cfg, UnmanagedCallbacks cbs, ILogger log)
   at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
   at Apache.Ignite.Core.Ignition.StartFromApplicationConfiguration()

IGNITE_HOME environment variable is in place.

It works fine in console mode.

Thanks,
Saif

Re: Running a IgniteRunnable on local node using compute

[Andrey Mashenkov]

Hi Anil,

Do you mean this is not work for you?

new IgniteRunnable() {
  @IgniteInstanceResource
  Ignite ignite;
@Override
public void run() {

ignite

}
}





On Tue, Mar 7, 2017 at 8:43 AM, Anil  wrote:

>
> ignite.compute(ignite..cluster().forLocal()).run() will run the ignite
> runnble on local node.
>
> final pseudo code -
>
> ignite.compute().broadcast(new IgniteRunnable() {
> @Override
> public void run() {
>
> Observable o = Observable.timer(((CommonUtils.getCurrentDayTime() +
> 24 * 60 * 60 * 1000) - System.currentTimeMillis()), 24 * 60 * 60 * 1000, 
> TimeUnit.MILLISECONDS,
> scheduler);
> o.subscribe(item -> {
> ignite.compute(ignite..cluster().forLocal()).run(new
> IgniteRunnableTask());
> });
> }
> });
>
>
>
> On 7 March 2017 at 10:23, Anil  wrote:
>
>> Hi,
>>
>> Are there any settings to use ignite.compute().run() to run the task on
>> local node ?
>>
>> i am try to schedule the task on each node using Rx Scheduler. so I am
>> broadcasting a runnable which initiates the scheduler on each node.
>>
>> As I know, we cannot run a task on local node using
>> ignite.compute().run(). this will run the task on one of the nodes. correct
>> ?
>>
>> we can start the thread for runnable instance and this will run the task
>> on local node. Bu this cannot inject ignite instance into runnable instance.
>>
>> Do you have any suggestions to achieve this ?
>>
>> Thanks
>>
>>
>>
>

Re: NullPointerException for @LoggerResource

[conor]

Ah I see, OK.  So I tried it just now as follows:

IgniteConfiguration cfg = new IgniteConfiguration();

// Set user attributes
cfg.setUserAttributes(getUserAttributes());

private Map getUserAttributes() {
Map userAttributes = new HashMap<>();
SecurityCredentials securityCredentials = new
SecurityCredentials(getModuleName(), passwordService.getPassword());
userAttributes.put("org.apache.ignite.security.cred",
securityCredentials);
return userAttributes;
}


But I get the following error:

Caused by: org.apache.ignite.IgniteCheckedException: User attribute has
illegal name: 'org.apache.ignite.security.cred'. Note that all names
starting with 'org.apache.ignite' are reserved for internal use.

How can I set the security credentials for the local node?




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-for-LoggerResource-tp11037p11050.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: NullPointerException for @LoggerResource

[vkulichenko]

setNodeAttributes is an SPI interface method and therefore is supposed to be
invoked only by Ignite, not by your code. To add attributes to a node, use
IgniteConfiguration#setUserAttributes.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-for-LoggerResource-tp11037p11049.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: CacheStore.loadCache loading data for 1024 partitions for a single node

[vkulichenko]

Why is it too high? Is it causing any problems?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/CacheStore-loadCache-loading-data-for-1024-partitions-for-a-single-node-tp11028p11048.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.