Re: Get client node instance

[arthi]

Hi,

We are tracking these Jira issues -
https://issues.apache.org/jira/browse/IGNITE-3060
https://issues.apache.org/jira/browse/IGNITE-3054

We expect the client handling to improve with both of these issues. 
Are these expected to be fixed in the near future? 
When is the 1.7 release? Is there any earlier release when these can be
done?

Thanks,
Arthi





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Get-client-node-instance-tp4897p5045.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Host Arrays in C++ API

[arthi]

Hi Igor & Val,

We are tracking this issue -
https://issues.apache.org/jira/browse/IGNITE-2946.

Is there a tested patch available for this fix. 
I saw a pull request - https://github.com/apache/ignite/pull/649
I this in the master now? 

the jira says the fix version is 1.7. When is that planned to happen? 

Thanks,
Arthi




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Host-Arrays-in-C-API-tp3707p5044.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

SQL Query - Standard Devation

[vineet]

Hello,I was wondering if the SQL standard deviation functions STDDEV_POP and
STDDEV_SAMP are supported. I did give it a try and got an
ArrayIndexOutOfBounds exception (v 1.5.0):Caused by:
java.lang.ArrayIndexOutOfBoundsException: 8 at
org.apache.ignite.internal.processors.query.h2.sql.GridSqlAggregateFunction.(GridSqlAggregateFunction.java:58)It
appears looking at the GridSqlFunctionType class that there is no support
for stddev functions at the moment. I was wondering if there are plans to
add support or if there is a workaround.Thanks!-VC



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

Re: Persistence using Cassandra

[ChickyDutt]

Thank you for the reply.

Meanwhile could you illuminate on the XML configuration details for a node
to operate with read and write through behaviours on Cassandra?

Please let me know if you need any further information.

Regards
Ashish Sharma.
On 19 May 2016 4:23 p.m., "Alexey Kuznetsov [via Apache Ignite Users]" <
ml-node+s70518n5032...@n6.nabble.com> wrote:

> Hi Chicky D.!
>
> Cassandra cache store was merged into upcoming ignite-1.6 release.
> ignite-1.6 is under voting process right now and may be released next week.
>
> JIRA issue for that store:
> https://issues.apache.org/jira/browse/IGNITE-1371
>
> But you may already try latest nightly build.
> See https://ignite.apache.org/community/contribute.html#nightly-builds
>
> This ignite-cassandra module is not yet documented (will be done soon),
> but it has tests - you may take a look.
>
> Hope this help.
>
> On Thu, May 19, 2016 at 8:18 PM, ChickyDutt <[hidden email]
> > wrote:
>
>> Hi Team,
>>
>> I am trying to implement cache store persistence in Cassandra. Is their
>> any Cassandra specific module available off the shelf or any ignite
>> provided utilities that could help me binf the two?
>>
>> Please let me know if you need any further information.
>>
>> Regards,
>> Chicky D.
>>
>> --
>> View this message in context: Persistence using Cassandra
>> 
>> Sent from the Apache Ignite Users mailing list archive
>>  at Nabble.com.
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-ignite-users.70518.x6.nabble.com/Persistence-using-Cassandra-tp5031p5032.html
> To start a new topic under Apache Ignite Users, email
> ml-node+s70518n...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




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

SQL - SELECT clean rows

[tomk]

Hi,
In my case I am caching database postgresql.  Then, I want to query it via
JDBC. It is working for me. One thing that bother me is format of returned
rows. I wouldnt like to see key there (only value).  How to lock returning
Key by JDBC ?



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

Efficiency worse than postgresql. Why ?

[tomk]

Hello,  
I measure time of time: number of rows is 15 000, using JDBC in both cases.
My case is such that ignite is cache of postgresql. Entire database is
loaded to cache (ignitevisorcmd shown 15 000 rows in cache scan).  
Ignite
SELECT COUNT(*): 53ms.
SELECT *:290 ms

Postgresql
SELECT COUNT(*): 3ms
SELECT *:89 ms.

Why ? I have no indexes in apache ignite. 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Efficiency-worse-than-postgresql-Why-tp5040.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cancel tasks on Ignite compute grid worker nodes

[fs12345]

Hi, 

Thank you for your help.
I have tried activeTaskFutures() and was able to cancel tasks that way. 

