Ignite start-up connection timeout?

Hi, Start ignite times wrong. How to solve? How to achieve more than 3 cache query? Please help me. Thank you very much! [29 09:40:49,277 DEBUG] [localhost-startStop-1] multicast.TcpDiscoveryMulticastIpFinder - Address receive timeout. [29 09:40:50,203 DEBUG] [tcp-disco-msg-worker-#2%null%]

Re: Non-cluster mode

Peter, This doesn't make much sense to me. With OFFHEAP_TIERED eviction policy should not change anything at all, so it sounds like misconfiguration. Can you provide the whole test that I can run and investigate? -Val -- View this message in context:

Continuous Query

Hi There, I am using Continuous Query mechanism and most of the time it works just fine. However, in some cases, it seems intermittently, CQ does not pick up the update in the cache where it should. Could you please clarify the behaviour of Continuous Query in the following scenario: My

Re: Re: argument type mismatch of oracle TIMESTAMP field when call loadCache

sorry, the infomation is not in detail. My ignite's version is new release version: 1.6. 胡永亮 Bob From: Vasiliy Sisko Date: 2016-06-28 19:18 To: user@ignite.apache.org Subject: Re: Re: argument type mismatch of oracle TIMESTAMP field when call loadCache Hello Bob. What version of Ignite

Re: Non-cluster mode

Hi Val, without the eviction policy, the setup breaks due to java.lang.OutOfMemoryError: GC overhead limit exceeded I'm not sure why the heap grows (+ it looks like GC can't free it), in case of the mentioned (off-heap) config. In the end almost everything should be stored off-heap. However,

Re: Non-cluster mode

Peter, The only configuration that defines whether nodes join topology or not is discovery SPI (the one you provided in the first message) All looks fine, expect that eviction policy will be ignored in your case. It's used for entries that are stored in heap memory, while your cache is

Re: Ignite & Kubernetes

Paulo, would you like to contribute this to Ignite? On Tue, Jun 28, 2016 at 11:43 AM, Paulo Pires wrote: > I came up with https://github.com/pires/apache-ignite-discovery-kubernetes > . > > I have been using this in production Kubernetes. Obviously, one needs DNS >

Re: Ignite & Kubernetes

I came up with https://github.com/pires/apache-ignite-discovery-kubernetes. I have been using this in production Kubernetes. Obviously, one needs DNS integration which happens to be a best-practice anyway. Pires On Thu, Apr 28, 2016 at 4:45 PM Dmitriy Setrakyan wrote: >

Re: Problem with installing ODBC Driver

It works, thank you! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Problem-with-installing-ODBC-Driver-tp5914p5975.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Non-cluster mode

Hi Val, thank you for checking it! I've switched to JDK8 and the issue disappeared. I've to test it with the JDK version we need to use in production. It would be great to hear whether there is a different approach to reach the same or if it could be a side-effect due to the used config:

Re: Non-cluster mode

Hi Peter, Your code works fine for me. Can you please attach the log file? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Non-cluster-mode-tp5959p5971.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Problem with installing ODBC Driver

I tried but it doesn't work, with local Ignite node started manually nor when it is stopped. Ignite log shows nothing, I believe ODBC didn't even start Ignite. We use Tableau 9.3.3 64-bit Here is Tableau error message:/ Failed to establish connection with the host. Unable to connect to the server

Re: ignite group indexing not work problem

Hi, I've tried the provided sample and found what instead of using oId_fNum_num index H2 engine prefers oId_fNum_date, thus preventing condition on num field to use index. I think it's incorrect behavior. Could you disable oId_fNum_date, execute the query again and provide me with the query

Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance)

Denis, is it ok to delete this file while the cluster is up? or this folder? servers and clietns might be connected to it. I posted another question for the community trying to understand the use of the work directory. Could you please respond to that? This lock.file has not been updated since

Re: Problem with installing ODBC Driver

vinisman wrote > Igor, now i successfully build a driver and run ODBC examples. But the > next step i need to plug Tableau Desktop to Apache Ignite. Tableau can do > it only with the help of DSN. Is it possible to tune Windows DSN in proper > way ? I believe you can connect Tableau to Ignite

Re: SQL Query on REST APIs

Hi, Francesco. Please properly subscribe to the user mailing list so community members can see your questions as soon as possible and provide answers on them quicker. All you need to do is send an email to user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. How many

