RE: Information regarding Ignite Web Console

Hi Deniz, Thank you so much for the detailed explanation. This clarified so many open questions on going forward with ignite. Regards, Sriveena From: Denis Mekhanikov [mailto:dmekhani...@gmail.com] Sent: Monday, July 02, 2018 8:39 PM To: user@ignite.apache.org Subject: Re: Information regarding

Re: org.apache.ignite.IgniteCheckedException: Unknown page IO type: 0

The node has not happened fault, is I modify configuration problem appears after the restart, now I need to how to correct the nodes offline, and then again in the form of a new node to join the cluster? All node profiles for the cluster are the same. 发自我的 iPhone > 在 2018年7月3日，00:16，Denis

Affinity calls in stream receiver

We have a custom stream receiver that makes affinity calls. This all functions properly, but we see a very large number of the following messages for the same two classes. We also just tripped a 2GB limit on Metaspace size, which we came close to in the past.

Thin client doesn't support Expiry Policies.

Hi, We are currently using Ignite 2.1/C# in our application and considering to use Ignite 2.5/C# because of thin client feature. But we notice that thin client doesn't support to cache value with expiry policy. We use that feature heavily in our application. May I ask if you are going to

Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery

Thanks Ily , could share any guidelines to control groupby?, Like didicated client nodes for connectivity from Tableau and SQL? Thanks Bhaskar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: How long Ignite retries upon NODE_FAILED events

Ok I did following poc real quick. 1. Two nodes, started. And joined. Topology snapshot servers=2. 2. In one node, I blocked the Ignite ports(47500, 47100 etc). 3. Then After failureDetecitonTimeout, it logged NODE_FAILED, and Topology snapshot servers=1 in each node. 4.

Re: How long Ignite retries upon NODE_FAILED events

If cluster already decided that node failed, it will be stopped after it will try to reconnect to the cluster with the same id 2018-07-02 18:37 GMT+03:00 HEWA WIDANA GAMAGE, SUBASH < subash.hewawidanagam...@fmr.com>: > Yes failureDetectionTimeout determines the time it wait to mark a node >

Re: Is it possible to configure Apache Ignite QueryCursor to be autocloseable in the xml configuration file?

Hi Igor, I am using version 2.5.0. Thanks Ti -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Deadlock during cache loading

(OT: Sorry about the duplicate posts, for some reason Nabble was refusing to show me new posts so I thought my earlier ones had been lost.) >Why did you decide, that cluster is deadlocked in the first place? Because all of the Datastreamer threads were stuck waiting on locks, and no progress was

Re: org.apache.ignite.IgniteCheckedException: Unknown page IO type: 0

Looks like your persistence files are corrupted. You configured *LOG_ONLY* WAL mode. It doesn't guarantee survival of OS crushes and power failures. How did you restart your node? Denis пн, 2 июл. 2018 г. в 16:40, NO <727418...@qq.com>: > When I restart the node, I get the following error, >

Re: Deadlock during cache loading

Denis does have a point. When we were trying to run using GP2 storage, the cluster would simply lock up for an hour. Once we moved to local SSDs on i3 instances those issues went away (but we needed 2.5 to have the streaming rate hold for up as we had a lot of data loaded). The i3 instances

RE: How long Ignite retries upon NODE_FAILED events

Yes failureDetectionTimeout determines the time it wait to mark a node failed. But my question is, after such node failed happened, and then what happens when that failed node becomes reachable in the network (less that failureDetectionTimeout) ? From: Evgenii Zhuravlev

Re: Deadlock during cache loading

Why did you decide, that cluster is deadlocked in the first place? > We've had several deployments in a row fail, apparently due to deadlocking in the loading process. What did you see in logs of the failing nodes? Denis пн, 2 июл. 2018 г. в 17:08, breischl : > Ah, I had not thought of that,

Re: Information regarding Ignite Web Console

You should specify QueryEntity.valueType corresponding to the type name, that you use when constructing a binary object. Please find attached example, that shows how to

Re: How long Ignite retries upon NODE_FAILED events

Hi, by default, Ignite uses a mechanism, that can be configured using failureDetectionTimeout: https://apacheignite.readme.io/v2.5/docs/tcpip-discovery#section-failure-detection-timeout Evgenii 2018-07-02 16:40 GMT+03:00 HEWA WIDANA GAMAGE, SUBASH < subash.hewawidanagam...@fmr.com>: > Hi team,

Re: Information regarding Ignite Web Console

> Does all the tables created in ignite gets converted to binary objects internally? Yes, unless you specify a different IgniteConfiguration#marshaller

Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery

Hello again! It seems that I had a copy-paste problem here: the actual flag name is IGNITE_SQL_FORCE_LAZY_RESULT_SET Regards, -- Ilya Kasnacheev 2018-07-02 16:53 GMT+03:00 Ilya Kasnacheev : > Hello! > > You can set IGNITE_SQL_LAZY_RESULT_SET=true (environment variable or JVM > system

Re: Deadlock during cache loading

Ah, I had not thought of that, thanks. Interestingly, going to a smaller cluster seems to have worked around the problem. We were running a 44-node cluster using 3 backups of the data. Switching to two separate 22-node clusters, each with 1 backup, seems to work just fine. Is there some limit to

Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery

Hello! You can set IGNITE_SQL_LAZY_RESULT_SET=true (environment variable or JVM system property) on all nodes since Apache Ignite 2.5, make sure that all queries run with lazy=true. It will still not save you from some scenarios such as runaway GROUP BYs, but from SELECT * it would. Regards,

Re: Node stopped automatically

Venkat, Please don't paste your logs into the body of your message, it makes them look unreadable. Use file attachment or provide a link instead. Node on host 1 got segmented and killed according to the configured segmentation policy. It may happen due to a network problem or long GC pause.

How long Ignite retries upon NODE_FAILED events

Hi team, For example, let's say one of the node is not down(JVM is up), but network not reachable from/to it. Then rest of the nodes will see NODE_FAILED and started working as normal with reduced cluster size. If that failed node, the network from/to it, becomes normal again after X

org.apache.ignite.IgniteCheckedException: Unknown page IO type: 0

When I restart the node, I get the following error, The problem persists after restarting the machine?? == [2018-07-02T21:25:52,932][INFO ][exchange-worker-#190][GridCacheDatabaseSharedManager] Read checkpoint status

Re: Ignite File System (igfs) spillover to disk

Matt, You can configure FileSystemConfiguration#dataCacheConfiguration and specify a persisted data region

Re: S3AFileSystem as IGFS secondary file system

I have been able to do it using the following lines: BasicHadoopFileSystemFactory f = new BasicHadoopFileSystemFactory(); f.setConfigPaths("cfg.xml"); IgniteHadoopIgfsSecondaryFileSystem sec = new IgniteHadoopIgfsSecondaryFileSystem(); sec.setFileSystemFactory(f);

Re: Deadlock during cache loading

transactions are easy to use: see examples, org.apache.ignite. examples.datagrid.store.auto We use them in the stream receiver.You simply bracket the get/put in the transaction, but use a timeout, then bracket that with an "until done" while loop, perhaps added a sleep to backoff. We ended

S3AFileSystem as IGFS secondary file system

Hi, I am struggling to get the S3AFileSystem configured as an IGFS secondary file system. I am using IGFS as my default file system, and do not want to have an HDFS cluster up and running besides the IGFS one. I have been able to reproduce the steps contained at

RE: Information regarding Ignite Web Console

Denis, Have some open questions in ignite 1. Does all the tables created in ignite gets converted to binary objects internally? 2. Does all the cache entities like Person gets converted to binary objects internally? 3. Is using binary objects better than entity cache

S3AFileSystem as IGFS secondary file system

Hi, I am struggling to get the S3AFileSystem configured as an IGFS secondary file system. I am using IGFS as my default file system, and do not want to have an HDFS cluster up and running besides the IGFS one. I have been able to reproduce the steps contained at

Re: Uneven partitioning and data not on off-heap memory.

Mikael, You can't configure a node not to use off-heap memory. It's always used. But you can enable on-heap caching along with it: https://apacheignite.readme.io/docs/memory-configuration#section-on-heap-caching So, off-heap memory cannot be disabled. @smovva, "Off-Heap" shows how many entries

RE: High cpu on ignite server nodes

I don't really have much to say but to try reducing/balancing on heap cache size. If you have a lot of objects on heap, you need to have a large heap, obviously. If you need to constantly add/remove on-heap objects, you'll have a lot of work for GC. Perhaps you can review your architecture to

Re: Node stopped automatically

Please could you provide some pointers, so that I can look deeper into the issue. 1) Does PageMemory cause any issues as per the metrics, one node is contains only 70 and other node is PageMemory [pages=390178] 2) Why whole cluster is going down, when one node is down 3) Can I restart the

Re: Is it possible to configure Apache Ignite QueryCursor to be autocloseable in the xml configuration file?

What is Ignite version you are on? Best Regards, Igor On Sat, Jun 30, 2018 at 9:28 PM tizh wrote: > I am writing a program in Golang that connects to local Ignite clusters > through an ODBC driver package written in Go. > > During development I began getting this error repeatedly: > > > > I

RE: Questions on setting up firewall for multicast cluster discovery.

The nodes are on VirtualBox VMs and connected via the Virtualboxe's 'bridged' network. Because it's Centos the each machines own firewall on must be set up to enable the required ports (like most Unixes). As a work round I can use static. That it works fine. However every time I create a new