Regards,







--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cancel-tasks-on-Ignite-compute-grid-worker-nodes-tp5027p5039.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Failed to execute compound future reducer: Compound future listener []class org.apache.ignite.IgniteCheckedException

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that the community
can receive email notifications? Here is the instruction: 


cmnaik wrote
> Hi, I am using data streamer for cache update, and using kafka to
> integrate with streamer to update cache with incoming data, it works fine
> if only one instance of ignite is running but when we have multiple
> instance running it is throwing below error. Let me know if anyone come
> across this or know solution for this problem. 
> 
> Caused by: java.lang.ClassNotFoundException:
> com.tgt.atpc.race.cache.configuration.RaceIgniteConfiguration$$EnhancerBySpringCGLIB$$c79d0918

Any idea what this class is? It's in your package and being sent to the
server node. Is this expected?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-execute-compound-future-reducer-Compound-future-listener-class-org-apache-ignite-IgniteChen-tp5026p5038.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IgniteCache method replace(key,newVal) behave different with replace(key,oldVal,newVal)

[vkulichenko]

Hi,

This trace is still not full. There should be also the root cause which
happened on primary node and should be attached to this one. If it's not the
case, please also check server node logs.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-method-replace-key-newVal-behave-different-with-replace-key-oldVal-newVal-tp4986p5037.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error creating IgniteContext - Ignite instance with provided name doesn't exist.

[vkulichenko]

Hi,

When IgniteContext is created it applies the following strategy:
1) First it checks whether Ignite instance is already started in the process
using node name defined in configuration.
2) If failed, it tries to start a node.

Exception handling in 1.5 is not ideal in this place because Ignite might
lose actual exception details. This is already fixed in master, you can try
the latest nightly build:
http://ignite.apache.org/community/contribute.html#nightly-builds

Another option is to execute this code prior to creating the IgniteContext:

var cfg = IgnitionEx.loadConfiguration("default-config.xml").get1()
cfg.setClientMode(true);
Ignition.start(cfg);

I expect that an exception will be thrown during call to "Ignite.start()"
and this should reveal the root cause.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Error-creating-IgniteContext-Ignite-instance-with-provided-name-doesn-t-exist-tp5021p5036.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cancel tasks on Ignite compute grid worker nodes

[vkulichenko]

In addition there is IgniteCompute.activeTaskFutures() method that returns
all currently running tasks executed by current node. You can also use these
futures to cancel tasks.

Also note that you can only cancel the whole task (which as usually a set of
several job executed on server nodes). Once you cancel the task, all jobs
will be interrupted.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cancel-tasks-on-Ignite-compute-grid-worker-nodes-tp5027p5035.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cancel tasks on Ignite compute grid worker nodes

[vdpyatkov]

Hello,

My first answer is corrupted. I duplicate it again

I would used support asynchronous operation, and cancel IgniteFuture if
needed.
For example:
1) Create cluster group by attribute
cg = cluster.forAttribute("ROLE", "worker");
2) Make compute async
c = igniteClient.compute(cg).withAsync()
3) Start executing task
c.call(job)
IgniteFuture f = c.future()
4) cancel or wait result
f.cancel()
f.get()





fs12345 wrote
> Hi all,
> 
> Let me start by saying I am quite a novice with Apache Ignite. 
> 
> Here is my question : I want to be able to monitor and cancel tasks
> running or that are going to run on worker nodes of an Ignite Cluster (say
> for example if one task takes too long to complete), and without using
> Visor. 
> 
> I tried to query all EVTS_TASK_EXECUTION events (from EventType) on all
> nodes as follows:
> 
> Ignite grid = Ignition.ignite("GRID_NAME");
> Collection
> 
>  allEvents = grid.events().remoteQuery(event -> true,0,
> EventType.EVTS_TASK_EXECUTION)
> for (Event evt : allEvents){
>   TaskEvent taskEvent = (TaskEvent) evt;
>   System.out.println(taskEvent);
> }
> 
> Each TaskEvent,  has a taskSessionId() method, and a .node() method. It
> seems that the .node() method returns the client node that originated the
> task with the corresponding IgniteUuid returned by taskSessionId().
> 
> On the other hand, when looking at ClusterMetrics for worker nodes I can
> retrieve the number of Jobs currently running on Worker Nodes, current CPU
> load etc : 
> 
> ClusterGroup workerNodes = grid.cluster().forAttribute("ROLE","WORKER");
> for(ClusterNode node : workerNodes.nodes()){
>   System.out.println(node.metrics().getCurrentActiveJobs());
> }
> 
> How could I 
>   1) Cancel tasks currently being run on worker nodes (whose number are
> displayed in the result of getCurrentActiveJobs()) or 
>   2) Cancel tasks dispatched by the clients nodes, for which I have an
> IgniteUuid ,
>   
> possibly without using grid.close() or such hard methods.
> 
> Thanks for your help





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cancel-tasks-on-Ignite-compute-grid-worker-nodes-tp5027p5034.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cancel tasks on Ignite compute grid worker nodes

