Re: Issue with Ignite + Zeppelin

Hey, Seems like Zeppelin might not be the best choice to connect to Ignite-2.0.0 . Can you suggest me what UI tool can I use to connect to Ignite that is running as a java application. -- View this message in context:

Re: SQL Syntax error in cross-cache query

i think "select id from personCache.Person p limit 5" should work. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-Syntax-error-in-cross-cache-query-tp15097p15099.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Issue with Ignite + Zeppelin

Hi, Thanks for the reply. I cannot use version lower than Ignite-2.0.0. So in that case I suppose I cannot use Zeppelin with Ignite as of now. Also as you suggested, I configured Ignite using Jdbc connection. Here are the configurations : common.max_count1000 default.driver

SQL Syntax error in cross-cache query

In ignite 2.0: when I ran those codes: SqlFieldsQuery sql = new SqlFieldsQuery("select id from \\\"personCache\\\".Person p limit 5"); I got it: "Syntax error in SQL statement "SELECT ID FROM[*] \""personCache\"".PERSON P LIMIT 5 "; What's this mistake ? thanks. -- View this message in

Re: Compute Grid Questions

Got it. Thank you. Matt On Tue, Jul 18, 2017 at 8:21 PM, vkulichenko wrote: > Matt, > > undeployTask method is about task deployment [1], it's unrelated to the > discussion. > > [1] https://apacheignite.readme.io/docs/deployment-spi > > -Val > > > > -- > View

How does node vistor task can work?

Try to fetch all nodes' statistic over the cluster but got exception: -- for (ClusterNode node : ignite.cluster().forRemotes().nodes()) { VisorGridConfiguration result =

encountering a character encoding problem when DML SQL is used

Hi guys, I am now encountering a character encoding problem when DML SQL is used. For example, if i run the DML SQL like the following sentence: update tableA set columnA="测试" and columnB="你好" where _key=1 it can works, but when i get it(_key=1) from the cache , i get the messy word. any

Multi Cloud Deployment Issue

Hi, I am trying to setup a multi-cloud cluster of Ignite 2.0 servers and facing severe issues in terms of the response time. I am running Tomcats as Ignite clients hosting my REST service. To narrow down the issue, I tried setting up the cluster in almost all permutation combinations. 1. Two

Re: Compute Grid Questions

Matt, undeployTask method is about task deployment [1], it's unrelated to the discussion. [1] https://apacheignite.readme.io/docs/deployment-spi -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Compute-Grid-Questions-tp14980p15091.html Sent from the

Re: Ignite SQL query result's metadata

Hi Menglei, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. menglei wrote > Hi, > > Currently we are heavily

Re: Problem with Visor and Cassandra Cache Store

Hi Roger, There is a bug in the code, I created a ticket: https://issues.apache.org/jira/browse/IGNITE-5781. Thanks for letting us know about the issue. -Val -- View this message in context:

Re: Compute Grid Questions

Hi Slava, I didn't know flags were cleared by *Thread.sleep()*, that makes sense now. Approach 1 in the code below works fine, but the second approach still won't interrupt a task with a given name. I'm surely missing something else. Is *ignite.compute().undeployTask(...)* supposed to work like

Re: Ignite Information

Mimmo, Can you describe the use case? What are you trying to achieve exactly? Generally, sending a lot of data across the network is something that you should avoid, of course. So it's hard to tell if your approach is correct or not without knowing all details. -Val -- View this message in

Re: java.lang.IllegalStateException: Data streamer has been closed.

Hi Zbyszek, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. zbyszek wrote > Hello All, > > I was wondering if

Ignite SQL queries's metadata

Hi all, Currently we are heavily using the standard SQL query functionality provided by Ignite. We have a lot join across the cache and need to get many columns from the query. But right now the interface of SQL resultset (QueryCursor in ignite) has limited exposure of the API, which is an

Ignite SQL queries's metadata

Hi all, Currently we are heavily using the standard SQL query functionality provided by Ignite. We have a lot join across the cache and need to get many columns from the query. But right now the interface of SQL resultset (QueryCursor in ignite) has limited exposure of the API, which is an

Re: multiple thread access in segment resolver

Sounds good, thanks Andrew for your help. On 18 Jul 2017 19:17, "Andrew Mashenkov [via Apache Ignite Users]" < ml+s70518n1508...@n6.nabble.com> wrote: Hi, Every node will have own SegmentationResolver and SegmentationProcessor instances. So, there is no need to be bothered about thread-safety.

Re: multiple thread access in segment resolver

Hi, Every node will have own SegmentationResolver and SegmentationProcessor instances. So, there is no need to be bothered about thread-safety. On Tue, Jul 18, 2017 at 8:51 PM, luqmanahmad wrote: > Hi Andrey, > > Shouldnt that need to be sync. The reason I am saying

Re: multiple thread access in segment resolver

Hi Andrey, Shouldnt that need to be sync. The reason I am saying because what happens if two server nodes are started simultaneously on the same machine or on two different machines ? I think there would be some synchronisation needed. I could be wrong but could you please confirm that for me as

