Re: error in running shared rdd example with intellij

[Mehdi Seydali]

how i could change client mode to server mode?

On Sat, Dec 29, 2018 at 9:49 AM Mehdi Seydali 
wrote:

> i have run it in 4 nodes. but the same error has remained.
>
> On Fri, Dec 28, 2018 at 5:44 PM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> Looks like this node is started in client node, but you don't have server
>> nodes available for it to connect to.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пт, 28 дек. 2018 г. в 15:59, mehdi sey :
>>
>>> hi i want to run SharedRddExample in intellij IDE. but i have encounter
>>> error
>>> just as bellow . why?
>>> /usr/lib/jvm/java-8-oracle/bin/java
>>> -DIGNITE_HOME=/usr/local/apache-ignite-fabric-2.6.0-bin/
>>>
>>> -javaagent:/snap/intellij-idea-community/109/lib/idea_rt.jar=35933:/snap/intellij-idea-community/109/bin
>>> -Dfile.encoding=UTF-8 -classpath
>>>
>>> 

Re: error in running shared rdd example with intellij

[Mehdi Seydali]

i have run it in 4 nodes. but the same error has remained.

On Fri, Dec 28, 2018 at 5:44 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> Looks like this node is started in client node, but you don't have server
> nodes available for it to connect to.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 28 дек. 2018 г. в 15:59, mehdi sey :
>
>> hi i want to run SharedRddExample in intellij IDE. but i have encounter
>> error
>> just as bellow . why?
>> /usr/lib/jvm/java-8-oracle/bin/java
>> -DIGNITE_HOME=/usr/local/apache-ignite-fabric-2.6.0-bin/
>>
>> -javaagent:/snap/intellij-idea-community/109/lib/idea_rt.jar=35933:/snap/intellij-idea-community/109/bin
>> -Dfile.encoding=UTF-8 -classpath
>>
>> 

Question about write speed.

[yangjiajun]

Hello.

I use ignite 2.6  as a sql database and enable persistence(full_sync).I only
start one node.All tables are replicated.I use streaming while insert
data.The write speed is about 5~6k records per table.Is such speed
normal?Can I improve it?

Here is my config file：
example-default.xml
 
 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to define a cache template?

[yangjiajun]

Hello!

I want to make some cache settings global.It means I need to define a cache
template and then use it,right?But I did not find any docs related to this.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite stops expiring caches after a period of time

[Scott Feldstein]

Hi Ilya,
Thanks. I assume since I’m using persistence that expiry of the data is the
only way to ensure that it is eventually purged. Is that correct or is
there something else I should look at?

Yep, I’m fine with upgrading to 2.7, we like to be as close to the bleeding
edge with our technology stack anyway :)
On Fri, Dec 28, 2018 at 06:41 Ilya Kasnacheev 
wrote:

> Hello!
>
> Since Ignite 2.0 works with OffHeap pages mostly, Page Eviction works best
> if you don't care about data (pure cache mode):
> https://apacheignite.readme.io/docs/evictions
>
> If it works for 2.7.0 I recommend you to stick with is, since if one would
> be fixing 2.6 they will yield 2.7 anyway :)
>
> Regards,
>
> --
> Ilya Kasnacheev
>
>
> ср, 26 дек. 2018 г. в 22:25, Scott Feldstein :
>
>> hi Ilya,
>> Why wouldn't many people use Expiry with 2.x?  Is there another feature
>> that I should be using that accomplishes the same thing?
>>
>> I've reproduced the issue for 2.6.0, but with 2.7.0 it looks like it is
>> working.  Here is the repro if anyone is interested -
>>
>> https://github.com/scottmf/ignite-expiry-repro
>>
>> On Tue, Dec 25, 2018 at 5:30 AM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> Not many people are using Expiry with 2.x.
>>>
>>> If you can share a reproducer, please create a ticket right away and I
>>> hope that somebody will look into it.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> вт, 25 дек. 2018 г. в 01:36, Scott Feldstein :
>>>
 Thanks Ilya, I’ll upgrade and see if that works soon. Right now we’ve
 switched to only using partitioned caches to avoid this issue. If it’s
 something that isn’t fixed with 2.7 then I’ll create a bug and attach code
 to reproduce it.

 I’m really surprised that no one else is complaining about it. The
 repro is very straight forward..


 On Mon, Dec 24, 2018 at 06:36 Ilya Kasnacheev <
 ilya.kasnach...@gmail.com> wrote:

> Hello!
>
> There could be fixes for expiration between 2.6 and 2.7.
>
> However, if it will still be the case, we would be glad if you could
> post reproducer for this behavior.
>
> Note that you can almost emulate replicated cache by creating
> partitioned cache with large number of backups, maybe you should be using
> that in the meantime.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
>
> пт, 21 дек. 2018 г. в 23:28, scottmf :
>
>> I forgot to mention this is on Ignite 2.6.0 and i'm running with a 3
>> node
>> cluster.
>>
>> I've been experimenting some more and I'm finding that using
>> PARTITIONED
>> caches works fine, but replicated caches stop expiring usually within
>> 10
>> minutes.  The behavior is very consistent.
>>
>> I plan on trying this with Ignite 2.7.0...
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

Re: Query Execution very slow

[Ilya Kasnacheev]

Hello!

There's a docs page at
https://apacheignite.readme.io/docs/configuration-parameters
This is because Ignite's query planner sometimes plans joins unoptimally
and you have to help it.

Regarding second sql, additional investigation is needed. Can you show
EXPLAIN after you apply enforceJoinOrder?

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 18:59, Prasad Bhalerao :

> Hi,
>
> After setting enforceJoinOrder to true it worked. Can you please explain
> how did it work... pushing the data to temp table first and then
> enforeOrder?
>
> Is it documented in ignite docs?
>
> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
> getAffectedIPRange_3 :: *TimeTakenToComplete=10 ::* Size=1295
>
>
> *But second sql is still taking time. The only difference is it has
> ipStart and ipEnd filter in where clause.*
>
> getAffectedIPRange_2 :: SQL_2=SELECT ipv4agd.id, ipv4agd.assetGroupId,
> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
> WHERE subscriptionId = ? AND (ipStart <= ? AND ipEnd >= ?) ORDER BY
> ipv4agd.assetGroupId
> getAffectedIPRange_2 :: *TimeTakenToComplete=25436* :: Size=1260
>
> Thanks,
> Prasad
>
> On Fri, Dec 28, 2018 at 9:02 PM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> Did you set enforceJoinOrder to true?
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пт, 28 дек. 2018 г. в 18:19, Prasad Bhalerao <
>> prasadbhalerao1...@gmail.com>:
>>
>>> Hi,
>>>
>>> I tried your suggestion but it did not work. It is taking 22.8 seconds.
>>>
>>> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
>>> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
>>> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
>>> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
>>>
>>> getAffectedIPRange_3 :: TimeTakenToComplete=22891 :: Size=1295
>>> Thanks,
>>> Prasad
>>>
>>> On Fri, Dec 28, 2018 at 8:32 PM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 Hello!

 I have created a PR for you:
 https://github.com/prasadbhalerao1983/IgniteTestPrj/pull/1
 With it, I can see:

 getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
 ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
 JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
 WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
 getAffectedIPRange_3 :: TimeTakenToComplete=11 :: Size=1295

 Regards,
 --
 Ilya Kasnacheev


 пт, 28 дек. 2018 г. в 17:46, Prasad Bhalerao <
 prasadbhalerao1...@gmail.com>:

> Can someone from community help me with t
>
> I have created a reproducer and uploaded it to GitHub. I have created
> 3 cases to test the sql execution time.
>
> Please run *IgniteQueryTester_4* class to check the issue.
> GitHub project: https://github
> .com/prasadbhalerao1983/IgniteTestPrj.git
>
> Thanks,
> Prasad
>
>
> On Wed, Dec 26, 2018 at 11:18 PM Prasad Bhalerao <
> prasadbhalerao1...@gmail.com> wrote:
>
>> How to push the ids to temp table, can you please give any example?
>> Is it a in memory temp table created by ignite?
>>
>> Can you please explain how enforceJoinOrder will help in this case?
>> Thanks ,
>> Prasad
>>
>> On Wed 26 Dec, 2018, 9:37 PM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com wrote:
>>
>>> Hello!
>>>
>>> Can you try pushing temp table to 1st position and setting
>>> enforceJoinOrder=true?
>>>
>>> SELECT ipv4agd.id,
>>>   ipv4agd.assetGroupId,
>>>   ipv4agd.ipStart,
>>>   ipv4agd.ipEnd
>>> FROM TABLE (assetGroupId bigint = ? ) temp
>>> JOIN IpV4AssetGroupData ipv4agd
>>> ON ipv4agd.assetGroupId = temp.assetGroupId
>>> WHERE subscriptionId= ?
>>> AND (ipStart <= ? AND ipEnd >= ?)
>>> ORDER BY ipv4agd.assetGroupId
>>>
>>> See https://apacheignite.readme.io/docs/configuration-parameters
>>> for enforceJoinOrder.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 26 дек. 2018 г. в 19:01, Prasad Bhalerao <
>>> prasadbhalerao1...@gmail.com>:
>>>
 I am executing following SQL on ignite cache. This cache has 37
 million records and this data is distributed across 4 nodes.
 *SQL:*
 SELECT ipv4agd.id,
   ipv4agd.assetGroupId,
   ipv4agd.ipStart,
   ipv4agd.ipEnd
 FROM IpV4AssetGroupData ipv4agd
 JOIN TABLE (assetGroupId bigint = ? ) temp
 ON ipv4agd.assetGroupId = 

Re: Query Execution very slow

[Prasad Bhalerao]

Hi,

After setting enforceJoinOrder to true it worked. Can you please explain
how did it work... pushing the data to temp table first and then
enforeOrder?

Is it documented in ignite docs?

getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
getAffectedIPRange_3 :: *TimeTakenToComplete=10 ::* Size=1295


*But second sql is still taking time. The only difference is it has ipStart
and ipEnd filter in where clause.*

getAffectedIPRange_2 :: SQL_2=SELECT ipv4agd.id, ipv4agd.assetGroupId,
ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
WHERE subscriptionId = ? AND (ipStart <= ? AND ipEnd >= ?) ORDER BY
ipv4agd.assetGroupId
getAffectedIPRange_2 :: *TimeTakenToComplete=25436* :: Size=1260

Thanks,
Prasad

On Fri, Dec 28, 2018 at 9:02 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> Did you set enforceJoinOrder to true?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 28 дек. 2018 г. в 18:19, Prasad Bhalerao  >:
>
>> Hi,
>>
>> I tried your suggestion but it did not work. It is taking 22.8 seconds.
>>
>> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
>> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
>> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
>> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
>>
>> getAffectedIPRange_3 :: TimeTakenToComplete=22891 :: Size=1295
>> Thanks,
>> Prasad
>>
>> On Fri, Dec 28, 2018 at 8:32 PM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> I have created a PR for you:
>>> https://github.com/prasadbhalerao1983/IgniteTestPrj/pull/1
>>> With it, I can see:
>>>
>>> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
>>> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
>>> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
>>> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
>>> getAffectedIPRange_3 :: TimeTakenToComplete=11 :: Size=1295
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> пт, 28 дек. 2018 г. в 17:46, Prasad Bhalerao <
>>> prasadbhalerao1...@gmail.com>:
>>>
 Can someone from community help me with t

 I have created a reproducer and uploaded it to GitHub. I have created
 3 cases to test the sql execution time.

 Please run *IgniteQueryTester_4* class to check the issue.
 GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git

 Thanks,
 Prasad


 On Wed, Dec 26, 2018 at 11:18 PM Prasad Bhalerao <
 prasadbhalerao1...@gmail.com> wrote:

> How to push the ids to temp table, can you please give any example?
> Is it a in memory temp table created by ignite?
>
> Can you please explain how enforceJoinOrder will help in this case?
> Thanks ,
> Prasad
>
> On Wed 26 Dec, 2018, 9:37 PM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com wrote:
>
>> Hello!
>>
>> Can you try pushing temp table to 1st position and setting
>> enforceJoinOrder=true?
>>
>> SELECT ipv4agd.id,
>>   ipv4agd.assetGroupId,
>>   ipv4agd.ipStart,
>>   ipv4agd.ipEnd
>> FROM TABLE (assetGroupId bigint = ? ) temp
>> JOIN IpV4AssetGroupData ipv4agd
>> ON ipv4agd.assetGroupId = temp.assetGroupId
>> WHERE subscriptionId= ?
>> AND (ipStart <= ? AND ipEnd >= ?)
>> ORDER BY ipv4agd.assetGroupId
>>
>> See https://apacheignite.readme.io/docs/configuration-parameters for
>> enforceJoinOrder.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 26 дек. 2018 г. в 19:01, Prasad Bhalerao <
>> prasadbhalerao1...@gmail.com>:
>>
>>> I am executing following SQL on ignite cache. This cache has 37
>>> million records and this data is distributed across 4 nodes.
>>> *SQL:*
>>> SELECT ipv4agd.id,
>>>   ipv4agd.assetGroupId,
>>>   ipv4agd.ipStart,
>>>   ipv4agd.ipEnd
>>> FROM IpV4AssetGroupData ipv4agd
>>> JOIN TABLE (assetGroupId bigint = ? ) temp
>>> ON ipv4agd.assetGroupId = temp.assetGroupId
>>> WHERE subscriptionId= ?
>>> AND (ipStart <= ? AND ipEnd >= ?)
>>> ORDER BY ipv4agd.assetGroupId
>>>
>>>
>>> As per the execution plan show below, ignite is using index
>>> "IPV4_ASSET_GROUP_DATA_IDX2 " and execution plan attached below.
>>>
>>> This sql is taking around 23 seconds. I have set the max index
>>> inline size as 65 bytes.
>>> The number of assetGroupIds set in join clause are 50.
>>>
>>> *Is there anything I can do to improve the performance of this SQL?*
>>>
>>> I have 

Re: Query Execution very slow

[Ilya Kasnacheev]

Hello!

Did you set enforceJoinOrder to true?

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 18:19, Prasad Bhalerao :