[vdpyatkov]

fs12345 wrote
> Hi all,
> 
> Let me start by saying I am quite a novice with Apache Ignite. 
> 
> Here is my question : I want to be able to monitor and cancel tasks
> running or that are going to run on worker nodes of an Ignite Cluster (say
> for example if one task takes too long to complete), and without using
> Visor. 
> 
> I tried to query all EVTS_TASK_EXECUTION events (from EventType) on all
> nodes as follows:
> 
> Ignite grid = Ignition.ignite("GRID_NAME");
> Collection
> 
>  allEvents = grid.events().remoteQuery(event -> true,0,
> EventType.EVTS_TASK_EXECUTION)
> for (Event evt : allEvents){
>   TaskEvent taskEvent = (TaskEvent) evt;
>   System.out.println(taskEvent);
> }
> 
> Each TaskEvent,  has a taskSessionId() method, and a .node() method. It
> seems that the .node() method returns the client node that originated the
> task with the corresponding IgniteUuid returned by taskSessionId().
> 
> On the other hand, when looking at ClusterMetrics for worker nodes I can
> retrieve the number of Jobs currently running on Worker Nodes, current CPU
> load etc : 
> Hello,
> 
> I not sure, what I all understood correctly.
> But I would used support asynchronous operation, and cancel IgniteFuture
> if needed.
> For example:
> 1) Create cluster group by attribute
> cg = cluster.forAttribute("ROLE", "worker");
> 2) Make compute async
> c = igniteClient.compute(cg).withAsync()
> 3) Start executing task
> c.call(job)
> IgniteFuture f = c.future()
> 4) cancel or wait result
> f.cancel()
> f.get()
> 
> ClusterGroup workerNodes = grid.cluster().forAttribute("ROLE","WORKER");
> for(ClusterNode node : workerNodes.nodes()){
>   System.out.println(node.metrics().getCurrentActiveJobs());
> }
> 
> How could I 
>   1) Cancel tasks currently being run on worker nodes (whose number are
> displayed in the result of getCurrentActiveJobs()) or 
>   2) Cancel tasks dispatched by the clients nodes, for which I have an
> IgniteUuid ,
>   
> possibly without using grid.close() or such hard methods.
> 
> Thanks for your help





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cancel-tasks-on-Ignite-compute-grid-worker-nodes-tp5027p5033.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Persistence using Cassandra

[Alexey Kuznetsov]

Hi Chicky D.!

Cassandra cache store was merged into upcoming ignite-1.6 release.
ignite-1.6 is under voting process right now and may be released next week.

JIRA issue for that store: https://issues.apache.org/jira/browse/IGNITE-1371

But you may already try latest nightly build.
See https://ignite.apache.org/community/contribute.html#nightly-builds

This ignite-cassandra module is not yet documented (will be done soon), but
it has tests - you may take a look.

Hope this help.

On Thu, May 19, 2016 at 8:18 PM, ChickyDutt 
wrote:

> Hi Team,
>
> I am trying to implement cache store persistence in Cassandra. Is their
> any Cassandra specific module available off the shelf or any ignite
> provided utilities that could help me binf the two?
>
> Please let me know if you need any further information.
>
> Regards,
> Chicky D.
>
> --
> View this message in context: Persistence using Cassandra
> 
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Persistence using Cassandra

[ChickyDutt]

Hi Team,

I am trying to implement cache store persistence in Cassandra. Is their any
Cassandra specific module available off the shelf or any ignite provided
utilities that could help me binf the two?

Please let me know if you need any further information.

