Re: Kafka Listener and Computing

[vmuthus]

Hi Val,

Thank you for the reply.

Within the grid can I start a consumer?. What is the best approach? Do I
need as startup Listener?  I do not want external process to get started for
consumer and then call the grid separately for distributed computing.

Also I can start the consumers in all nodes as well right? to have more
throughput.

Thanks
Venkat





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Listener-and-Computing-tp6891p6907.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IgniteException on starting node from Jar

[chevy]

Please find the attached config files. It is working when I run my code from 
eclipse and not through jar.
--
Regards,
Chetan.

From: "vkulichenko [via Apache Ignite Users]" 
>
Date: Wednesday, August 10, 2016 at 4:53 AM
To: "Chetan.V.Yadav" 
>
Subject: Re: IgniteException on starting node from Jar

Hi,

Spring is used under the hood when you use Spring XML to configure Ignite. 
Please attach (not copy-paste to avoid mistakes) both mpm-default.xml and 
mpm-ignite.xml files and I will try to run with them.

-Val


If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/IgniteException-on-starting-node-from-Jar-tp6881p6887.html
To unsubscribe from IgniteException on starting node from Jar, click 
here.
NAML




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteException-on-starting-node-from-Jar-tp6881p6906.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Reloading ignite configuration file

[vmuthus]

Hi Val,
Thank you.
I need to do it by programming right. In that case worst case scenario if
the entire cluster crashes then the new dynamic cache will be lost and
cannot reload right?

I am thinking building a POC with fewer number of caches and start adding
more caches into the cluster and not stopping the cluster/nodes. is there
any possibilities?
Thanks
Venkat




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

Re: Why there are no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub?

[Denis Magda]

Nick,

As far as I remember you were preparing the image for the earlier release. Can 
you do the same for both 1.6.0 and 1.7.0?
Do we have any documentation so that any from the community can perform this 
task at the end of release process?

—
Denis

> On Aug 9, 2016, at 9:39 PM, Valentin Kulichenko 
>  wrote:
> 
> Crossposting to dev list.
> 
> Igniters,
> 
> Is there anyone who can create image for the recently released 1.7?
> 
> -Val
> 
> On Sat, Aug 6, 2016 at 2:18 PM, zshamrock  > wrote:
> Why there is no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub
> https://hub.docker.com/r/apacheignite/ignite/tags/ 
> ?
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Why-there-are-no-official-1-6-0-and-1-7-0-ignite-docker-images-on-Docker-Hub-tp6832.html
>  
> 
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> 

Re: Why there are no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub?

[Valentin Kulichenko]

Crossposting to dev list.

Igniters,

Is there anyone who can create image for the recently released 1.7?

-Val

On Sat, Aug 6, 2016 at 2:18 PM, zshamrock 
wrote:

> Why there is no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub
> https://hub.docker.com/r/apacheignite/ignite/tags/?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Why-there-are-no-official-1-6-0-and-1-7-
> 0-ignite-docker-images-on-Docker-Hub-tp6832.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Timings for a weighted average computation

[vkulichenko]

This is a duplicate of this thread:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-td6703.html

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Timings-for-a-weighted-average-computation-tp6670p6901.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: [Ignite 1.6.0 .net version]When on server node failed, the PutAll in all the client nodes hang

[vkulichenko]

Hi Jason,

Do you still have this issue? If yes, I would try the latest 1.7 and see if
it changes anything.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-net-version-When-on-server-node-failed-the-PutAll-in-all-the-client-nodes-hang-tp6642p6900.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: How is memory used for the Ignite server node?

[vkulichenko]

Hi Jason,

Provided capacity planning guide can give you rough estimate to start with
and you will have to test case by case after that. I actually think it's way
more risky if you don't do that.

As for the memory consumed by process, remember that both JVM and CLR are
managing their own memory, so it can actually be consumed by temporary
object that are not GCed yet, for example. It also depends on what kind of
load you create on the cluster (only cache, compute, etc.). Generally I
recommend at least 4GB heap memory in case the data is off-heap. If you
don't experience OOM errors or GC pauses, you're good.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-is-memory-used-for-the-Ignite-server-node-tp6626p6899.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Ignite worth using in its current state in production? Is it mature enough?

[vkulichenko]