> Hi,
>
> I tried your suggestion but it did not work. It is taking 22.8 seconds.
>
> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
>
> getAffectedIPRange_3 :: TimeTakenToComplete=22891 :: Size=1295
> Thanks,
> Prasad
>
> On Fri, Dec 28, 2018 at 8:32 PM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> I have created a PR for you:
>> https://github.com/prasadbhalerao1983/IgniteTestPrj/pull/1
>> With it, I can see:
>>
>> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
>> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
>> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
>> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
>> getAffectedIPRange_3 :: TimeTakenToComplete=11 :: Size=1295
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пт, 28 дек. 2018 г. в 17:46, Prasad Bhalerao <
>> prasadbhalerao1...@gmail.com>:
>>
>>> Can someone from community help me with t
>>>
>>> I have created a reproducer and uploaded it to GitHub. I have created 3
>>> cases to test the sql execution time.
>>>
>>> Please run *IgniteQueryTester_4* class to check the issue.
>>> GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
>>>
>>> Thanks,
>>> Prasad
>>>
>>>
>>> On Wed, Dec 26, 2018 at 11:18 PM Prasad Bhalerao <
>>> prasadbhalerao1...@gmail.com> wrote:
>>>
 How to push the ids to temp table, can you please give any example?
 Is it a in memory temp table created by ignite?

 Can you please explain how enforceJoinOrder will help in this case?
 Thanks ,
 Prasad

 On Wed 26 Dec, 2018, 9:37 PM Ilya Kasnacheev >>> wrote:

> Hello!
>
> Can you try pushing temp table to 1st position and setting
> enforceJoinOrder=true?
>
> SELECT ipv4agd.id,
>   ipv4agd.assetGroupId,
>   ipv4agd.ipStart,
>   ipv4agd.ipEnd
> FROM TABLE (assetGroupId bigint = ? ) temp
> JOIN IpV4AssetGroupData ipv4agd
> ON ipv4agd.assetGroupId = temp.assetGroupId
> WHERE subscriptionId= ?
> AND (ipStart <= ? AND ipEnd >= ?)
> ORDER BY ipv4agd.assetGroupId
>
> See https://apacheignite.readme.io/docs/configuration-parameters for
> enforceJoinOrder.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 26 дек. 2018 г. в 19:01, Prasad Bhalerao <
> prasadbhalerao1...@gmail.com>:
>
>> I am executing following SQL on ignite cache. This cache has 37
>> million records and this data is distributed across 4 nodes.
>> *SQL:*
>> SELECT ipv4agd.id,
>>   ipv4agd.assetGroupId,
>>   ipv4agd.ipStart,
>>   ipv4agd.ipEnd
>> FROM IpV4AssetGroupData ipv4agd
>> JOIN TABLE (assetGroupId bigint = ? ) temp
>> ON ipv4agd.assetGroupId = temp.assetGroupId
>> WHERE subscriptionId= ?
>> AND (ipStart <= ? AND ipEnd >= ?)
>> ORDER BY ipv4agd.assetGroupId
>>
>>
>> As per the execution plan show below, ignite is using index
>> "IPV4_ASSET_GROUP_DATA_IDX2 " and execution plan attached below.
>>
>> This sql is taking around 23 seconds. I have set the max index inline
>> size as 65 bytes.
>> The number of assetGroupIds set in join clause are 50.
>>
>> *Is there anything I can do to improve the performance of this SQL?*
>>
>> I have checked the memory and cpu utilization and it it is very low.
>> I also tried to profile it using jprofiler to find out the issue, but 
>> could
>> not find solution. I have also attached profiler snapshot at the end.
>> Please check.
>>
>>
>> .
>>
>> *Indexes:*
>>
>> public class IpV4AssetGroupData implements 
>> UpdatableData {
>>
>>   @QuerySqlField
>>   private long id;
>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>> "ipv4_asset_group_data_idx2", order = 2)})
>>   private long assetGroupId;
>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>> "ipv4_asset_group_data_idx1", order = 1),
>>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
>> 1)})
>>   private long subscriptionId;
>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>> "ipv4_asset_group_data_idx1", order = 2),
>>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
>> 3)})
>>   private int ipStart;
>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>> "ipv4_asset_group_data_idx1", order = 3),
>>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 

Re: Query Execution very slow

[Prasad Bhalerao]

Hi,

I tried your suggestion but it did not work. It is taking 22.8 seconds.

getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId

getAffectedIPRange_3 :: TimeTakenToComplete=22891 :: Size=1295
Thanks,
Prasad

On Fri, Dec 28, 2018 at 8:32 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> I have created a PR for you:
> https://github.com/prasadbhalerao1983/IgniteTestPrj/pull/1
> With it, I can see:
>
> getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
> ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
> JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
> WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
> getAffectedIPRange_3 :: TimeTakenToComplete=11 :: Size=1295
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 28 дек. 2018 г. в 17:46, Prasad Bhalerao  >:
>
>> Can someone from community help me with t
>>
>> I have created a reproducer and uploaded it to GitHub. I have created 3
>> cases to test the sql execution time.
>>
>> Please run *IgniteQueryTester_4* class to check the issue.
>> GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
>>
>> Thanks,
>> Prasad
>>
>>
>> On Wed, Dec 26, 2018 at 11:18 PM Prasad Bhalerao <
>> prasadbhalerao1...@gmail.com> wrote:
>>
>>> How to push the ids to temp table, can you please give any example?
>>> Is it a in memory temp table created by ignite?
>>>
>>> Can you please explain how enforceJoinOrder will help in this case?
>>> Thanks ,
>>> Prasad
>>>
>>> On Wed 26 Dec, 2018, 9:37 PM Ilya Kasnacheev >> wrote:
>>>
 Hello!

 Can you try pushing temp table to 1st position and setting
 enforceJoinOrder=true?

 SELECT ipv4agd.id,
   ipv4agd.assetGroupId,
   ipv4agd.ipStart,
   ipv4agd.ipEnd
 FROM TABLE (assetGroupId bigint = ? ) temp
 JOIN IpV4AssetGroupData ipv4agd
 ON ipv4agd.assetGroupId = temp.assetGroupId
 WHERE subscriptionId= ?
 AND (ipStart <= ? AND ipEnd >= ?)
 ORDER BY ipv4agd.assetGroupId

 See https://apacheignite.readme.io/docs/configuration-parameters for
 enforceJoinOrder.

 Regards,
 --
 Ilya Kasnacheev


 ср, 26 дек. 2018 г. в 19:01, Prasad Bhalerao <
 prasadbhalerao1...@gmail.com>:

> I am executing following SQL on ignite cache. This cache has 37
> million records and this data is distributed across 4 nodes.
> *SQL:*
> SELECT ipv4agd.id,
>   ipv4agd.assetGroupId,
>   ipv4agd.ipStart,
>   ipv4agd.ipEnd
> FROM IpV4AssetGroupData ipv4agd
> JOIN TABLE (assetGroupId bigint = ? ) temp
> ON ipv4agd.assetGroupId = temp.assetGroupId
> WHERE subscriptionId= ?
> AND (ipStart <= ? AND ipEnd >= ?)
> ORDER BY ipv4agd.assetGroupId
>
>
> As per the execution plan show below, ignite is using index
> "IPV4_ASSET_GROUP_DATA_IDX2 " and execution plan attached below.
>
> This sql is taking around 23 seconds. I have set the max index inline
> size as 65 bytes.
> The number of assetGroupIds set in join clause are 50.
>
> *Is there anything I can do to improve the performance of this SQL?*
>
> I have checked the memory and cpu utilization and it it is very low. I
> also tried to profile it using jprofiler to find out the issue, but could
> not find solution. I have also attached profiler snapshot at the end.
> Please check.
>
>
> .
>
> *Indexes:*
>
> public class IpV4AssetGroupData implements 
> UpdatableData {
>
>   @QuerySqlField
>   private long id;
>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
> "ipv4_asset_group_data_idx2", order = 2)})
>   private long assetGroupId;
>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
> "ipv4_asset_group_data_idx1", order = 1),
>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
> 1)})
>   private long subscriptionId;
>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
> "ipv4_asset_group_data_idx1", order = 2),
>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
> 3)})
>   private int ipStart;
>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
> "ipv4_asset_group_data_idx1", order = 3),
>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
> 4)})
>   private int ipEnd;
>
> }
>
> *Execution plan:*
>
> Query execution is too long [time=15788 ms, sql='SELECT
> IPV4AGD__Z0.ID __C0_0,
> IPV4AGD__Z0.ASSETGROUPID __C0_1,
> IPV4AGD__Z0.IPSTART __C0_2,
> IPV4AGD__Z0.IPEND __C0_3
> FROM 

javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Some of DataStreamer operations failed [failedCount=1]

[userx]

Hi

I have recently upgraded to 2.7 and are in the process of load testing the
ignite infrastructure. In order to do so we have fired request which
populates the data to these ignite caches. We have got a lot of errors with
the message mentioned in the request.

Here is the excerpt from ignite started in client mode from a java program.
Caused by: javax.cache.CacheException: class
org.apache.ignite.IgniteCheckedException: Some of DataStreamer operations
failed [failedCount=1]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1287)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.close(DataStreamerImpl.java:1388)
at com.XXX.datagrid.DataGridClient.writeAll(DataGridClient.java:190)



