Re: error in ignite-spark

i have searched alot but i couldn't find enable scala profile i maven. do you have any link? On Wed, Dec 26, 2018 at 8:34 PM Ilya Kasnacheev wrote: > Hello! > > With -Pscala command or via netbeans dialogs. > > Regards, > -- > Ilya Kasnacheev > > > ср, 26 дек. 2018 г. в 19:54, Mehdi Seydali : >

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

As you see, the example in config has , which means that it's just a part of the configuration. Exceptions message says "Cache name must not be null" and that really the problem that you faced, just define cache name property to resolve this issue. Evgenii чт, 27 дек. 2018 г. в 22:28, yangjiajun

Ouch! Argument is invalid: Cache name must not be null or empty.

Hello. I use ignite 2.6 as a database and try to tune data rebalancing according to following doc： https://apacheignite.readme.io/docs/rebalancing#section-rebalance-message-throttling But I get an exception when I set those settings. class org.apache.ignite.IgniteException: Ouch! Argument is inva

Unsubscribe

Unsubscribe

Re: error in importing ignite 2.7 to netbeans

pom content file in /example/src/ just like bellow. i think profile has set. http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> 4.0.0

Re: error in importing ignite 2.7 to netbeans

In which file i can see the profile?pom in the root folder of ignite? On Wednesday, December 26, 2018, aealexsandrov wrote: > Please check that you set the scale profile because of without it the spark > dependencies will not be added: > > ... > > > scala > >

Re: Data Replication Between Ignite Clusters Through Kafka

Hi, Can anyone suggest me know how to achieve the data replication across clusters for ignite? What needs to be corrected to make it work as mentioned in previous post. Thanks, Prashant -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Remote Node

Hi, By default, Ignite uses TcpDiscoveryMulticastIpFinder, which means that nodes can be connected to each other even without configuring certain IP addresses. You can use TcpDiscoveryVmIpFinder instead, it will try to connect only to the pre-configured addresses. TcpDiscoverySpi discovery = new

Ignite Remote Node

Hello I have upgraded my code from Apache ignite version 2.6 to 2.7. I am running two server nodes in two different machines. However after upgrade, noticed that these two server nodes joined. Log shows as servers=2, state=ACTIVE. Based on previous suggestion, I have commented out TCPDiscoverSPI

Re: Index inline size

Prasad, By default *QuerySqlField#inlineSize *is equal to -1, which means, that it will be chosen automatically. *CacheConfiguration#setSqlIndexMaxInlineSize *specifies the maximal automatically calculated inline size for a cache. But if *QuerySqlField#inlineSize *is not -1, then it will be used r

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

Thank you, I will try to reproduce the same. Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

Hello. I only started one node. Here is my config file: example-default.xml aealexsandrov wrote > No, > > I just try to get the details and reproduce the issue. Possible there is > an > issue here. I will retur

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

No, I just try to get the details and reproduce the issue. Possible there is an issue here. I will return with an update soon. Also could you please provide the configuration of your nodes? Did you update the walArchivePath for all of your nodes? BR, Andrei -- Sent from: http://apache-ignite-

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

Hello.Thanks for your reply. I use version 2.6. I changed the walArchivePath to the directory where before was walPath. So the correct operation is to set the walPath to the directory where before was walArchivePath? aealexsandrov wrote > Hi, > > What is the version of Ignite you use? > > D

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

aealexsandrov wrote > Hi, > > What is the version of Ignite you use? > > Did you set the walPath to the directory where before was walArchivePath? > > BR, > Andei > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Sent from: http://apache-ignite-users.70518.x6.nab

Re: Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

Hi, What is the version of Ignite you use? Did you set the walPath to the directory where before was walArchivePath? BR, Andei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failed to initialize wal (work directory contains incorrect number of segments) [cur=357, expected=10]

Hello. I want to disable wal archiving by setting WAL path and the WAL archive path to the same value. https://apacheignite.readme.io/docs/write-ahead-log I make this change and then success restart my node first time.But I get an exception when I restart my node second time.Is my change a danger

Re: Ignite we-console security

Hi, Sheshananda! I merged IGNITE-9845 to master. And it will be available in Ignite 2.8. This will allow to configure SSL for Web Console in "DEV" mode and in "Direct install" mode. Please, note that IGNITE-10668 is under development for now. When finished, it will enable SSL configuration in "Do

Re: If I want to know how long it takes for data reading from the server side, where should I add logs?

Hi, Will be better if you shared your code. However, I see that you used persistence. So here are some reasons why you can see these drops: 1)You data region is less than full loaded data size stored on disk. In case if read operation can't find the value in RAM then it will read it from the disk

Is Apache planning to release support for table joins with updates .

I am looking solution for queries like below : Update Person SET lastName ='pit' where person.id =city.id AND city.zipCode ='B8Q97' OR UPDATE table1, table2 SET table1.quantity = 6 where table1.pid =table2.pid AND table2.zip ="abc" -- Sent from: http://apache-ignite-users.70518.x6.nab

RE: CAP Theorem (CP? or AP?)

There were two bugs actually, but the problem is basically the same, just in different cases. SQL + Partition Loss Policies issue (fixed in 2.7) - https://issues.apache.org/jira/browse/IGNITE-8927 (the issue says “hang” but the visible behavior actually varies) SQL + Partition Loss Policies + Na