Hi Jason,

I will not be able to tell you all the details, but this was a IoT use case
which doesn't require a lot of memory and doesn't store a lot of data in
memory, but has strict SLAs on throughput and latency under load. Each
incoming event triggered 2-3 atomic cache operations (get/put/invoke).
Updates were persisted to Cassandra using write-through.
In the benchmark we were running, the whole system was able to process
million events per seconds. I don't remember the numbers for latency, but
they were within production SLAs.

As for the large clusters, I recommend to try it and see how it behaves in
production environment. You can also refer to this page for some tuning
tips: https://apacheignite.readme.io/docs/preparing-for-production

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Is-Ignite-worth-using-in-its-current-state-in-production-Is-it-mature-enough-tp6748p6898.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Kafka Listener and Computing

[vkulichenko]

Hi Venkat,

You can also use Compute Grid [1] directly. I.e., create a Kafka consumer
that will execute closures or tasks on the grid. Caches are not needed with
this approach.

[1] https://apacheignite.readme.io/docs/compute-grid

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Listener-and-Computing-tp6891p6896.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: how async support can improve read and write performance

[vkulichenko]

Pipelined method looks like a simple batching. In Ignite you can do the same
with putAll() and getAll() which will minimize the number of network
messages where possible. For loading large amounts of data you can also use
data streamer:
https://apacheignite.readme.io/docs/data-streamers#ignitedatastreamer

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/how-async-support-can-improve-read-and-write-performance-tp6894p6895.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

how async support can improve read and write performance

[shirely]

Well, I am testing the read and write performance between ignite and redis. I
found that redis has a pipelined method that improve performance a lot. Is
there anything like redis pipelined in ignite??  I tried async but the
performance didn't change, maybe there is something wrong? would you please
give me some suggestions ?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/how-async-support-can-improve-read-and-write-performance-tp6894.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster node stopped

[suhuadong]

Hello,

Sorry,I don't  describe clearly. 
My cluster stop many times.
The topology destruction take place at 22:03:38,But I attach log files don't 
contain it.
The topology destruction take place at 21:26:55,I attach log files contain
it.

The stoped server node's ip is 172.21.0.183.
The stoped server node's id is ac184004.

The topology destruction take place at 21:26:55 in
ignite-ac184004.0.log-172.21.0.183.
ignite-ac184004.0.log-172.21.0.183：