Re: Strange collocated distributed set behavior

Thank you, Andrey. I will be monitoring the progress of this issue. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Strange-collocated-distributed-set-behavior-tp5643p5963.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Problem with curator-framework package when running spark job on Ignite

Hi, Please double check that you moved all ZooKeeper module related libs from “{apache_build}/libs/optional/ignite-zookeper” into “{apache_build}/libs/“ and start the nodes using ignite.sh using your configuration. If you start the nodes from IDEA please make sure that there are no any curator

Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance)

Barrett, The data streamer is designed for caches preloading. There are no any serious issues related to it that prevents from using it in production. If you have one please share more details. — Denis > On Jun 27, 2016, at 1:46 AM, Barrett Strausser wrote: > >

Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance)

Binti, As I see from the thread dumps the node is not stopped because the following shmem related Thread is trying to acquire a lock preventing the node from finalization "ipc-shmem-gc-#24%DataGridServer-Production%" prio=10 tid=0x7f2124cc4000 nid=0x12cc05 sleeping[0x7f20fd435000]

Non-cluster mode

Hello Ignite-Community! As a part of an evaluation of Ignite 1.6, I'm trying to use Ignite in a cluster *without* cluster-mode. It should be used as local cache (independent of the other nodes). Therefore, the (Ignite-)nodes shouldn't try to discover other (Ignite-)nodes. I tried

Re: How to use rest api to put an object into cache?

Hi Kevin, Yes, currently REST protocol interpret everything as String. At this moment you can use *ConnectorMessageInterceptor *interface. Once you implement and configure it, you will start receiving callback for all keys and values passed back and forth. So you can encode you object as a String

Web Console Beta 2 release

Igniters! I'd like to announce that we just pushed Ignite Web Console Beta 2 to master branch and deployed new version at https://console.gridgain.com NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web Console. What's new: - Implemented Monitoring of grid and caches

Re: DataStreamer hanging

Hi, Please properly subscribe to the user list so that we can see your questions as soon as possible and provide answers on them quicker. All you need to do is send an email to ì user-subscr...@ignite.apache.orgî and follow simple instructions in the reply. Please provide the logs from all the

Re: Ignite with Cassandra and SSL

Hi, This is a duplicate discussion of the following http://apache-ignite-users.70518.x6.nabble.com/Ignite-with-Cassandra-and-SSL-td5610.html#a5700 You will find a solution in the discussion above. -- Denis Good morning Could you please help me understand how to establish

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same ver

Lot of thank you, dear Magda -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Creating-cache-with-CacheLoaderFactory-on-client-node-brings-exception-org-apache-ignite-IgniteCheck-tp5915p5951.html Sent from the Apache Ignite Users mailing list archive at

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same ver

Yes, you have to redeploy this class every time it’s changed. Peer-class-loading feature is supported for Ignite Compute engine allowing to deploy/re-deploy compute tasks automatically. https://apacheignite.readme.io/docs/zero-deployment —

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same ver

Hi dear Magda, As far as I understood ,my loaderFactory(and generally whatever (classes) is used in client node)must be manually set also in the rest nodes? I replaced my classes to remote node,and it started working. Isn't there another solution? At least to be done automatically. Every time

Re: transaction not timing out

Hi, As Dmitriy pointed out, there is no a reliable way to timeout a transaction once the commit phase has begun. If there is a chance that your cache store may stall for unpredictable amount of time, this should be handled within the store and possibly throw an exception, but this will result in

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same ver

Hi, You have to place the class of your loader factory in clients’ nodes classpath as well. The main reason for this is because when a transaction is started from a client node (that is quite a usual case) then the client first commits data to a storage and after that to in-memory. Case with

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same ver

Hi @bintisepaha, Yes the the JDK versions are same. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Creating-cache-with-CacheLoaderFactory-on-client-node-brings-exception-org-apache-ignite-IgniteCheck-tp5915p5946.html Sent from the Apache Ignite Users mailing

Re: transaction not timing out

Hi Binti, In case of writeAll the locks for keys are acquired sequentially. To avoid deadlocks you need to use an ordered data structure like TreeSet the will hold the keys. Alex G. can you join the thread and provide your thoughts on why the timeout is not honored for the discussed