I am also pasting the ignite server logs
2018-12-28 14:52:55,885 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.exchange.time - Started exchange init
[topVer=AffinityTopologyVersion [topVer=60, minorTopVer=1],
mvccCrd=MvccCoordinator [nodeId=a54f6008-64d4-4aea-aa26-0a716c29c1db,
crdVer=1546005033221, topVer=AffinityTopologyVersion [topVer=15,
minorTopVer=0]], mvccCrdChange=false, crd=true, evt=DISCOVERY_CUSTOM_EVT,
evtNode=cdea7a3b-7b3f-431c-aa90-3fe44de336ea,
customEvt=DynamicCacheChangeBatch
[id=725a415f761-0c9822c2-ec75-433a-b460-6b941dec650d,
reqs=[DynamicCacheChangeRequest [cacheName=6532_40789, hasCfg=true,
nodeId=cdea7a3b-7b3f-431c-aa90-3fe44de336ea, clientStartOnly=false,
stop=false, destroy=false, disabledAfterStartfalse]],
exchangeActions=ExchangeActions [startCaches=[6532_40789], stopCaches=null,
startGrps=[], stopGrps=[], resetParts=null, stateChangeRequest=null],
startCaches=false], allowMerge=false]
2018-12-28 14:52:55,886 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager -
Updating caches registry performed in 1 ms.
2018-12-28 14:52:55,895 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.GridCacheProcessor - Started
cache [name=6532_40789, id=-443798693, group=ProductCache,
memoryPolicyName=default, mode=PARTITIONED, atomicity=ATOMIC, backups=1,
mvcc=false], encryptionEnabled=false]
2018-12-28 14:52:55,896 WARN
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager - No
server nodes found for cache client: 6532_40789
2018-12-28 14:52:55,896 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager -
Caches starting performed in 10 ms.
2018-12-28 14:52:55,896 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager -
Affinity initialization for started caches performed in 0 ms.
2018-12-28 14:52:55,896 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Finished waiting for partition release future
[topVer=AffinityTopologyVersion [topVer=60, minorTopVer=1], waitTime=0ms,
futInfo=NA, mode=DISTRIBUTED]
2018-12-28 14:52:55,897 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Finished waiting for partitions release latch: ServerLatch [permits=0,
pendingAcks=[], super=CompletableLatch [id=exchange,
topVer=AffinityTopologyVersion [topVer=60, minorTopVer=1]]]
2018-12-28 14:52:55,897 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Finished waiting for partition release future
[topVer=AffinityTopologyVersion [topVer=60, minorTopVer=1], waitTime=0ms,
futInfo=NA, mode=LOCAL]
2018-12-28 14:52:55,897 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
- Logical recovery performed in 0 ms.
2018-12-28 14:52:55,897 INFO
[exchange-worker-#123%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.exchange.time - Finished exchange init
[topVer=AffinityTopologyVersion [topVer=60, minorTopVer=1], crd=true]
2018-12-28 14:52:55,903 INFO
[sys-#752%f3a9610b-2b22-4323-92fe-2c9bf79200f0%] {}
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture
- Coordinator received single message [ver=AffinityTopologyVersion
[topVer=60, minorTopVer=1], node=401772af-63d0-4bd4-b6b7-7199f53ed270,
allReceived=true]
2018-12-28 14:52:55,903 INFO

Re: Query Execution very slow

[Ilya Kasnacheev]

Hello!

I have created a PR for you:
https://github.com/prasadbhalerao1983/IgniteTestPrj/pull/1
With it, I can see:

getAffectedIPRange_3 :: SQL_3=SELECT ipv4agd.id, ipv4agd.assetGroupId,
ipv4agd.ipStart, ipv4agd.ipEnd FROM TABLE (assetGroupId bigint = ? ) temp
JOIN IpV4AssetGroupData ipv4agd ON ipv4agd.assetGroupId = temp.assetGroupId
WHERE subscriptionId = ? ORDER BY ipv4agd.assetGroupId
getAffectedIPRange_3 :: TimeTakenToComplete=11 :: Size=1295

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 17:46, Prasad Bhalerao :

> Can someone from community help me with t
>
> I have created a reproducer and uploaded it to GitHub. I have created 3
> cases to test the sql execution time.
>
> Please run *IgniteQueryTester_4* class to check the issue.
> GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git
>
> Thanks,
> Prasad
>
>
> On Wed, Dec 26, 2018 at 11:18 PM Prasad Bhalerao <
> prasadbhalerao1...@gmail.com> wrote:
>
>> How to push the ids to temp table, can you please give any example?
>> Is it a in memory temp table created by ignite?
>>
>> Can you please explain how enforceJoinOrder will help in this case?
>> Thanks ,
>> Prasad
>>
>> On Wed 26 Dec, 2018, 9:37 PM Ilya Kasnacheev > wrote:
>>
>>> Hello!
>>>
>>> Can you try pushing temp table to 1st position and setting
>>> enforceJoinOrder=true?
>>>
>>> SELECT ipv4agd.id,
>>>   ipv4agd.assetGroupId,
>>>   ipv4agd.ipStart,
>>>   ipv4agd.ipEnd
>>> FROM TABLE (assetGroupId bigint = ? ) temp
>>> JOIN IpV4AssetGroupData ipv4agd
>>> ON ipv4agd.assetGroupId = temp.assetGroupId
>>> WHERE subscriptionId= ?
>>> AND (ipStart <= ? AND ipEnd >= ?)
>>> ORDER BY ipv4agd.assetGroupId
>>>
>>> See https://apacheignite.readme.io/docs/configuration-parameters for
>>> enforceJoinOrder.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 26 дек. 2018 г. в 19:01, Prasad Bhalerao <
>>> prasadbhalerao1...@gmail.com>:
>>>
 I am executing following SQL on ignite cache. This cache has 37 million
 records and this data is distributed across 4 nodes.
 *SQL:*
 SELECT ipv4agd.id,
   ipv4agd.assetGroupId,
   ipv4agd.ipStart,
   ipv4agd.ipEnd
 FROM IpV4AssetGroupData ipv4agd
 JOIN TABLE (assetGroupId bigint = ? ) temp
 ON ipv4agd.assetGroupId = temp.assetGroupId
 WHERE subscriptionId= ?
 AND (ipStart <= ? AND ipEnd >= ?)
 ORDER BY ipv4agd.assetGroupId


 As per the execution plan show below, ignite is using index
 "IPV4_ASSET_GROUP_DATA_IDX2 " and execution plan attached below.

 This sql is taking around 23 seconds. I have set the max index inline
 size as 65 bytes.
 The number of assetGroupIds set in join clause are 50.

 *Is there anything I can do to improve the performance of this SQL?*

 I have checked the memory and cpu utilization and it it is very low. I
 also tried to profile it using jprofiler to find out the issue, but could
 not find solution. I have also attached profiler snapshot at the end.
 Please check.


 .

 *Indexes:*

 public class IpV4AssetGroupData implements 
 UpdatableData {

   @QuerySqlField
   private long id;
   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
 "ipv4_asset_group_data_idx2", order = 2)})
   private long assetGroupId;
   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
 "ipv4_asset_group_data_idx1", order = 1),
   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
 1)})
   private long subscriptionId;
   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
 "ipv4_asset_group_data_idx1", order = 2),
   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
 3)})
   private int ipStart;
   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
 "ipv4_asset_group_data_idx1", order = 3),
   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 
 4)})
   private int ipEnd;

 }

 *Execution plan:*

 Query execution is too long [time=15788 ms, sql='SELECT
 IPV4AGD__Z0.ID __C0_0,
 IPV4AGD__Z0.ASSETGROUPID __C0_1,
 IPV4AGD__Z0.IPSTART __C0_2,
 IPV4AGD__Z0.IPEND __C0_3
 FROM IPV4_ASSET_GROUP_DETAIL_CACHE.IPV4ASSETGROUPDATA IPV4AGD__Z0
  INNER JOIN TABLE(ASSETGROUPID BIGINT=?1) TEMP__Z1
  ON TRUE
 WHERE (IPV4AGD__Z0.ASSETGROUPID = TEMP__Z1.ASSETGROUPID) AND
 ((IPV4AGD__Z0.SUBSCRIPTIONID = ?2) AND ((IPV4AGD__Z0.IPSTART <= ?3) AND
 (IPV4AGD__Z0.IPEND >= ?4)))
 ORDER BY 2',

 plan=

 SELECT
 IPV4AGD__Z0.ID AS __C0_0,
 IPV4AGD__Z0.ASSETGROUPID AS __C0_1,
 IPV4AGD__Z0.IPSTART AS __C0_2,
 IPV4AGD__Z0.IPEND AS __C0_3
 FROM IPV4_ASSET_GROUP_DETAIL_CACHE.IPV4ASSETGROUPDATA IPV4AGD__Z0
 /* IPV4_ASSET_GROUP_DETAIL_CACHE.IPV4_ASSET_GROUP_DATA_IDX2:
 

Re: Query Execution very slow

[Prasad Bhalerao]

Can someone from community help me with t

I have created a reproducer and uploaded it to GitHub. I have created 3
cases to test the sql execution time.

Please run *IgniteQueryTester_4* class to check the issue.
GitHub project: https://github.com/prasadbhalerao1983/IgniteTestPrj.git

Thanks,
Prasad


On Wed, Dec 26, 2018 at 11:18 PM Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:

> How to push the ids to temp table, can you please give any example?
> Is it a in memory temp table created by ignite?
>
> Can you please explain how enforceJoinOrder will help in this case?
> Thanks ,
> Prasad
>
> On Wed 26 Dec, 2018, 9:37 PM Ilya Kasnacheev  wrote:
>
>> Hello!
>>
>> Can you try pushing temp table to 1st position and setting
>> enforceJoinOrder=true?
>>
>> SELECT ipv4agd.id,
>>   ipv4agd.assetGroupId,
>>   ipv4agd.ipStart,
>>   ipv4agd.ipEnd
>> FROM TABLE (assetGroupId bigint = ? ) temp
>> JOIN IpV4AssetGroupData ipv4agd
>> ON ipv4agd.assetGroupId = temp.assetGroupId
>> WHERE subscriptionId= ?
>> AND (ipStart <= ? AND ipEnd >= ?)
>> ORDER BY ipv4agd.assetGroupId
>>
>> See https://apacheignite.readme.io/docs/configuration-parameters for
>> enforceJoinOrder.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 26 дек. 2018 г. в 19:01, Prasad Bhalerao <
>> prasadbhalerao1...@gmail.com>:
>>
>>> I am executing following SQL on ignite cache. This cache has 37 million
>>> records and this data is distributed across 4 nodes.
>>> *SQL:*
>>> SELECT ipv4agd.id,
>>>   ipv4agd.assetGroupId,
>>>   ipv4agd.ipStart,
>>>   ipv4agd.ipEnd
>>> FROM IpV4AssetGroupData ipv4agd
>>> JOIN TABLE (assetGroupId bigint = ? ) temp
>>> ON ipv4agd.assetGroupId = temp.assetGroupId
>>> WHERE subscriptionId= ?
>>> AND (ipStart <= ? AND ipEnd >= ?)
>>> ORDER BY ipv4agd.assetGroupId
>>>
>>>
>>> As per the execution plan show below, ignite is using index
>>> "IPV4_ASSET_GROUP_DATA_IDX2 " and execution plan attached below.
>>>
>>> This sql is taking around 23 seconds. I have set the max index inline
>>> size as 65 bytes.
>>> The number of assetGroupIds set in join clause are 50.
>>>
>>> *Is there anything I can do to improve the performance of this SQL?*
>>>
>>> I have checked the memory and cpu utilization and it it is very low. I
>>> also tried to profile it using jprofiler to find out the issue, but could
>>> not find solution. I have also attached profiler snapshot at the end.
>>> Please check.
>>>
>>>
>>> .
>>>
>>> *Indexes:*
>>>
>>> public class IpV4AssetGroupData implements 
>>> UpdatableData {
>>>
>>>   @QuerySqlField
>>>   private long id;
>>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>>> "ipv4_asset_group_data_idx2", order = 2)})
>>>   private long assetGroupId;
>>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>>> "ipv4_asset_group_data_idx1", order = 1),
>>>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 1)})
>>>   private long subscriptionId;
>>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>>> "ipv4_asset_group_data_idx1", order = 2),
>>>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 3)})
>>>   private int ipStart;
>>>   @QuerySqlField(orderedGroups = {@QuerySqlField.Group(name = 
>>> "ipv4_asset_group_data_idx1", order = 3),
>>>   @QuerySqlField.Group(name = "ipv4_asset_group_data_idx2", order = 4)})
>>>   private int ipEnd;
>>>
>>> }
>>>
>>> *Execution plan:*
>>>
>>> Query execution is too long [time=15788 ms, sql='SELECT
>>> IPV4AGD__Z0.ID __C0_0,
>>> IPV4AGD__Z0.ASSETGROUPID __C0_1,
>>> IPV4AGD__Z0.IPSTART __C0_2,
>>> IPV4AGD__Z0.IPEND __C0_3
>>> FROM IPV4_ASSET_GROUP_DETAIL_CACHE.IPV4ASSETGROUPDATA IPV4AGD__Z0
>>>  INNER JOIN TABLE(ASSETGROUPID BIGINT=?1) TEMP__Z1
>>>  ON TRUE
>>> WHERE (IPV4AGD__Z0.ASSETGROUPID = TEMP__Z1.ASSETGROUPID) AND
>>> ((IPV4AGD__Z0.SUBSCRIPTIONID = ?2) AND ((IPV4AGD__Z0.IPSTART <= ?3) AND
>>> (IPV4AGD__Z0.IPEND >= ?4)))
>>> ORDER BY 2',
>>>
>>> plan=
>>>
>>> SELECT
>>> IPV4AGD__Z0.ID AS __C0_0,
>>> IPV4AGD__Z0.ASSETGROUPID AS __C0_1,
>>> IPV4AGD__Z0.IPSTART AS __C0_2,
>>> IPV4AGD__Z0.IPEND AS __C0_3
>>> FROM IPV4_ASSET_GROUP_DETAIL_CACHE.IPV4ASSETGROUPDATA IPV4AGD__Z0
>>> /* IPV4_ASSET_GROUP_DETAIL_CACHE.IPV4_ASSET_GROUP_DATA_IDX2:
>>> SUBSCRIPTIONID = ?2
>>> AND IPSTART <= ?3
>>> AND IPEND >= ?4
>>>  */
>>> /* WHERE (IPV4AGD__Z0.IPEND >= ?4)
>>> AND ((IPV4AGD__Z0.SUBSCRIPTIONID = ?2)
>>> AND (IPV4AGD__Z0.IPSTART <= ?3))
>>> */
>>> INNER JOIN TABLE(ASSETGROUPID BIGINT=?1) TEMP__Z1
>>> /* function: ASSETGROUPID = IPV4AGD__Z0.ASSETGROUPID */
>>> ON 1=1
>>> WHERE (IPV4AGD__Z0.ASSETGROUPID = TEMP__Z1.ASSETGROUPID)
>>> AND ((IPV4AGD__Z0.SUBSCRIPTIONID = ?2)
>>> AND ((IPV4AGD__Z0.IPSTART <= ?3)
>>> AND (IPV4AGD__Z0.IPEND >= ?4)))
>>> ORDER BY 2
>>> , parameters=[[3483555, 3180458, 3250090, 3483563, 3182509, 3213230,
>>> 3245998, 3487661, 3215281, 3444657, 3182515, 

Re: ignite stops expiring caches after a period of time

[Ilya Kasnacheev]

Hello!

Since Ignite 2.0 works with OffHeap pages mostly, Page Eviction works best
if you don't care about data (pure cache mode):
https://apacheignite.readme.io/docs/evictions

If it works for 2.7.0 I recommend you to stick with is, since if one would
be fixing 2.6 they will yield 2.7 anyway :)

Regards,
-- 
Ilya Kasnacheev


ср, 26 дек. 2018 г. в 22:25, Scott Feldstein :

> hi Ilya,
> Why wouldn't many people use Expiry with 2.x?  Is there another feature
> that I should be using that accomplishes the same thing?
>
> I've reproduced the issue for 2.6.0, but with 2.7.0 it looks like it is
> working.  Here is the repro if anyone is interested -
>
> https://github.com/scottmf/ignite-expiry-repro
>
> On Tue, Dec 25, 2018 at 5:30 AM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> Not many people are using Expiry with 2.x.
>>
>> If you can share a reproducer, please create a ticket right away and I
>> hope that somebody will look into it.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> вт, 25 дек. 2018 г. в 01:36, Scott Feldstein :
>>
>>> Thanks Ilya, I’ll upgrade and see if that works soon. Right now we’ve
>>> switched to only using partitioned caches to avoid this issue. If it’s
>>> something that isn’t fixed with 2.7 then I’ll create a bug and attach code
>>> to reproduce it.
>>>
>>> I’m really surprised that no one else is complaining about it. The repro
>>> is very straight forward..
>>>
>>>
>>> On Mon, Dec 24, 2018 at 06:36 Ilya Kasnacheev 
>>> wrote:
>>>
 Hello!

 There could be fixes for expiration between 2.6 and 2.7.

 However, if it will still be the case, we would be glad if you could
 post reproducer for this behavior.

 Note that you can almost emulate replicated cache by creating
 partitioned cache with large number of backups, maybe you should be using
 that in the meantime.

 Regards,

 --
 Ilya Kasnacheev


 пт, 21 дек. 2018 г. в 23:28, scottmf :

> I forgot to mention this is on Ignite 2.6.0 and i'm running with a 3
> node
> cluster.
>
> I've been experimenting some more and I'm finding that using
> PARTITIONED
> caches works fine, but replicated caches stop expiring usually within
> 10
> minutes.  The behavior is very consistent.
>
> I plan on trying this with Ignite 2.7.0...
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite Data streamer optimization

[Ilya Kasnacheev]

Hello!

Maybe times have changed but it used to be that the best optimization was
to feed DataStreamer's addData() from multiple threads in parallel.

Can you try that?

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 14:32, ashishb888 :

> I am using below settings:
> allowOverwrite: false
> nodeParallelOperations: 1
> autoFlushFrequency: 10
> perNodeBufferSize: 500
>
>
> My records size is around 2000 bytes. And see the
> "grid-data-loader-flusher"
> thread stats as below:
>
> Thread  Count   Average Longest Duration
> grid-data-loader-flusher-#100   38  4,737,793.579   30,427,862
> 180,036,156
>
> What would be the best configurations for Data streamer?
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: error in running shared rdd example with intellij

[Ilya Kasnacheev]

Hello!

Looks like this node is started in client node, but you don't have server
nodes available for it to connect to.

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 15:59, mehdi sey :

> hi i want to run SharedRddExample in intellij IDE. but i have encounter
> error
> just as bellow . why?
> /usr/lib/jvm/java-8-oracle/bin/java
> -DIGNITE_HOME=/usr/local/apache-ignite-fabric-2.6.0-bin/
>
> -javaagent:/snap/intellij-idea-community/109/lib/idea_rt.jar=35933:/snap/intellij-idea-community/109/bin
> -Dfile.encoding=UTF-8 -classpath
>
> 

Re: error in ignite-spark

[Ilya Kasnacheev]

Hello!

This is not an error, see "BUILD SUCCESS".

You should consult netbeans' and IDEA's documentation with regard to how to
use Maven inside of them.

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 14:46, Mehdi Seydali :

> after running example i have encounter the following error attache. why?
>
> On Wed, Dec 26, 2018 at 4:04 PM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> No you don't.
>>
>> You can use the following maven commands from examples directory to run
>> example:
>>
>> mvn clean install -Pscala -DskipTests
>> mvn -Pscala exec:java
>> -Dexec.mainClass=org.apache.ignite.examples.spark.SharedRDDExample
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 26 дек. 2018 г. в 13:42, Mehdi Seydali :
>>
>>> spark example have been written with java not scala. i think this error
>>> relate to spark version. i have another question. for running this example
>>> is it  necessary to intsall spark before running?.
>>>
>>> On Wed, Dec 26, 2018 at 1:44 PM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 Hello!

 You have to enable 'scala' profile in Maven to be able to build Spark
 examples. However, even after I rebuild with scala profile, netbeans will
 not show them propetly. You will still be able to run them all right, I
 think.

 Regards,
 --
 Ilya Kasnacheev


 ср, 26 дек. 2018 г. в 12:27, mehdi sey :

> hi. i want to execute a RDD example in spark from example folder of
> ignite
> 2.7, but i have encounter and error just like an attached picture. in
> import
> section you see an underlined line. i have added dependency but still
> is
> remained why?
>
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-31-16.png>
>
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-34-19.png>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

error in running shared rdd example with intellij

[mehdi sey]

hi i want to run SharedRddExample in intellij IDE. but i have encounter error
just as bellow . why?
/usr/lib/jvm/java-8-oracle/bin/java
-DIGNITE_HOME=/usr/local/apache-ignite-fabric-2.6.0-bin/
-javaagent:/snap/intellij-idea-community/109/lib/idea_rt.jar=35933:/snap/intellij-idea-community/109/bin
-Dfile.encoding=UTF-8 -classpath

Re: error in ignite-spark

[Mehdi Seydali]

yes  i have considered intellij. how i could use it?

On Fri, Dec 28, 2018 at 2:27 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> Have you considered installing IDEA? Developing Ignite under Netbeans or
> Eclipse is an expert option which is clearly not your case.
>
> Otherwise you can start with
> https://maven.apache.org/guides/introduction/introduction-to-profiles.html
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 28 дек. 2018 г. в 10:09, Mehdi Seydali :
>
>> 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 <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> With -Pscala command or via netbeans dialogs.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 26 дек. 2018 г. в 19:54, Mehdi Seydali :
>>>
 How could i enable scala profile??

 On Wed, 26 Dec 2018, 13:44 Ilya Kasnacheev, 
 wrote:

> Hello!
>
> You have to enable 'scala' profile in Maven to be able to build Spark
> examples. However, even after I rebuild with scala profile, netbeans will
> not show them propetly. You will still be able to run them all right, I
> think.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 26 дек. 2018 г. в 12:27, mehdi sey :
>
>> hi. i want to execute a RDD example in spark from example folder of
>> ignite
>> 2.7, but i have encounter and error just like an attached picture. in
>> import
>> section you see an underlined line. i have added dependency but still
>> is
>> remained why?
>>
>> <
>> http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-31-16.png>
>>
>> <
>> http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-34-19.png>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>

Re: Ignite Data streamer optimization

[Denis Mekhanikov]

To achieve the best data streaming performance, you should
aim at highest utilization of resources on data nodes.
There is no silver bullet for data streamer tuning, unfortunately.
Try changing parameters and see, how they affect the utilization and
overall performance.

For me default data streamer parameters usually work fine.
Your value of perNodeBufferSize looks too big. It's measured in records,
not bytes.
By default it's 512.

Denis

пт, 28 дек. 2018 г. в 14:32, ashishb888 :

> I am using below settings:
> allowOverwrite: false
> nodeParallelOperations: 1
> autoFlushFrequency: 10
> perNodeBufferSize: 500
>
>
> My records size is around 2000 bytes. And see the
> "grid-data-loader-flusher"
> thread stats as below:
>
> Thread  Count   Average Longest Duration
> grid-data-loader-flusher-#100   38  4,737,793.579   30,427,862
> 180,036,156
>
> What would be the best configurations for Data streamer?
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Data Replication Between Ignite Clusters Through Kafka

[akurbanov]

Hello,

Well, you have java.lang.NoClassDefFoundError:
org/apache/ignite/internal/util/typedef/internal/A as a cause, my guess is
that you have different versions of Ignite at compile time and runtime.
Could you please verify your dependencies in project or share it?

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: error in ignite-spark

[Mehdi Seydali]

with those command that you said i coud run in command line. but how i
could run it in intellij or in netbeans? how i could enabled scala profile
in netbeans or intellij?

On Wed, Dec 26, 2018 at 4:04 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> No you don't.
>
> You can use the following maven commands from examples directory to run
> example:
>
> mvn clean install -Pscala -DskipTests
> mvn -Pscala exec:java
> -Dexec.mainClass=org.apache.ignite.examples.spark.SharedRDDExample
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 26 дек. 2018 г. в 13:42, Mehdi Seydali :
>
>> spark example have been written with java not scala. i think this error
>> relate to spark version. i have another question. for running this example
>> is it  necessary to intsall spark before running?.
>>
>> On Wed, Dec 26, 2018 at 1:44 PM Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> You have to enable 'scala' profile in Maven to be able to build Spark
>>> examples. However, even after I rebuild with scala profile, netbeans will
>>> not show them propetly. You will still be able to run them all right, I
>>> think.
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> ср, 26 дек. 2018 г. в 12:27, mehdi sey :
>>>
 hi. i want to execute a RDD example in spark from example folder of
 ignite
 2.7, but i have encounter and error just like an attached picture. in
 import
 section you see an underlined line. i have added dependency but still is
 remained why?

 <
 http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-31-16.png>

 <
 http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-34-19.png>




 --
 Sent from: http://apache-ignite-users.70518.x6.nabble.com/

>>>

Ignite Data streamer optimization

[ashishb888]

I am using below settings:
allowOverwrite: false
nodeParallelOperations: 1
autoFlushFrequency: 10
perNodeBufferSize: 500


My records size is around 2000 bytes. And see the "grid-data-loader-flusher"
thread stats as below:

Thread  Count   Average Longest Duration
grid-data-loader-flusher-#100   38  4,737,793.579   30,427,862  
180,036,156

What would be the best configurations for Data streamer?

Thanks



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Multithreading in Compute Task

[Denis Mekhanikov]

Both approaches are valid, so you may use whatever works better for you.
Just make sure not to run tasks, that may end up in the same thread pool,
if you depend on their results. Otherwise thread pool starvation is
possible.

Custom thread pools are designed for executing tasks from other tasks:
https://apacheignite.readme.io/docs/thread-pools#section-custom-thread-pools
But if you only need to perform an asynchronous operation, then a simple
Java thread pool could work.

Denis


сб, 22 дек. 2018 г. в 20:43, kellan :

> Hi,
> I have a compute task that needs to query the local data set several
> hundred
> times per task. Creating another task in a custom thread pool seems to be
> the preferred method of multithreading within an already running compute
> task, but I find the overhead a bit slow. I've tried running Scala futures
> within the task, which gives me the desired results, but I've noticed some
> unexpected behavior, like the task freezing (possibly thread pool
> starvation, I'm not sure). Is there a safe, efficient way to run futures
> within a task that I know are only going to operate only on the local data
> set?
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: error in ignite-spark

[Ilya Kasnacheev]

Hello!

Have you considered installing IDEA? Developing Ignite under Netbeans or
Eclipse is an expert option which is clearly not your case.

Otherwise you can start with
https://maven.apache.org/guides/introduction/introduction-to-profiles.html

Regards,
-- 
Ilya Kasnacheev


пт, 28 дек. 2018 г. в 10:09, Mehdi Seydali :

> 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 :
>>
>>> How could i enable scala profile??
>>>
>>> On Wed, 26 Dec 2018, 13:44 Ilya Kasnacheev, 
>>> wrote:
>>>
 Hello!

 You have to enable 'scala' profile in Maven to be able to build Spark
 examples. However, even after I rebuild with scala profile, netbeans will
 not show them propetly. You will still be able to run them all right, I
 think.

 Regards,
 --
 Ilya Kasnacheev


 ср, 26 дек. 2018 г. в 12:27, mehdi sey :

> hi. i want to execute a RDD example in spark from example folder of
> ignite
> 2.7, but i have encounter and error just like an attached picture. in
> import
> section you see an underlined line. i have added dependency but still
> is
> remained why?
>
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-31-16.png>
>
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t2160/Screenshot_from_2018-12-26_10-34-19.png>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

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

[Denis Mekhanikov]

Try substituting personalDetails.F_id with a value from the record,
that you expect to be updated, and try running the subquery on its own.
Make sure, that the result is not empty.

Denis

пт, 28 дек. 2018 г. в 13:14, DS :

> Denis Mekhanikov wrote
> > Is it a single query? Why not execute these two updates separately?
> > I don't see any problems in the first one.
> >
> > The second one needs some refactoring though.
> > Ignite uses an SQL query engine of H2, which doesn't support JOINs in
> > UPDATE statements.
> > But you may change it in the following way:
> >
> > UPDATE table1 SET table1.quantity = 6 WHERE EXISTS
> >
> > (SELECT * FROM table2 WHERE table2.pid=table1.pid AND table2.zip
> > ='abc')
> > ;
> >
> >
> > Denis
> >
> > чт, 27 дек. 2018 г. в 12:49, DS 
>
> > deepika.singh@
>
> > :
> >
> >> 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.nabble.com/
> >>
>
>  Query i ran  over GridGain :
>
> UPDATE personalDetails SET personalDetails.age = 26
> WHERE EXISTS (SELECT * FROM cityDEtails WHERE
>  cityDEtails.id=personalDetails.F_id AND cityDEtails.pincode = 560102)
>
> It ran but didn't update the value ?? .
>
> any idea why?
>
>
>
>
>
>
> --
> 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]

[aealexsandrov]

Hi,

I was able to reproduce this issue. The details you can see at the next
ticket:

https://issues.apache.org/jira/browse/IGNITE-10840

BR,
Andrei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Can we put a timeout on Ignite.close ?

[userx]

Thank you.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Can Ignite code throw any RuntimeExceptions ?

[Denis Mekhanikov]

Usually Ignite methods throw exceptions with some
general description and a cause exception wrapped into them.

I can't remember, if there is any place, where a non-Ignite exception is
thrown from Ignite
method. Let us know, if you find one.

Denis

чт, 27 дек. 2018 г. в 09:59, userx :

> Hi
>
> Let say we have a java program which starts Ignite in a client mode. Let us
> say there is a RuntimeException which happens in the Ignite code (on the
> client side only), would it be wrapped as an IgniteException and passed to
> the Java client or would it be thrown as a RuntimeException to the java
> program under any circumstances ?
>
> I have seen most of the methods declaring throws IgniteException but just
> thinking about any scenario where in a RuntimeException occurs and get
> passed to the client.
>
> Regards
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

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

[DS]

Denis Mekhanikov wrote
> Is it a single query? Why not execute these two updates separately?
> I don't see any problems in the first one.
> 
> The second one needs some refactoring though.
> Ignite uses an SQL query engine of H2, which doesn't support JOINs in
> UPDATE statements.
> But you may change it in the following way:
> 
> UPDATE table1 SET table1.quantity = 6 WHERE EXISTS
> 
> (SELECT * FROM table2 WHERE table2.pid=table1.pid AND table2.zip
> ='abc')
> ;
> 
> 
> Denis
> 
> чт, 27 дек. 2018 г. в 12:49, DS 

> deepika.singh@

> :
> 
>> 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.nabble.com/
>>

 Query i ran  over GridGain :

UPDATE personalDetails SET personalDetails.age = 26
WHERE EXISTS (SELECT * FROM cityDEtails WHERE
 cityDEtails.id=personalDetails.F_id AND cityDEtails.pincode = 560102)

It ran but didn't update the value ?? .

any idea why?






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Can we put a timeout on Ignite.close ?

[Denis Mekhanikov]

Ignite.close() effectively does exactly what you described.
It tries to stop all threads as fast as possible by interrupting them.
But some threads may be doing some blocking operations at the moment,
so they are not killed instantaneously.
For example, if you try to stop a node in the middle of a checkpoint, then
the close() method may hang until a disk write operation finishes.

You can take a thread dump and analyze it to figure out, what's blocking
the close. Logs also may contain useful information on this matter.

If you need to stop Ignite asynchronously, you can start a new thread
and call Ignite#close() from it.

Denis

ср, 26 дек. 2018 г. в 16:55, userx :

> Hi
>
> Is there a way we can put a timeout on close operation of Ignite. For an
> example I have a java program which does some computation and then starts
> the Ignite in client mode so that the computed numbers can be written to
> cache on Ignite Servers in persistent mode. Say if there is an execution
> exception, I would want the java program to call close on the Ignite
> started
> in the client mode and return to its normal processing with in a specified
> time say 5 seconds or so ?
> Which means that if the ignite in the client mode is not getting closed in
> 5
> seconds, all the ignite threads started on the client side should be
> interrupted and should be closed/killed/stopped.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

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

[Denis Mekhanikov]

Is it a single query? Why not execute these two updates separately?
I don't see any problems in the first one.

The second one needs some refactoring though.
Ignite uses an SQL query engine of H2, which doesn't support JOINs in
UPDATE statements.
But you may change it in the following way:

UPDATE table1 SET table1.quantity = 6 WHERE EXISTS

(SELECT * FROM table2 WHERE table2.pid=table1.pid AND table2.zip ='abc')
;


Denis

чт, 27 дек. 2018 г. в 12:49, DS :

> 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.nabble.com/
>

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

[yangjiajun]

Hello.Thanks for your reply.

I want to make such settings global.Do this settings only affect specific
caches?


ezhuravlev wrote
> 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 <

> 1371549332@

>>:
> 
>> 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 invalid: Cache
>> name must not be null or empty.
>> at
>>
>> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
>> at org.apache.ignite.Ignition.start(Ignition.java:355)
>> at
>>
>> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
>> Caused by: class org.apache.ignite.IgniteCheckedException: Ouch! Argument
>> is
>> invalid: Cache name must not be null or empty.
>> at
>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1133)
>> at
>>
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
>> at
>>
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
>> at
>> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
>> at
>>
>> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
>> at org.apache.ignite.Ignition.start(Ignition.java:352)
>> ... 1 more
>> Caused by: java.lang.IllegalArgumentException: Ouch! Argument is invalid:
>> Cache name must not be null or empty.
>> at
>>
>> org.apache.ignite.internal.util.GridArgumentCheck.ensure(GridArgumentCheck.java:109)
>> at
>>
>> org.apache.ignite.internal.processors.cache.GridCacheUtils.validateCacheName(GridCacheUtils.java:1590)
>> at
>>
>> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoin(GridCacheProcessor.java:738)
>> at
>>
>> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:808)
>> at
>>
>> org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:707)
>> at
>>
>> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
>> at
>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:980)
>> ... 10 more
>> Failed to start grid: Ouch! Argument is invalid: Cache name must not be
>> null
>> or empty.
>>
>>
>> Here is my config file:
>> example-default2.xml
>> <
>> http://apache-ignite-users.70518.x6.nabble.com/file/t2059/example-default2.xml>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/