[21:26:55,427][WARNING][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Node
is out of topology (probably, due to short-time network problems).
[21:26:55,430][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Local node SEGMENTED: TcpDiscoveryNode
[id=ac184004-f488-40be-9dd5-dc54632bcbbe, addrs=[124.250.36.149, 127.0.0.1,
172.21.0.183], sockAddrs=[/172.21.0.183:58600, /124.250.36.149:58600,
/124.250.36.149:58600, /127.0.0.1:58600, /172.21.0.183:58600],
discPort=58600, order=526, intOrder=275, lastExchangeTime=1470144415424,
loc=true, ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,466][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Stopping local node according to configured segmentation policy.
[21:26:55,467][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=588dbb39-a124-4879-a476-3bb723e1e4d9,
addrs=[124.250.36.148, 127.0.0.1, 172.21.0.182],
sockAddrs=[/124.250.36.148:58600, /124.250.36.148:58600,
/124.250.36.148:58600, /127.0.0.1:58600, /172.21.0.182:58600],
discPort=58600, order=244, intOrder=132, lastExchangeTime=1470103699289,
loc=false, ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,470][INFO][disco-event-worker-#144%null%][GridDiscoveryManager]
Topology snapshot [ver=567, servers=1, clients=0, CPUs=32, heap=60.0GB]
[21:26:55,471][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=ea39b0d0-fb6b-483b-86d5-d2cfda7c0abf,
addrs=[127.0.0.1, 172.21.0.39], sockAddrs=[/172.21.0.39:58600,
/127.0.0.1:58600, /172.21.0.39:58600], discPort=58600, order=251,
intOrder=136, lastExchangeTime=1470103699833, loc=false,
ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,473][INFO][Thread-69][GridTcpRestProtocol] Command protocol
successfully stopped: TCP binary
[21:26:55,474][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=51421fee-0d08-4f46-82ea-1a12f8d80f6f,
addrs=[127.0.0.1, 172.21.0.40], sockAddrs=[/172.21.0.40:58600,
/127.0.0.1:58600, /172.21.0.40:58600], discPort=58600, order=257,
intOrder=139, lastExchangeTime=1470103699833, loc=false,
ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,475][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=14d75a27-f8ae-4da6-9285-f6b6abfe645c,
addrs=[127.0.0.1, 172.21.0.41], sockAddrs=[/172.21.0.41:58600,
/127.0.0.1:58600, /172.21.0.41:58600], discPort=58600, order=263,
intOrder=142, lastExchangeTime=1470103699833, loc=false,
ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,475][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=2333a45f-4d81-423d-90fe-445efc233883,
addrs=[127.0.0.1, 172.21.0.42], sockAddrs=[/172.21.0.42:58600,
/127.0.0.1:58600, /172.21.0.42:58600], discPort=58600, order=265,
intOrder=143, lastExchangeTime=1470103699833, loc=false,
ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,476][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=f67c2596-bf28-41d5-b79d-7e351b72768f,
addrs=[127.0.0.1, 172.21.0.43], sockAddrs=[/172.21.0.43:58600,
/127.0.0.1:58600, /172.21.0.43:58600], discPort=58600, order=267,
intOrder=144, lastExchangeTime=1470103699833, loc=false,
ver=1.6.0#20160518-sha1:0b22c45b, isClient=false]
[21:26:55,477][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=ddcbfdba-cf93-415c-a914-e84ac729ccc4,
addrs=[124.250.36.139, 127.0.0.1, 172.21.0.173],
sockAddrs=[/124.250.36.139:0, /124.250.36.139:0, /124.250.36.139:0,
/127.0.0.1:0, /172.21.0.173:0], discPort=0, order=299, intOrder=160,
lastExchangeTime=1470103699833, loc=false, ver=1.6.0#20160518-sha1:0b22c45b,
isClient=true]
[21:26:55,478][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=36e21ab4-2d96-4e22-8496-755ae90253ba,
addrs=[124.250.36.70, 124.250.36.74, 127.0.0.1, 172.21.0.77],
sockAddrs=[/124.250.36.70:0, /124.250.36.70:0, /124.250.36.74:0,
/124.250.36.74:0, /127.0.0.1:0, /127.0.0.1:0, /172.21.0.77:0], discPort=0,
order=307, intOrder=164, lastExchangeTime=1470103700085, loc=false,
ver=1.6.0#20160518-sha1:0b22c45b, isClient=true]
[21:26:55,478][WARNING][disco-event-worker-#144%null%][GridDiscoveryManager]
Node FAILED: TcpDiscoveryNode [id=048e6c2a-7520-4197-8074-a65beefac047,
addrs=[124.250.36.73, 124.250.36.74, 127.0.0.1, 172.21.0.80],
sockAddrs=[/124.250.36.73:0, /124.250.36.73:0, /124.250.36.73:0,

Kafka Listener and Computing

[vmuthus]

 We are trying t find a write platofrm to do realtime data processing in
memory.
Need few suggestions.

Our Data is cached in the grid. for our request I need the listener part of
the same Ignite Grid listening to a Kafka topic and process the message and
compute certain task.
How do I do it.

I do not want to update the cache just od the computation for every kafka
message and spit the output to another queue. Also I want the same Grid will
do the computation without creating client node/process.

Any help is appreciated.

Thanks
Venkat




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Kafka-Listener-and-Computing-tp6891.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cannot get cache through the REST API

[vkulichenko]

Hi Yuci,

What's your use case? Trying to get data directly from cache when you're
using web session clustering sounds weird to me. What's the reason for that?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p6890.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite RDD Map Reduce function

[vkulichenko]

Hi,

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


pmazumdar wrote
> Can someone please provide an example as to how to use map and reduce
> functions of ignite RDD (used with Spark)? I want to calculate weighted
> average on the data that resides on ignite cache using ignite RDD. i.e.
> 
> IgniteRDDDouble, Double igniteRDD =
> ic.fromCache(CacheConfig.partitionedCache());
> 
> I now want to use Map and Reduce functions on igniteRDD to calculate
> weighted average. Could someone please assist?

IgniteRDD extends standard Spark RDD, so all APIs are available. You can use
standard map() and reduce() functions, as well as all others.

In some cases you can speed up the process using SQL queries that you can
run directly against data in Ignite using IgniteRDD.sql() method. See
details here:
https://apacheignite-fs.readme.io/docs/ignitecontext-igniterdd#section-running-sql-queries-against-ignite-cache

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-RDD-Map-Reduce-function-tp6880p6888.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reloading ignite configuration file

[vmuthus]

Once I start my ignite nodes/cluseter
for example 
"ignite examples/config/example-cache.xml"

is there a way I can modify the example-cache.xml file adding more cache
bean entries and the ignite reloads it automatically?

Thanks
Venkat Muthusamy 



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

Re: IgniteException on starting node from Jar

[vkulichenko]

Hi,

Spring is used under the hood when you use Spring XML to configure Ignite.
Please attach (not copy-paste to avoid mistakes) both mpm-default.xml and
mpm-ignite.xml files and I will try to run with them.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteException-on-starting-node-from-Jar-tp6881p6887.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: yarn deployment

[Nikolai Tikhonov]

Hi,

YARN could not download Ignite build. It's might be related with
configuration your access to internet.

You can configure IGNITE_PATH property. In this case ignite yarn will take
a apache ignite build from hdfs [1].

[1] http://apacheignite.gridgain.org/v1.6/docs/yarn-deployment

On Tue, Aug 9, 2016 at 10:54 PM, prasanth  wrote:

> bump...
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/yarn-deployment-tp6843p6885.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: yarn deployment

[prasanth]

bump...



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

Re: IgniteException on starting node from Jar

[Vladislav Pyatkov]

Hello,

If you do not use Spring, you can not use xml configuration.
Configure Ignite programmatically (through java code).
See here [1] on Java tab.
Also, look at the method
Ignition#start(org.apache.ignite.configuration.IgniteConfiguration)

[1]
https://apacheignite.readme.io/docs/clients-vs-servers#configuring-clients-and-servers


On Tue, Aug 9, 2016 at 6:15 PM, chevy  wrote:

> I am not using spring framework for my code and it is in plain Java. So, I
> do
> not have any spring version to specify explicitly. Also, how can i make my
> code use config inside jar rather than pick it from $IGNITE_HOME?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/IgniteException-on-starting-
> node-from-Jar-tp6881p6883.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Re: IgniteException on starting node from Jar

[chevy]

I am not using spring framework for my code and it is in plain Java. So, I do
not have any spring version to specify explicitly. Also, how can i make my
code use config inside jar rather than pick it from $IGNITE_HOME?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteException-on-starting-node-from-Jar-tp6881p6883.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IgniteException on starting node from Jar

[Alisher Alimov]

Hi!

Current problem doesn’t related to Ignite, I think that problem in spring, 
check your spring version and try to specify version of spring-beans schema 
directly (ex. spring-beans-3.1.xsd )


With best regards
Alisher Alimov
alimovalis...@gmail.com




> On 9 авг. 2016 г., at 17:39, chevy  wrote:
> 
> Hi,
> 
> When I start ignite node from my eclipse IDE it starts without any issues
> but when I export my code to jar and execute the code, I get below mentioned
> error. I am using same config even when I am running directly from IDE.
> 
> Error:
> 
> Exception in thread "main" class org.apache.ignite.IgniteException: Failed
> to instantiate Spring XML application context
> [springUrl=file:/opt/ignite/apache-ignite-fabric-1.6.0-bin/config/mpm-ignite.xml,
> err=Line 9 in XML document from URL
> [file:/opt/ignite/apache-ignite-fabric-1.6.0-bin/config/mpm-ignite.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 9;
> columnNumber: 72; cvc-elt.1: Cannot find the declaration of element
> 'beans'.]
> 
> 
> Config:
> 
> 
> 
> 
> http://www.springframework.org/schema/beans;
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd;>
> 
>
> 
>
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/IgniteException-on-starting-node-from-Jar-tp6881.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.



signature.asc
Description: Message signed with OpenPGP using GPGMail

IgniteException on starting node from Jar

[chevy]

Hi,

 When I start ignite node from my eclipse IDE it starts without any issues
but when I export my code to jar and execute the code, I get below mentioned
error. I am using same config even when I am running directly from IDE.

Error:

Exception in thread "main" class org.apache.ignite.IgniteException: Failed
to instantiate Spring XML application context
[springUrl=file:/opt/ignite/apache-ignite-fabric-1.6.0-bin/config/mpm-ignite.xml,
err=Line 9 in XML document from URL
[file:/opt/ignite/apache-ignite-fabric-1.6.0-bin/config/mpm-ignite.xml] is
invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 9;
columnNumber: 72; cvc-elt.1: Cannot find the declaration of element
'beans'.]


Config:




http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd;>









--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IgniteException-on-starting-node-from-Jar-tp6881.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Address bind error

[Alisher Alimov]

Hi!

Ignite uses Jetty server to provide HTTP Rest API and seems that you bind 
Ignite REST server on same port as Tomcat

You can find more information about it here: 
http://apacheignite.gridgain.org/docs/configuration

With best regards
Alisher Alimov
alimovalis...@gmail.com




> On 9 авг. 2016 г., at 15:59, Ravi Puri  wrote:
> 
> I got the below error as i am running tomcat server at localhost and also the
> ignite-config.xml at same host. is this the problem due to this? or is it
> something error not related to i mentioned above??
> 
> 
> 
> 
> WARNING: FAILED ServerConnector@e11eade{HTTP/1.1}{0.0.0.0:8080}:
> java.net.BindException: Address already in use: bind
> java.net.BindException: Address already in use: bind
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
>   at 
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
>   at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
>   at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
>   at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>   at org.eclipse.jetty.server.Server.doStart(Server.java:366)
>   at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>   at
> org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.startJetty(GridJettyRestProtocol.java:220)
>   at
> org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.start(GridJettyRestProtocol.java:177)
>   at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.startProtocol(GridRestProcessor.java:861)
>   at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.startHttpProtocol(GridRestProcessor.java:832)
>   at
> org.apache.ignite.internal.processors.rest.GridRestProcessor.start(GridRestProcessor.java:447)
>   at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1518)
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Address-bind-error-tp6878.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Address bind error

[Ravi Puri]

I got the below error as i am running tomcat server at localhost and also the
ignite-config.xml at same host. is this the problem due to this? or is it
something error not related to i mentioned above??




WARNING: FAILED ServerConnector@e11eade{HTTP/1.1}{0.0.0.0:8080}:
java.net.BindException: Address already in use: bind
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at 
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.startJetty(GridJettyRestProtocol.java:220)
at
org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.start(GridJettyRestProtocol.java:177)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.startProtocol(GridRestProcessor.java:861)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.startHttpProtocol(GridRestProcessor.java:832)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.start(GridRestProcessor.java:447)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1518)



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

答复: ignite client cannot connect problem

[Zhengqingzheng]

Hi Vladislav Pyatkov,
I am still using  ignite1.5.0.final。
I will try 1.7.0

Best wishes,
Kevin

发件人: Vladislav Pyatkov [mailto:vldpyat...@gmail.com]
发送时间: 2016年8月9日 17:22
收件人: user@ignite.apache.org
主题: Re: ignite client cannot connect problem

Hello,

Please clarify what version of Apache Ignite do you use?
At first glance, it will not reproduce in version 1.7.

On Tue, Aug 9, 2016 at 11:29 AM, Zhengqingzheng 
> wrote:
Hi there,
When I start my ignite client, I got the following message:
[15:59:04,435][ERROR][tcp-client-disco-msg-worker-#4%127.0.0.1%][TcpDiscoverySpi]
 Runtime error caught during grid runnable execution: IgniteSpiThread 
[name=tcp-client-disco-msg-worker-#4%127.0.0.1%]
java.lang.AssertionError
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.updateMetrics(ClientImpl.java:2012)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processHeartbeatMessage(ClientImpl.java:1895)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1558)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1477)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
~

And there is no more info show in the log file, any idea what’s going on ?

I followed into the core code and find that this is due to an assertion check 
failed:
/**
 * @param nodeId Node ID.
 * @param metrics Metrics.
 * @param cacheMetrics Cache metrics.
 * @param tstamp Timestamp.
 */
private void updateMetrics(UUID nodeId,
ClusterMetrics metrics,
Map cacheMetrics,
long tstamp)
{
assert nodeId != null;
assert metrics != null;
assert cacheMetrics != null;
….
Which is called from  private void 
processHeartbeatMessage(TcpDiscoveryHeartbeatMessage msg),
TcpDiscoveryHeartbeatMessage should contains cacheMetrics initialization.
But failed on my client side.

My ignite configuration is defined as:
 TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(false);

List addrs = new ArrayList();
 addrs.add(IGNITE_NEW_ADDRESS);
ipFinder.setAddresses(addrs);
TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
discoverySpi.setIpFinder(ipFinder);
discoverySpi.setLocalPort(ThreadLocalRandom.current().nextInt(48500,
48520 + 1));
discoverySpi.setJoinTimeout(3);
discoverySpi.setSocketTimeout(3);
   igniteCCF.setDiscoverySpi(discoverySpi);

TcpCommunicationSpi commSpi = new TcpCommunicationSpi();

commSpi.setSharedMemoryPort(-1);
commSpi.setLocalPort(ThreadLocalRandom.current().nextInt(49530,
49550 + 1));
igniteCCF.setCommunicationSpi(commSpi);
// create ignite instance
ignite = Ignition.start(igniteCCF);

Any configuration I should change? Or add?

Best regards,
Kevin



--
Vladislav Pyatkov

Re: Cannot get cache through the REST API

[yucigou]

Hi Saikat,

Thanks for your kind input. But there is no luck yet. I guess that in order
to runs sql fields query over cache, you need to make fields visible for sql
queries first. But in my case, the session objects are not annotated with
@QuerySqlField

Furthermore, I got the following error message:

{
  "error": "Indexing is disabled for cache: session-cache. Use
setIndexedTypes or setTypeMetadata methods on CacheConfiguration to
enable.",
  "response": null,
  "sessionToken": "",
  "successStatus": 1
}

Also not very sure of how setIndexedTypes works for Ignite web session
clustering.

Cheers,
Yuci



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p6875.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cannot get cache through the REST API

[yucigou]

Hi Val,

Thanks for the reply. But I found all cache related APIs (e.g., commands
getall, get) require a key parameter. The issue is how I would be able to
find out the keys in the first place? Is there any API that can list all the
keys of a particular cache?

By the way, I guess session IDs may be used as the keys, and so I tried
using a session ID as the key for command getall:

http://ves-hx-40.ebi.ac.uk:8574/ignite?cmd=getall=C1B28644177A7917C8841204F2D2=session-cache

I got the response, but no value was returned:

{
  "affinityNodeId": "",
  "error": "",
  "response": {
"C1B28644177A7917C8841204F2D2": {}
  },
  "sessionToken": "",
  "successStatus": 0
}

Any comments please?

Cheers,
Yuci



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p6874.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Stored Procedure

[kvipin]

Hi Val,

thanks for the answer. It seems that OFFSET and LIMIT duo is more general
and powerful than FIRST keyword alone.


thanks & regards,



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

Re: Ignite Cluster node stopped

[Vladislav Pyatkov]

Hello,

Ok, the topology destruction take place at 22:03:38, but I do not see any
rows at the time. Not in GC (172.21.0.183-gc.log) as not
ignite-ac184004.0.log-172.21.0.183. Also, I can not find a needed logs in
other files.

The logs need for investigation and understanding what to do next.
Please, check (by timestamp) what all file contains rows where is there
issue.
Can you  attach need a log files?

On Tue, Aug 9, 2016 at 4:26 AM, suhuadong  wrote:

> hi,
> Gc logs from all nine node.
>
> http://apache-ignite-users.70518.x6.nabble.com/file/n6758/gc-logs.bz2
> Ignite logs from all nine node.
>
> http://apache-ignite-users.70518.x6.nabble.com/file/n6757/ignite-logs.bz2
>
> I allocate 60g memory to jvm, jvm used memory is about 30g.
>
> My JVM_OPTS：
> -server -Xms60g -Xmx60g -Djava.net.preferIPv4Stack=true -XX:+UseG1GC
> -XX:MaxGCPauseMillis=500 -XX:InitiatingHeapOccupancyPercent=30
> -XX:ConcGCThreads=8 -XX:+UseTLAB -XX:+DisableExplicitGC -XX:+PrintGCDetails
> -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles=100 -XX:GCLogFileSize=100M
> -Xloggc:/data/ignite-1.6/gc/logs/log.txt
>
> My ignite config file:
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>
>  class="org.apache.ignite.cache.store.cassandra.
> datasource.PlainCredentials">
> 
> 
> 
>  class="com.datastax.driver.core.policies.RoundRobinPolicy"/>
> 
> class="org.apache.ignite.cache.store.cassandra.persistence.
> KeyValuePersistenceSettings">
> 
> value="classpath:com/yiche/abraham/domain/persistence-device.xml"/>
> 
> 
> class="org.apache.ignite.cache.store.cassandra.persistence.
> KeyValuePersistenceSettings">
> 
> value="classpath:com/yiche/abraham/domain/persistence-click.xml"/>
> 
> 
> class="org.apache.ignite.cache.store.cassandra.persistence.
> KeyValuePersistenceSettings">
> 
> value="classpath:com/yiche/abraham/domain/persistence-idfa.xml"/>
> 
>
>  class="org.apache.ignite.cache.store.cassandra.datasource.DataSource">
> 
>
> 
> 
> 172.21.0.177
> 172.21.0.178
> 172.21.0.179
> 172.21.0.180
> 
> 
> 
> 
> 
> 
>
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
> 
>
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
>
>  value="PRIMARY_SYNC"/>
>
> 
> 
> 
> 
> 
> 
>
>  class="org.apache.ignite.cache.store.cassandra.
> CassandraCacheStoreFactory">
>  value="cassandraRegularDataSource"/>
>  value="device_persistence_settings"/>
> 
> 
>
> 
> 
>
>  class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>
> 
> 
> 
>
> 
>
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
>
> 
> 
>
>  class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>
> 
> 
> 
>
>
>  value="PRIMARY_SYNC"/>
>
> 
> 
> 
>
> 
> 
> 
>
>  class="org.apache.ignite.cache.store.cassandra.
> CassandraCacheStoreFactory">
>  value="cassandraRegularDataSource"/>
>  value="click_persistence_settings"/>
> 
> 
>
> 
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
>
> 
> 
>
>  class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>
> 
> 
> 
>
>
>
>  value="PRIMARY_SYNC"/>
> 
> 
> 
>
> 
> 
> 
>
>  class="org.apache.ignite.cache.store.cassandra.
> CassandraCacheStoreFactory">
>  value="cassandraRegularDataSource"/>
>

Re: ignite client cannot connect problem

[Vladislav Pyatkov]

Hello,

Please clarify what version of Apache Ignite do you use?
At first glance, it will not reproduce in version 1.7.

On Tue, Aug 9, 2016 at 11:29 AM, Zhengqingzheng 
wrote:

> Hi there,
>
> When I start my ignite client, I got the following message:
>
> [15:59:04,435][ERROR][tcp-client-disco-msg-worker-#4%127.0.0.1%][TcpDiscoverySpi]
> Runtime error caught during grid runnable execution: IgniteSpiThread
> [name=tcp-client-disco-msg-worker-#4%127.0.0.1%]
>
> java.lang.AssertionError
>
> at org.apache.ignite.spi.discovery.tcp.ClientImpl$
> MessageWorker.updateMetrics(ClientImpl.java:2012)
>
> at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.
> processHeartbeatMessage(ClientImpl.java:1895)
>
> at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.
> processDiscoveryMessage(ClientImpl.java:1558)
>
> at org.apache.ignite.spi.discovery.tcp.ClientImpl$
> MessageWorker.body(ClientImpl.java:1477)
>
> at org.apache.ignite.spi.IgniteSpiThread.run(
> IgniteSpiThread.java:62)
>
> ~
>
>
>
> And there is no more info show in the log file, any idea what’s going on ?
>
>
>
> I followed into the core code and find that this is due to an assertion
> check failed:
>
> /**
>
>  * @param nodeId Node ID.
>
>  * @param metrics Metrics.
>
>  * @param cacheMetrics Cache metrics.
>
>  * @param tstamp Timestamp.
>
>  */
>
> private void updateMetrics(UUID nodeId,
>
> ClusterMetrics metrics,
>
> Map cacheMetrics,
>
> long tstamp)
>
> {
>
> assert nodeId != null;
>
> assert metrics != null;
>
> assert cacheMetrics != null;
>
> ….
>
> Which is called from  private void 
> processHeartbeatMessage(TcpDiscoveryHeartbeatMessage
> msg),
>
> TcpDiscoveryHeartbeatMessage should contains cacheMetrics initialization.
>
> But failed on my client side.
>
>
>
> My ignite configuration is defined as:
>
>  TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(false);
>
>
>
> List addrs = new ArrayList();
>
>  addrs.add(IGNITE_NEW_ADDRESS);
>
> ipFinder.setAddresses(addrs);
>
> TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
>
> discoverySpi.setIpFinder(ipFinder);
>
> discoverySpi.setLocalPort(ThreadLocalRandom.current().
> nextInt(48500,
>
> 48520 + 1));
>
> discoverySpi.setJoinTimeout(3);
>
> discoverySpi.setSocketTimeout(3);
>
>igniteCCF.setDiscoverySpi(discoverySpi);
>
>
>
> TcpCommunicationSpi commSpi = new TcpCommunicationSpi();
>
>
>
> commSpi.setSharedMemoryPort(-1);
>
> commSpi.setLocalPort(ThreadLocalRandom.current().nextInt(49530,
>
> 49550 + 1));
>
> igniteCCF.setCommunicationSpi(commSpi);
>
> // create ignite instance
>
> ignite = Ignition.start(igniteCCF);
>
>
>
> Any configuration I should change? Or add?
>
>
>
> Best regards,
>
> Kevin
>



-- 
Vladislav Pyatkov

ignite client cannot connect problem

[Zhengqingzheng]

Hi there,
When I start my ignite client, I got the following message:
[15:59:04,435][ERROR][tcp-client-disco-msg-worker-#4%127.0.0.1%][TcpDiscoverySpi]
 Runtime error caught during grid runnable execution: IgniteSpiThread 
[name=tcp-client-disco-msg-worker-#4%127.0.0.1%]
java.lang.AssertionError
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.updateMetrics(ClientImpl.java:2012)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processHeartbeatMessage(ClientImpl.java:1895)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1558)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1477)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
~

And there is no more info show in the log file, any idea what's going on ?

I followed into the core code and find that this is due to an assertion check 
failed:
/**
 * @param nodeId Node ID.
 * @param metrics Metrics.
 * @param cacheMetrics Cache metrics.
 * @param tstamp Timestamp.
 */
private void updateMetrics(UUID nodeId,
ClusterMetrics metrics,
Map cacheMetrics,
long tstamp)
{
assert nodeId != null;
assert metrics != null;
assert cacheMetrics != null;

Which is called from  private void 
processHeartbeatMessage(TcpDiscoveryHeartbeatMessage msg),
TcpDiscoveryHeartbeatMessage should contains cacheMetrics initialization.
But failed on my client side.

My ignite configuration is defined as:
 TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(false);

List addrs = new ArrayList();
 addrs.add(IGNITE_NEW_ADDRESS);
ipFinder.setAddresses(addrs);
TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
discoverySpi.setIpFinder(ipFinder);
discoverySpi.setLocalPort(ThreadLocalRandom.current().nextInt(48500,
48520 + 1));
discoverySpi.setJoinTimeout(3);
discoverySpi.setSocketTimeout(3);
   igniteCCF.setDiscoverySpi(discoverySpi);

TcpCommunicationSpi commSpi = new TcpCommunicationSpi();

commSpi.setSharedMemoryPort(-1);
commSpi.setLocalPort(ThreadLocalRandom.current().nextInt(49530,
49550 + 1));
igniteCCF.setCommunicationSpi(commSpi);
// create ignite instance
ignite = Ignition.start(igniteCCF);

Any configuration I should change? Or add?

Best regards,
Kevin

Re: Getting exception in SQL Query JOINS

[begineer]

Thanks it worked 
I changed my code as below 
query1.setArgs(new Object[] {args1.toArray()});



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

Re: SQLQuery JOIN does not accept multiple parameters in list/array as placeholder.

[begineer]

Thanks It worked !



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/SQLQuery-JOIN-does-not-accept-multiple-parameters-in-list-array-as-placeholder-tp6837p6868.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.