Regards,
Chicky D.




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

Re: AWS Autoscaling

[vdpyatkov]

Hello dilipramji,

You can use TcpDiscoveryS3IpFinder for AWS or TcpDiscoveryCloudIpFinder for
adding nodes to cluster.
Also see the articles:
https://apacheignite.readme.io/docs/aws-config
https://apacheignite.readme.io/docs/generic-cloud-configuration 


dilipramji wrote
> Hi,
> 
> Does Ignite/GridGain support auto-scaling when deploying on AWS? If not,
> can you explain how an AWS-hosted system should be architected for
> guaranteed SLA?
> 
> Thanks,
> 
> Dilip





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

Re: database caching using php

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that the community
can receive email notifications? Here is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


Jewel wrote
> I need to know how many features of apache ignite I can access using php?
> Such as Ignite for Database Caching. If I can use that then can anyone
> please send me any tutorial or an example link?

In PHP you can REST API to access the cluster. You can find the full list of
available commands here: https://apacheignite.readme.io/docs/rest-api

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/database-caching-using-php-tp5017p5029.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

read through not work

[Zhengqingzheng]

Hi  there,
I am trying to load a data record via read through method from cache.
My cache configuration set read through to true, my cache key is an object with 
5 fields, 2 of them might be null.
When I called the following functions :
IgniteCache binaryCache = 
cache.withKeepBinary();
BinaryObject v1 = binaryCache.get(key1);
I got null, (the cache is empty, however the record is ready in the database, 
it does not automatically load into cache).

When I check the log file, I notice that there is no error message, only one 
warning. The log message contains the following information:
[20:00:05,476][INFO][main][GridDiscoveryManager] Topology snapshot [ver=277, 
servers=3, clients=0, CPUs=20, heap=20.0GB]
[20:00:11,388][WARNING][main][GridDhtColocatedCache] 
 For best performance 
you should implement java.io.Externalizable for all cache keys and values: 
com.huawei.soa.ignite.model.MetaUniqueIndexKey
[20:00:11,711][INFO][main][GridTcpRestProtocol] Command protocol successfully 
stopped: TCP binary
[20:00:11,796][INFO][main][GridCacheProcessor] Stopped cache: null
[20:00:11,797][INFO][main][GridCacheProcessor] Stopped cache: 
ignite-marshaller-sys-cache
[20:00:11,797][INFO][main][GridCacheProcessor] Stopped cache: ignite-sys-cache
[20:00:11,797][INFO][main][GridCacheProcessor] Stopped cache: 
ignite-atomics-sys-cache


Anyone know what's wrong here?


Many thanks,
Kevin

Cancel tasks on Ignite compute grid worker nodes

[fs12345]

Hi all,

Let me start by saying I am quite a novice with Apache Ignite. 

Here is my question : I want to be able to monitor and cancel tasks running
or that are going to run on worker nodes of an Ignite Cluster (say for
example if one task takes too long to complete), and without using Visor. 

I tried to query all EVTS_TASK_EXECUTION events (from EventType) on all
nodes as follows:

Ignite grid = Ignition.ignite("GRID_NAME");
Collection allEvents = grid.events().remoteQuery(event -> true,0,
EventType.EVTS_TASK_EXECUTION)
for (Event evt : allEvents){
TaskEvent taskEvent = (TaskEvent) evt;
System.out.println(taskEvent);
}

Each TaskEvent,  has a taskSessionId() method, and a .node() method. It
seems that the .node() method returns the client node that originated the
task with the corresponding IgniteUuid returned by taskSessionId().

On the other hand, when looking at ClusterMetrics for worker nodes I can
retrieve the number of Jobs currently running on Worker Nodes, current CPU
load etc : 

ClusterGroup workerNodes = grid.cluster().forAttribute("ROLE","WORKER");
for(ClusterNode node : workerNodes.nodes()){
System.out.println(node.metrics().getCurrentActiveJobs());
}

How could I 
1) Cancel tasks currently being run on worker nodes (whose number are
displayed in the result of getCurrentActiveJobs()) or 
2) Cancel tasks dispatched by the clients nodes, for which I have an
IgniteUuid ,

possibly without using grid.close() or such hard methods.

Thanks for your help




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cancel-tasks-on-Ignite-compute-grid-worker-nodes-tp5027.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.