Re: Inserting Data From Spark to Ignite

Please, try use other JDBC driver version. You mNge it by JDBC connections string. Checkout this article [1]. [1] https://apacheignite.readme.io/docs/jdbc-driver#jdbc-connection On Tue, Jul 18, 2017 at 7:02 PM, limabean wrote: > Here is the requested example code

Re: Issue with Ignite + Zeppelin

First of all, I don't recommend use Zeppelin 0.7.1 with Ignite 2.0 because different versions of Ignite can have some backward compatibility issues. It's very strange that you don't have any errors in logs. Could you please try other JDBC driver? See docs here [1]. [1]

Problem with Visor and Cassandra Cache Store

Hello, I am getting the following exceptions from the ignite server(s) when using the visor cache command: [10:03:36,710][SEVERE][mgmt-#415%null%][GridJobWorker] Failed to execute job due to unexpected runtime exception [jobId=c2fd5a65d51-7f82d6ed-0d7f-4cc9-a312-229ba87c8edd,

Re: Ignite2.0 Off Heap Storage

Yes, Denis you are right max size can be higher than 80%. There just should be enough memory for OS needs + JVM heap and perm (or meta) space. On Tue, Jul 18, 2017 at 7:17 PM, Denis Magda wrote: > Andrey, > > On Jul 18, 2017, at 8:37 AM, Andrey Mashenkov

Re: split-brain processors

Hi Luqman, SegmentationResolver is just an interface to user can implement custom logic, but Ignite doesn't use it at all. As Ignite doesn't provide split-brain functionality, you need to implement a GridSegmentationProcessor. So, configuration properties related to segmentation thing affect

July 19 webinar: Distributed ACID transactions in Apache® Ignite™

Igniters, Akmal B. Chaudhri will host a webinar tomorrow (July 19 at 11 a.m. Pacific time) during which he'll take attendees on a deep-dive into the Apache Ignite architecture's ACID-compliant transactional subsystem. Register here: http://bit.ly/2tCWvlL It will be recorded and that link above

Re: Ignite client not seeing cache created by server

Hi Maureen, Client and server nodes found each other and created a cluster, so it can't be possible that there're two caches in the same cluster with the same name. On client node you can check ignite.cacheNames() before cache = ignite.getOrCreateCache(cfg); call. To make sure that IMAGE_CACHE

Re: multiple thread access in segment resolver

Hi Luqman, Please, take a look at internal class GridSegmentationProcessor and where the only method isValidSegment() called from. It is called on node start from single thread and then called from one of discovery thread (SegmentCheckWorker). Seems, there is no need any sync.

Ignite client not seeing cache created by server

Hi, I am trying to use apache ignite cache for the first time. I have 2 java spring boot applications, the first one is configured as an ignite server: Snippet from ignite-config-dev.xml: And it is creating a cache on start -up: public void initCache() { Ignite ignite =

Re: CodecNotFoundException: [smallint <-> java.lang.Integer] with Cassandra

Hi, I've found that there is no Short<->SMALLINT mapping in ignite. I see only Short<->INT. Looks like a bug to me, so I've create a ticket [1]. [1] https://issues.apache.org/jira/browse/IGNITE-5779 On Fri, Jul 14, 2017 at 11:58 PM, Roger Fischer (CW) wrote: > Hello, > >

Re: Ignite2.0 Off Heap Storage

Andrey, > On Jul 18, 2017, at 8:37 AM, Andrey Mashenkov > wrote: > > By default, memory region max size is about 80% of total RAM. You are limited > only with you RAM size, but it is not recommended to set higher than default. Why is it not recommended to take

Re: java.lang.IllegalStateException: Data streamer has been closed

Thank you Mikhail, Your answer is very helpful. Just needed confirmation that this was a known issue. Regards, Zbyszek -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Data-streamer-has-been-closed-tp15061p15067.html Sent from

Re: Inserting Data From Spark to Ignite

Here is the requested example code demonstrating one of the methods that is failing to write to Ignite. The readme shows the full stack trace appearing from the app as it runs in Spark 2.1 I first run the CreateIgniteCache program and verify using a DB tool that the Cache and Table are

Re: java.lang.IllegalStateException: Data streamer has been closed

Hi, looks like you faced with the following bug: https://issues.apache.org/jira/browse/IGNITE-5195 unfortunately there's no workaround for this. Don't change cluster topology :) Thanks, Mikhail. -- View this message in context:

Re: Ignite2.0 Off Heap Storage

Hi Ajay, By default, memory region max size is about 80% of total RAM. You are limited only with you RAM size, but it is not recommended to set higher than default. Please, make sure you run x64 JVM if you want to use large memory region and JVM process needs more than 4Gb. Would you share a

Re: Ignite2.0 Off Heap Storage

Hi, Can you tell how much max off heap memory region we can start with memory policy configuration, Is their any limit to set this, because we are getting unsafe memory exception. Thanks, Ajay. -- View this message in context:

Re: Ignite2.0 Off Heap Storage

You can backport the fix to 2.0 and use your own build of ignite or wait for 2.1 release, which should be very soon. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-Off-Heap-Storage-tp15008p15062.html Sent from the Apache Ignite Users mailing list

java.lang.IllegalStateException: Data streamer has been closed

Hello All, I was wondering if anybody has encountered the following issue. I have 2 servers (Ignite 2.0.1) in the cluster. Each of these 2 servers loads different caches (with different names) in LOCAL mode using DataStreamer. I am starting these servers simultaneously (say the second server is

Re: Possible starvation in striped pool

Hi Alper, Seems, sometime stripe-pool threads stucks for awhile due to short network issues. Possibly, it happens when nodes doesn't left the grid gracefully. Try to set java.net.preferIPv4Stack=true on all nodes (incl. clients), it can help in some cases when client is droped from grid due to

Re: Ignite Information

Hi Val, Thanks for reply. We are trying to eliminate the reduce step in hadoop processing by sending each map results in a distribuited cache for minimize time of execution. Do you think it's a reasonable thing? When we send data with DataStream overwrite true through more parallel DataStreamer

Re: Issue with Ignite + Zeppelin

Hi, I am using binary release of Zeppelin-0.7.1 . Here is the cache configuration : CacheConfiguration itemCacheConfiguration = new CacheConfiguration("Item"); itemCacheConfiguration.setMemoryPolicyName(igniteProperties.getMemoryPolicyName());

Re: Compute Grid Questions

Hi Matt, It seems that your code is not quite correct. In accordance with the spec Thread.sleep(long millis) clears the interrupted status in case of InterruptedException is raised. Could you try the following implementation of IgniteRunnable? public static class MyTask implements

Re: Issue with Ignite + Zeppelin

Did you build Zeppelin from sources or use binary release? From Ignite configuration I see that you use Ignite 2.x, but still there is no Zeppelin release with Ignite 2.x. Also I asked you share cache configuration but I see only Ignite configuration. Could you please share configuration for

Re: Ignite DataStream Troughput

Hi Mikhail, Thanks for reply. I tried with set overwrite false, throughput is inscreased and time has decreased. 3 parallel DataStream 26s on 1 Server Node. We need to update the entries if we set overwrite false, so how can we do ? We need a sort of reduce job on Ignite Server, is there any

Re: Issue with Ignite + Zeppelin

Hi, When I execute the paragraph on zeppelin notebook, I get these logs in Zeppelin : INFO [2017-07-18 16:43:03,550] ({pool-2-thread-17} SchedulerFactory.java[jobStarted]:131) - Job paragraph_1500273041300_616329143 started by scheduler

Re: Issue with Ignite + Zeppelin

Hi, what about zeppelin ignite interpreter logs? At least this log should contain something helpful. Also could you please share your cache configuration? On Tue, Jul 18, 2017 at 10:33 AM, Megha Mittal wrote: > Hi, > > I am using TcpDiscoveryS3IpFinder for ip

Re: What tool is used to create diagrams in apache ignite documenation

Hi, you are right it's definitely offtopic for this mail list, I believe photoshop was used. Thanks, Mikhail. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/What-tool-is-used-to-create-diagrams-in-apache-ignite-documenation-tp15043p15050.html Sent from the

multiple thread access in segment resolver

Hi all, Let say we have a segmentation resolver named "ApplicationSegmentationResolver" which is checking about the statuses of different applications but it needs to be initialised first time. For example something like this: public ApplicationSegmentationResolver implements

Re: Ignite DataStream Troughput

Hi Mimmo, overwrite true - significantly reduce upload speed, try to avoid it. Thanks, Mikhail. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-DataStream-Troughput-tp14918p15048.html Sent from the Apache Ignite Users mailing list archive at

Re: Scheduler throwing NullPointerException for Ignite 2.0.0

Hi Raul, Please use the following link to track the issue: https://issues.apache.org/jira/browse/IGNITE-5773 Thanks, Mikhail. On Sun, Jul 16, 2017 at 6:14 PM, Raul wrote: > Hi, > > Any update on the issue? > > On 11 July 2017 at 16:01, chapurlatn wrote:

Re: Ignite2.0 Off Heap Storage

Hi, then how come to know how much data resides and how memory utilized. Because when i loaded 10 million records it was showing only 4 million records then where was the rest data. Thanks, Ajay. -- View this message in context:

Re: Issue with Ignite + Zeppelin

Hi, I am using TcpDiscoveryS3IpFinder for ip discovery of servers and client. Can this be the issue that zeppelin is not able to create the connection ? Also, for the logs on server, i get normal messages like : 2017-07-18 12:58:57,026 INFO IgniteKernal.info - FreeList [name=null, buckets=256,

Re: New blog post: Implementing Ignite.NET Plugin, interacting with Java

Good point, done. On Tue, Jul 18, 2017 at 2:35 AM, Denis Magda wrote: > Pavel, the blog post is well deserved to be mentioned on this > documentation page! > https://apacheignite-net.readme.io/docs/plugins readme.io/docs/plugins> > > Please add it