read from igniteRDD and write to igniteRDD

hi. as we know we can create igniteRDD for sharing between spark worker. i want to know how we can read from igniteRDD from spark executor and how to write to igniteRDD from spark executor. is it possible to share an example? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: WAL size control

I have more than three hundred WAL segments in our folder -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: WAL size control

Hi Igniters - I have the problem too, but I only have one node in the server. I want to know how to delete the unused WAL segments safety. Looking forward to your reply. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Abnormal termination of nodes with native persistence enabled

thanks! 在 2019/1/14 下午11:44, ilya.kasnacheev 写道: Hello! Please see http://apache-ignite-users.70518.x6.nabble.com/Native-persistence-ignite-server-failed-to-join-when-client-has-been-started-td26248.html#a26250 with regards to visor node. Node with BaselineTopology cannot join mixed cluster

MVCC and continuous query

As per https://apacheignite.readme.io/docs/multiversion-concurrency-control, continuous query can be done against ignite with mvcc enabled (transactional_snapshot). However, on the same page, it also mentioned that events is not supported with MVCC. I am wondering what mechanism continuous query

Re: Local node SEGMENTED error causing node goes down for no obvious reason

It seems there were issues with network. You can see plenty of discovery warnings in logs of the kind (231.log): [2018-11-07T07:44:44,627][WARN ][grid-timeout-worker-#119][TcpDiscoverySpi] Socket write has timed out (consider increasing 'IgniteConfiguration.failureDetectionTimeout' configuration

Re: Difference between Ignite Kafka Streamer and Kafka consumer (2.0)

About your question "/What is difference between Ignite Kafka Streamer and Kafka consumer?/": Kafka Consumer is Kafka API to poll data from Kafka while Ignite Kafka Streamer is a complete solution to stream data from Kafka into Ignite. Internally Kafka Streamer starts one or many Kafka Consumers

IgniteInterruptedException on cache.get in a transaction inside runnable (ignite 2.6)

Hi folks, we are getting this error in existing code in ignite 2.6.0. The cache.get is on a replicated/transactional cache and holds only only a single key/value pair. It has been used like this for a while in production. The code is executed in a runnable and wrapped in a

Insert performance

Hello, I'm doing tests to get the best performance whily using Ignite. I've to insert a lot of data, then doing some requests. First, in my tests, I'm using objects with @SqlFields annotations, cache.putAll is faster than IgniteDataStream, is it normal ? I'm using cache.putAll to send 5000

Re: Thread got interrupted while trying to acquire table lock & Got interrupted while waiting for future to complete

Was there any resolution to this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Visor "cache" command hangs when client node connects.

So if it's all running inside DC/OS it works ni issues. So wondering what would be the strategy if external clients want to connect either Ignite being inside the contaimer env or outside... Just REST? On Fri., Jan. 11, 2019, 15:00 John Smith Yeah this doesn't work on the dev environment either,

Ignite documentation error regarding RAM usage

Hello, Following this bug fix - https://issues.apache.org/jira/browse/IGNITE-7824, I think the documentation needs to be updated too, right? It still mentions 20% RAM, and it should be 80%. This is the documentation I'm referring to: https://apacheignite.readme.io/docs/memory-configuration

Unable to activate an ignite cluster with multiple hosts.

I tried to activate my 3-node ignite cluster with "control.sh --activate", but the activation keeps failing. The command just hang there for ever. The same activate command works if the ignite cluster has only one node. But it does not work if the cluster has multiple nodes. I am using

Re: java.lang.OutOfMemoryError: Java heap space on server node during cache querying on same node by multiple clients nodes

Hello! We were able to debug underlying problem, which was that Communication will hold references to those (large) messages once they were sent. The solution for such cases where GridNioServer will hold on to large messages is to decrease TcpCommunicationSpi#setAckSendThreshold

Re: Abnormal termination of nodes with native persistence enabled

Hello! Please see http://apache-ignite-users.70518.x6.nabble.com/Native-persistence-ignite-server-failed-to-join-when-client-has-been-started-td26248.html#a26250 with regards to visor node. > Node with BaselineTopology cannot join mixed cluster running in > compatibility mode This is the key.

Re: Ignite ML withKeepBinary cache

Hello! I can see there is a ticket in JIRA: https://issues.apache.org/jira/browse/IGNITE-10700 If anything is not there please update it. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache updates slow on Linux Vs Windows

Hello! Did you figure out anything? I went through your log but did not have any exact ideas. Is it possible that Windows node is slowed down by very active I/O? Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to Write and Read a Nested JSON Into and From Apache Ignite Table

Hello! You can nest BinaryObjects as deep as you need. I know that there are users who routinely serialize JSON to BinaryObject. However, you will not be actually refer to nested data in SQL queries, only to top-level values. Regards, -- Sent from:

Re: Does ignite keep loading result when the jdbc thin connection is dead?

Hello! I guess it is true. But, you can sometimes work around it by setting 'lazy=true' connection flag. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Able to access one cache not able to access another from cluster

Hello! What happens when you try to access the one cache that you can't? Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite benchmarking with YCSB

Hello! Unfortunately there's not enoug info to be able to debug this further. I don't think you can get Ignite to use both IPs to connect client to server, unless you start two differing server nodes with different own IP. Regards, -- Sent from:

Re: SQL Support for IN predicate

Hello! I believe you can still get IN to ignore indexes for more complex queries, so watch out even if they work for simpler ones. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin: support connection pooling in 2.7?

Hello! > When we use connection pool,we randomly get a connection from the > pool.This cause strange issues.For example,when we do create index > operation after create a table we get an exception "cache doesn't exists". It is a known issue, which you can mitigate by not putting connection to

Re: Local node SEGMENTED error causing node goes down for no obvious reason

Hello! I can see that at 2018-11-07T07:54:47 five new clients will suddently arrive and then five server nodes will drop (not being able to acknowledge addition of new nodes perhaps?). Either there is communication problems between new clients and old servers, or some bug manifested by rapid

Re: Cache access blocked on destroy

Hello! Unfortunately your e-mail contained neither attachment nor links to it. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: UPDATE query with JOIN

Hello! Unfortunately you can't do this right now. Your best bet is 4) as you have figured. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Error with Spark + IGFS (HDFS cache) through Hive

Hello! If you can write a test which demonstrates problematic behavior, and a fix on top of that, and fill a ticket against IGNITE project in Apache JIRA, I think we could merge it all right. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: SQL performance very slow compared to KV in pure-in-memory cache?

Do you use the same config for both runs? If you use ignite-sql.xml for SQL and ignite.xml for key-value than key-value keys indeed should be much faster, because SQL features are not used there and Ignite doesn’t have to maintain all the SQL indexes, etc. Stan From: summasumma Sent: 7 января

RE: Failed to read data from remote connection

Not really. The amount of direct memory needed doesn’t grow with the node count nor the amount of data you store. Stan From: wangsan Sent: 12 января 2019 г. 9:30 To: user@ignite.apache.org Subject: RE: Failed to read data from remote connection Yeath, set a larger MaxDirectMemorySize . But, I

Re: Ignite in Kubernetes not works correctly

failureDetectionTimeout - 6 joinTimeout - 12 Saw these recomendations in one of the answers in your forum On Mon, Jan 14, 2019 at 2:21 PM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > Glad you managed to resolve it. What did you have to increase the values > to? > >

Re: Does Ignite message support C++?

Hi, 1. Async is not yet supported in C++ clients. 2. Continuous queries supported by thick C++ client. 3. Works through SQL, so supported by thick client. 4. SQL supported by thick client, and also planned for C++ thin client. Best Regards, Igor On Mon, Jan 14, 2019 at 10:53 AM summasumma

Re: Ignite in Kubernetes not works correctly

Glad you managed to resolve it. What did you have to increase the values to? Regards, Stephen > On 14 Jan 2019, at 09:34, Alena Laas wrote: > > It seems that increasing joinTimeout and failureDetectionTimeout solved the > problem. > > On Fri, Jan 11, 2019 at 5:24 PM Alena Laas

Re: [IGNITE-10925] After upgrading 2.7 getting Unexpected error occurred during unmarshalling

Hi, I am able to create a reproducer for this issue. I have also created a JIRA IGNITE-10925 for this issue. Reproducer: https://github.com/prasadbhalerao1983/IgniteIssueReproducer.git Step to Reproduce: 1) First Run com.example.demo.Server

Re: Ignite in Kubernetes not works correctly

It seems that increasing joinTimeout and failureDetectionTimeout solved the problem. On Fri, Jan 11, 2019 at 5:24 PM Alena Laas wrote: > I attached part of the log with "node failed" events (100.99.129.141 - ip > of restarted node) > > These events are repeated until suddenly after about 40 min

Re: How to dump thread stacks in Ignite docker container

Hi Justin, One way you can do it: 1. Access to standard output of a default process started in an Ignite container. 2. Find pid of a java process in the container (run ps in the container). 3. Run "kill -3 ${java_pid}" in the container. 4. Observe a thread dump in the container output (mentioned