[jira] [Created] (IGNITE-7495) Ability to disable WAL globally for data region

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7495:
---

 Summary: Ability to disable WAL globally for data region
 Key: IGNITE-7495
 URL: https://issues.apache.org/jira/browse/IGNITE-7495
 Project: Ignite
  Issue Type: New Feature
  Components: cache
Reporter: Vladimir Ozerov
 Fix For: 2.5


Recently we introduced a set of commands to control WAL state of particular 
caches. I.e. using SQL API user could do the following to disable WAL in order 
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}

Now consider that user has a lot of tables and would like to disable WAL for 
the whole data region at once (e.g. to load data for the whole schema). 
Currently to achieve this he would have to issue a number of commands for each 
and every table. 

Instead, we should provide tiered approach, when user could disable WAL for 
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING; // Disable for table
{code}

*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be 
possible to have a data region with disabled WAL, while still being able to 
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
handling.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7494) WAL management commands for control.sh script

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7494:
---

 Summary: WAL management commands for control.sh script
 Key: IGNITE-7494
 URL: https://issues.apache.org/jira/browse/IGNITE-7494
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.5


Need to add WAL mode management commands for {{control.sh}} script:
- enableWal
- disableWal
- isWalEnabled

See {{IgniteCluster}} API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7493) Propagate WAL management API to .NET

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7493:
---

 Summary: Propagate WAL management API to .NET
 Key: IGNITE-7493
 URL: https://issues.apache.org/jira/browse/IGNITE-7493
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Vladimir Ozerov
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Need to add the following methods to .NET:
{code}
ICluster.disableWal member is missing in .NET.
ICluster.enableWal member is missing in .NET.
ICluster.isWalEnabled member is missing in .NET.
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: cache operation failed after transaction rolled back due to deadlock

[ALEKSEY KUZNETSOV]

created ticket with reproducer [1] 

I think the fix should be to clear context in tx.close()

[1] https://issues.apache.org/jira/browse/IGNITE-7486

> 23 янв. 2018 г., в 1:56, Yakov Zhdanov  написал(а):
> 
> Guys, can you check if you call tx.close(); or properly use
> try-with-resources construct?
> 
> Tx context should not be cleared automatically otherwise user would not get
> any notification that original transaction failed. I believe context should
> be cleared on tx.close().
> 
> Anyway, let's take a look at reproducer from Alexey first.
> 
> --Yakov
> 
> 2018-01-22 2:02 GMT-08:00 ALEKSEY KUZNETSOV :
> 
>> Sure
>> 
>> пн, 22 янв. 2018 г. в 12:25, Andrey Gura :
>> 
>>> It seems that problem isn't related with deadlock detection and should be
>>> reproducible when deadlock detection disabled.
>>> 
>>> Anyway it sounds like a bug. Could you please file a ticket and provide
>>> minimal reproducer?
>>> 
>>> 19 янв. 2018 г. 3:55 PM пользователь "ALEKSEY KUZNETSOV" <
>>> alkuznetsov...@gmail.com> написал:
>>> 
 Hi, Igntrs!
 
 
 
 When you have your transaction rolled back due to detected deadlock,
>> you
 are unabled to perform cache operations (in thread where tx was started
>>> and
 rolled back), because it leads to TransactionTimeoutException.
 
 
 
 The reason of such behavior is that tx thread map (txManager#threadMap)
>>> was
 not cleared from tx when roll back occured.
 
 In GridNearTxLocal#onTimeout you can find comment on that :
 
 *// Note: if rollback asynchronously on timeout should not clear thread
 map*
 
 *// since thread started tx still should be able to see this tx.*
 
 Cache operation picks up tx from that map and throws exception.
 
 
 
 So, one must create new thread in order to perform cache operations?
 
 
 --
 
 *Best Regards,*
 
 *Kuznetsov Aleksey*
 
>>> 
>> 
>> 
>> --
>> 
>> *Best Regards,*
>> 
>> *Kuznetsov Aleksey*
>> 

[jira] [Created] (IGNITE-7492) Implement metrics for Memory Regions in UI tools

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7492:


 Summary: Implement metrics for Memory Regions in UI tools
 Key: IGNITE-7492
 URL: https://issues.apache.org/jira/browse/IGNITE-7492
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


See IGNITE-6920 for list of metrics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Partition loss policy to disable cache completely

[Yakov Zhdanov]

Val,

Your suggestion to prohibit any cache operation on partition loss does not
make sense to me. Why should I care about some partition during particular
operation if I don't access it? Imagine I use data on nodes A and B
performing reads and writes and node C crashes in the middle of tx. Should
my tx be rolled back? I think no.

As far as difference it seems that IGNORE resets lost status for affected
partitions and READ_WRITE_ALL does not.

* @see Ignite#resetLostPartitions(Collection)
* @see IgniteCache#lostPartitions()

--Yakov

2018-01-17 14:36 GMT-08:00 Valentin Kulichenko <
valentin.kuliche...@gmail.com>:

> Folks,
>
> Our PartitionLossPolicy allows to disable operations on lost partitions,
> however all available policies allow any operations on partitions that were
> not lost. It seems to me it can be very useful to also have a policy that
> completely blocks the cache in case of data loss. Is it possible to add
> one?
>
> And as a side question: what is the difference between READ_WRITE_ALL and
> IGNORE policies? Looks like both allow both read and write on all
> partitions.
>
> -Val
>

Re: cache operation failed after transaction rolled back due to deadlock

[Yakov Zhdanov]

Guys, can you check if you call tx.close(); or properly use
try-with-resources construct?

Tx context should not be cleared automatically otherwise user would not get
any notification that original transaction failed. I believe context should
be cleared on tx.close().

Anyway, let's take a look at reproducer from Alexey first.

--Yakov

2018-01-22 2:02 GMT-08:00 ALEKSEY KUZNETSOV :

> Sure
>
> пн, 22 янв. 2018 г. в 12:25, Andrey Gura :
>
> > It seems that problem isn't related with deadlock detection and should be
> > reproducible when deadlock detection disabled.
> >
> > Anyway it sounds like a bug. Could you please file a ticket and provide
> > minimal reproducer?
> >
> > 19 янв. 2018 г. 3:55 PM пользователь "ALEKSEY KUZNETSOV" <
> > alkuznetsov...@gmail.com> написал:
> >
> > > Hi, Igntrs!
> > >
> > >
> > >
> > > When you have your transaction rolled back due to detected deadlock,
> you
> > > are unabled to perform cache operations (in thread where tx was started
> > and
> > > rolled back), because it leads to TransactionTimeoutException.
> > >
> > >
> > >
> > > The reason of such behavior is that tx thread map (txManager#threadMap)
> > was
> > > not cleared from tx when roll back occured.
> > >
> > > In GridNearTxLocal#onTimeout you can find comment on that :
> > >
> > > *// Note: if rollback asynchronously on timeout should not clear thread
> > > map*
> > >
> > > *// since thread started tx still should be able to see this tx.*
> > >
> > > Cache operation picks up tx from that map and throws exception.
> > >
> > >
> > >
> > > So, one must create new thread in order to perform cache operations?
> > >
> > >
> > > --
> > >
> > > *Best Regards,*
> > >
> > > *Kuznetsov Aleksey*
> > >
> >
>
>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[jira] [Created] (IGNITE-7491) Documentation: add new data region metrics description

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-7491:


 Summary: Documentation: add new data region metrics description
 Key: IGNITE-7491
 URL: https://issues.apache.org/jira/browse/IGNITE-7491
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Andrey Kuznetsov
Assignee: Denis Magda
 Fix For: 2.4


Newly created data region metrics should be documented.

* `getTotalAllocatedSize` -- same as `getTotalAllocatedPages` but in bytes.
* `getPhysicalMemorySize` -- same as `getPhysicalMemoryPages` but in bytes.
* `getCheckpointBufferPages` -- gets checkpoint buffer size in pages.
* `getCheckpointBufferSize` -- gets checkpoint buffer size in bytes.
* `getPageSize` -- gets memory page size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3181: Ignite 6902

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

https://github.com/apache/ignite/pull/3181


---

[GitHub] ignite pull request #3401: IGNITE-6711: Squashed ignite-6711 branch.

[andrey-kuznetsov]

Github user andrey-kuznetsov closed the pull request at:

https://github.com/apache/ignite/pull/3401


---

[GitHub] ignite pull request #2283: IGNITE-5571

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/2283


---

[GitHub] ignite pull request #3335: Ignite 7003 1

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3335


---

Re: Hello

[Denis Magda]

Hi Roman and welcome to the Ignite community!

Added you to Ignite JIRA, so now you can assign tickets on yourself. Below you 
can find additional useful information.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list sharing 
your JIRA id, so we can add you as a contributor in Jira.

These are the easy tickets to start with:
https://issues.apache.org/jira/browse/IGNITE-4549?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN

While those are more advanced but appealing:
https://ignite.apache.org/community/contribute.html#pick-tickets 


Looking forward for your contributions!

—
Denis

> On Jan 22, 2018, at 4:23 AM, Roman Guseinov  wrote:
> 
> Hello Ignite Community!
> 
> My name is Roman. I want to contribute to Apache Ignite. Any help on this
> will be appreciated.
> 
> Thanks!
> 
> Best Regards, Roman
> Email: ro...@gromtech.ru
> Username at Jira: guseinov

Re: Apache Ignite 2.4 release

[Denis Magda]

Ok, let’s target Wednesday as a code freeze date.

Community members who are involved in 2.4 release please merge you fixes and 
optimizations by that time.

—
Denis

> On Jan 22, 2018, at 8:24 AM, Anton Vinogradov  wrote:
> 
> Issues
> https://issues.apache.org/jira/browse/IGNITE-6711
> https://issues.apache.org/jira/browse/IGNITE-6902
> 
> are in master and ignite-2.4
> 
> On Mon, Jan 22, 2018 at 6:43 PM, Denis Magda  wrote:
> 
>> Igniters,
>> 
>> What’s left and what prevents us from passing 2.4 through the QA phase?
>> 
>> Petr, Anton, Vladimir, Alex G., others please chime in.
>> 
>> —
>> Denis
>> 
>>> On Jan 17, 2018, at 7:05 PM, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> Great news, indeed! Looking forward to 2.4 release.
>>> 
>>> On Wed, Jan 17, 2018 at 2:55 AM, Vladimir Ozerov 
>>> wrote:
>>> 
 Igniters,
 
 Great news - two very important tickets - baseline topology and Java 8
 support - were merged to master. At this point it makes sense to create
>> a
 branch to stabilize the release and finalize outstanding tickets. I
>> created
 the branch *ignite-2.4*. Please follow the rules below when merging new
 commits to master:
 1) If ticket is targeted for 2.4 release, please merge to master, then
 cherry-pick to ignite-2.4
 2) Otherwise just merge to master.
 
 Vladimir.
 
 On Tue, Jan 16, 2018 at 12:32 PM, Anton Vinogradov <
 avinogra...@gridgain.com
> wrote:
 
> Denis,
> 
> I'll review https://issues.apache.org/jira/browse/IGNITE-6902
> 
> On Fri, Jan 12, 2018 at 11:45 PM, Denis Magda 
>> wrote:
> 
>> Here is the page create before:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4
>> <
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4>
>> 
>> This is good news. It will be perfect if we also release as many
> "required
>> tickets" as we can:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4
>> <
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4>
>> 
>> My favorite is memory metrics in bytes: https://issues.apache.org/
>> jira/browse/IGNITE-6902  jira/browse/IGNITE-6902
>>> 
>> 
>> The discussion lists are flooded with the demands for this essential
>> capability. Who is going to review it?
>> 
>> -
>> Denis
>> 
>>> On Jan 12, 2018, at 11:22 AM, Dmitriy Setrakyan <
 dsetrak...@apache.org
>> 
>> wrote:
>>> 
>>> +1
>>> 
>>> Do we have a list of features for 2.4 documented anywhere?
>>> 
>>> D.
>>> 
>>> On Fri, Jan 12, 2018 at 7:43 AM, Pavel Tupitsyn <
 ptupit...@apache.org>
>>> wrote:
>>> 
 +1
 
 But some stuff is not yet in master (like baseline topology), so it
 is
>> too
 soon to create a branch, I think.
 
 Pavel
 
 On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov <
> voze...@gridgain.com>
 wrote:
 
> Igniters,
> 
> A number of major improvements have been made (or being finalized
 at
>> the
> moment) to Ignite since recent 2.3 release. This includes baseline
> topology, new DDL commands, migration to Java 8 and Java 9 support,
> critical performance improvements to WAL, etc..
> 
> I think it makes sense to make a new release. What do you think if
 we
> release AI 2.4 with all this great stuff by the end of Jan?
> 
> If there are no objections, I'll create a branch to start
> stabilization
> process.
> 
> Vladimir.
> 
 
>> 
>> 
> 
 
>> 
>> 

Re: Ignite Semaphore Bug 7090

[Tim Onyschak]

Hey Vladisav,

I implemented your requests. Take a look, specifically, i created an
interface to encapsulate the NodeUpdates and let
the DataStructuresProcessor handle the execution by checking for one type
as opposed to multiple if checks. In this case it checks for
GridCacheNodeUpdate
instance and executes onNodeRemoved. Let me know what you think.

Thanks,
Tim



On Sat, Jan 20, 2018 at 8:10 AM, Vladisav Jelisavcic 
wrote:

> Hi Tim,
>
> I reviewed your contribution and left you some comments on the pr.
> Thanks!
>
> Vladisav
>
> On Wed, Jan 17, 2018 at 10:14 PM, Vladisav Jelisavcic  > wrote:
>
>> Hi Tim,
>>
>> thank you for the contribution!
>> I'll do the review soon and let you know.
>>
>>
>>
>> On Wed, Jan 17, 2018 at 8:56 AM, Yakov Zhdanov 
>> wrote:
>>
>>> Thanks Tim! I hope Vlad can review your patch. If this does not happen in
>>> 2-3 days I will take a look. Can you please let me know on weekend if I
>>> need to?
>>>
>>> --Yakov
>>>
>>> 2018-01-16 23:36 GMT+03:00 Tim Onyschak :
>>>
>>> > Hey all,
>>> >
>>> > I created a patch and posted to user group, was told feed back would be
>>> > left on the jira. I wanted to see if we could get a fix in with 2.4,
>>> could
>>> > somebody please review.
>>> >
>>> > http://apache-ignite-users.70518.x6.nabble.com/Semaphore-
>>> > Stuck-when-no-acquirers-to-assign-permit-td18639.html
>>> >
>>> > https://issues.apache.org/jira/browse/IGNITE-7090
>>> >
>>> > https://github.com/apache/ignite/pull/3138
>>> >
>>> > Thanks,
>>> > Tim
>>> >
>>>
>>
>>
>

[jira] [Created] (IGNITE-7490) Doc: clarify what's table name and how to change fields/indexes for QueryEntity/Annotations configs

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7490:
---

 Summary: Doc: clarify what's table name and how to change 
fields/indexes for QueryEntity/Annotations configs
 Key: IGNITE-7490
 URL: https://issues.apache.org/jira/browse/IGNITE-7490
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
Assignee: Denis Magda
 Fix For: 2.4


Users got confused on:
 * what should be a table name if SQL is configured with QueryEntity/Annotations
 * how to add/remove columns if QueryEntity/Annotations were used for initial 
configurations

http://apache-ignite-users.70518.x6.nabble.com/query-on-BinaryObject-index-and-table-td19631.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Apache Ignite 2.4 release

[Anton Vinogradov]

Issues
https://issues.apache.org/jira/browse/IGNITE-6711
https://issues.apache.org/jira/browse/IGNITE-6902

are in master and ignite-2.4

On Mon, Jan 22, 2018 at 6:43 PM, Denis Magda  wrote:

> Igniters,
>
> What’s left and what prevents us from passing 2.4 through the QA phase?
>
> Petr, Anton, Vladimir, Alex G., others please chime in.
>
> —
> Denis
>
> > On Jan 17, 2018, at 7:05 PM, Dmitriy Setrakyan 
> wrote:
> >
> > Great news, indeed! Looking forward to 2.4 release.
> >
> > On Wed, Jan 17, 2018 at 2:55 AM, Vladimir Ozerov 
> > wrote:
> >
> >> Igniters,
> >>
> >> Great news - two very important tickets - baseline topology and Java 8
> >> support - were merged to master. At this point it makes sense to create
> a
> >> branch to stabilize the release and finalize outstanding tickets. I
> created
> >> the branch *ignite-2.4*. Please follow the rules below when merging new
> >> commits to master:
> >> 1) If ticket is targeted for 2.4 release, please merge to master, then
> >> cherry-pick to ignite-2.4
> >> 2) Otherwise just merge to master.
> >>
> >> Vladimir.
> >>
> >> On Tue, Jan 16, 2018 at 12:32 PM, Anton Vinogradov <
> >> avinogra...@gridgain.com
> >>> wrote:
> >>
> >>> Denis,
> >>>
> >>> I'll review https://issues.apache.org/jira/browse/IGNITE-6902
> >>>
> >>> On Fri, Jan 12, 2018 at 11:45 PM, Denis Magda 
> wrote:
> >>>
>  Here is the page create before:
>  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4
> <
>  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4>
> 
>  This is good news. It will be perfect if we also release as many
> >>> "required
>  tickets" as we can:
>  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4
> <
>  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4>
> 
>  My favorite is memory metrics in bytes: https://issues.apache.org/
>  jira/browse/IGNITE-6902  >>> jira/browse/IGNITE-6902
> >
> 
>  The discussion lists are flooded with the demands for this essential
>  capability. Who is going to review it?
> 
>  -
>  Denis
> 
> > On Jan 12, 2018, at 11:22 AM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org
> 
>  wrote:
> >
> > +1
> >
> > Do we have a list of features for 2.4 documented anywhere?
> >
> > D.
> >
> > On Fri, Jan 12, 2018 at 7:43 AM, Pavel Tupitsyn <
> >> ptupit...@apache.org>
> > wrote:
> >
> >> +1
> >>
> >> But some stuff is not yet in master (like baseline topology), so it
> >> is
>  too
> >> soon to create a branch, I think.
> >>
> >> Pavel
> >>
> >> On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov <
> >>> voze...@gridgain.com>
> >> wrote:
> >>
> >>> Igniters,
> >>>
> >>> A number of major improvements have been made (or being finalized
> >> at
>  the
> >>> moment) to Ignite since recent 2.3 release. This includes baseline
> >>> topology, new DDL commands, migration to Java 8 and Java 9 support,
> >>> critical performance improvements to WAL, etc..
> >>>
> >>> I think it makes sense to make a new release. What do you think if
> >> we
> >>> release AI 2.4 with all this great stuff by the end of Jan?
> >>>
> >>> If there are no objections, I'll create a branch to start
> >>> stabilization
> >>> process.
> >>>
> >>> Vladimir.
> >>>
> >>
> 
> 
> >>>
> >>
>
>

[GitHub] ignite pull request #3419: IGNITE-6917: SQL: implement COPY command for effi...

[gg-shq]

GitHub user gg-shq opened a pull request:

https://github.com/apache/ignite/pull/3419

IGNITE-6917: SQL: implement COPY command for efficient data loading



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6917-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3419.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3419


commit deb7994f0fd4233e3e0b699794b9066af87195c7
Author: gg-shq 
Date:   2018-01-19T12:13:37Z

IGNITE-6917: Intermediate commit

commit e7747a58c2cdacc6987d625a46d1f79a81863cd3
Author: gg-shq 
Date:   2018-01-19T17:21:50Z

IGNITE-6917: Intermediate commit

commit 6f37e6751285a96bdf757b392e1d4113bb47ee48
Author: gg-shq 
Date:   2018-01-19T17:30:22Z

IGNITE-6917: Intermediate commit

commit 49f0324c77d0bb3b4ec87317b1ecbde1bd6f34b1
Author: gg-shq 
Date:   2018-01-22T10:27:34Z

IGNITE-6917: Intermediate commit

commit a5bec61d41d8dc242cfbf11a7cf03c23bbbcd7c3
Author: gg-shq 
Date:   2018-01-22T12:25:04Z

IGNITE-6917: Intermediate commit

commit e18e18696fc92b93b17decf087721c693625ac36
Author: gg-shq 
Date:   2018-01-22T12:35:56Z

IGNITE-6917: Intermediate commit

commit 990c04919e181535e57290ee2516a9603657c160
Author: gg-shq 
Date:   2018-01-22T16:18:18Z

IGNITE-6917: Intermediate commit




---

Re: Apache Ignite 2.4 release

[Denis Magda]

Igniters,

What’s left and what prevents us from passing 2.4 through the QA phase?

Petr, Anton, Vladimir, Alex G., others please chime in.

—
Denis

> On Jan 17, 2018, at 7:05 PM, Dmitriy Setrakyan  wrote:
> 
> Great news, indeed! Looking forward to 2.4 release.
> 
> On Wed, Jan 17, 2018 at 2:55 AM, Vladimir Ozerov 
> wrote:
> 
>> Igniters,
>> 
>> Great news - two very important tickets - baseline topology and Java 8
>> support - were merged to master. At this point it makes sense to create a
>> branch to stabilize the release and finalize outstanding tickets. I created
>> the branch *ignite-2.4*. Please follow the rules below when merging new
>> commits to master:
>> 1) If ticket is targeted for 2.4 release, please merge to master, then
>> cherry-pick to ignite-2.4
>> 2) Otherwise just merge to master.
>> 
>> Vladimir.
>> 
>> On Tue, Jan 16, 2018 at 12:32 PM, Anton Vinogradov <
>> avinogra...@gridgain.com
>>> wrote:
>> 
>>> Denis,
>>> 
>>> I'll review https://issues.apache.org/jira/browse/IGNITE-6902
>>> 
>>> On Fri, Jan 12, 2018 at 11:45 PM, Denis Magda  wrote:
>>> 
 Here is the page create before:
 https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 <
 https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4>
 
 This is good news. It will be perfect if we also release as many
>>> "required
 tickets" as we can:
 https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 <
 https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4>
 
 My favorite is memory metrics in bytes: https://issues.apache.org/
 jira/browse/IGNITE-6902 >> jira/browse/IGNITE-6902
> 
 
 The discussion lists are flooded with the demands for this essential
 capability. Who is going to review it?
 
 -
 Denis
 
> On Jan 12, 2018, at 11:22 AM, Dmitriy Setrakyan <
>> dsetrak...@apache.org
 
 wrote:
> 
> +1
> 
> Do we have a list of features for 2.4 documented anywhere?
> 
> D.
> 
> On Fri, Jan 12, 2018 at 7:43 AM, Pavel Tupitsyn <
>> ptupit...@apache.org>
> wrote:
> 
>> +1
>> 
>> But some stuff is not yet in master (like baseline topology), so it
>> is
 too
>> soon to create a branch, I think.
>> 
>> Pavel
>> 
>> On Fri, Jan 12, 2018 at 5:31 PM, Vladimir Ozerov <
>>> voze...@gridgain.com>
>> wrote:
>> 
>>> Igniters,
>>> 
>>> A number of major improvements have been made (or being finalized
>> at
 the
>>> moment) to Ignite since recent 2.3 release. This includes baseline
>>> topology, new DDL commands, migration to Java 8 and Java 9 support,
>>> critical performance improvements to WAL, etc..
>>> 
>>> I think it makes sense to make a new release. What do you think if
>> we
>>> release AI 2.4 with all this great stuff by the end of Jan?
>>> 
>>> If there are no objections, I'll create a branch to start
>>> stabilization
>>> process.
>>> 
>>> Vladimir.
>>> 
>> 
 
 
>>> 
>> 

[GitHub] ignite pull request #3418: Ignite 6899 check

[oignatenko]

GitHub user oignatenko opened a pull request:

https://github.com/apache/ignite/pull/3418

Ignite 6899 check



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-6899-check

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3418.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3418


commit 5c204d7b433f043fdce25be0330d7793767ea99f
Author: Turik Campbell 
Date:   2018-01-09T22:06:18Z

IGNITE-6899: Adding GA Grid to Apache Ignite ML module

commit e30356df9e41b9d8379b8880b66b60d97458f3e9
Author: Turik Campbell 
Date:   2018-01-12T04:34:33Z

IGNITE-6899: Applied Ignite code style

commit fd59c65bc24733f56c5e95b5334b772a44c9b57e
Author: Turik Campbell 
Date:   2018-01-12T04:38:02Z

Merge branch 'master' into ignite-6899

commit aa8601f05100358de337736931b5b34566bf34af
Author: Turik Campbell 
Date:   2018-01-13T15:24:55Z

IGNITE-6899: Added package-info.java files to sub packages of genetic (ie: 
src/main/java/org/apache/ignite/ml/genetic)

commit d804213debc1a027037185b07f3e5d66018b4c30
Author: Turik Campbell 
Date:   2018-01-13T15:46:13Z

IGNITE-6899: Updated visibility of chromosomeCriteria and updated typo for 
respective accessor/mutator method.

commit 7f107a8e05a5f77ee1725dda981433b8c8e56436
Author: Turik Campbell 
Date:   2018-01-13T15:47:40Z

IGNITE-6899: Merge branch 'master' into ignite-6899

commit cc1943af8902cf4dc99dda631b39d6ebb5941d3d
Author: Turik Campbell 
Date:   2018-01-15T02:57:36Z

IGNITE-6899: Fixed Java coding conventions for comments

commit 644f935ba984d47a7943025b261354790179fe52
Author: Turik Campbell 
Date:   2018-01-16T03:12:41Z

Merge branch 'master' into ignite-6899

commit 7be0e3712d8db1c7042809bb33bdb39aecd1c909
Author: Turik Campbell 
Date:   2018-01-17T12:51:18Z

IGNITE-6899: Merged 'master' branch into 'ignite-6899' branch and resolved 
conflicts

commit 60a5aa6f9c8d68c19d45c70aab75a90f657eae13
Author: Turik Campbell 
Date:   2018-01-18T12:36:59Z

IGNITE-6899: Merge branch 'master' into ignite-6899

commit a7a3d8071344c3c3adbc8b83d33dbb7bac5309ca
Author: Turik Campbell 
Date:   2018-01-20T13:06:36Z

IGNITE-6899: Deleted unwanted directory /maven_repository

commit 191109734409e4391263d449ecba66ba8d49ca32
Author: Turik Campbell 
Date:   2018-01-20T13:27:36Z

IGNITE-6899: Moved ML 'GAGrid' examples to examples/src/main/java directory.
 Updated OptimizeMakeChangeGAExample to use 'elitism' selection 
method (ie: set eliteCount).

commit 59b55a79bb085849053bf6b736056d5485df47f7
Author: Turik Campbell 
Date:   2018-01-20T13:38:03Z

IGNITE-6899: Merge branch 'master' into ignite-6899

commit b568a03ca6c7e036aba1dce6bef70acb8faa8d36
Author: Turik Campbell 
Date:   2018-01-20T16:09:44Z

IGNITE-6899: Removed FITNESS_EVALUATER_TYPE (enum) in favor using boolean 
value to describe fitness evaluation

commit 8706ef36bcda8a074b80483efd1729b468329a0b
Author: Turik Campbell 
Date:   2018-01-20T16:11:36Z

IGNITE-6899: Fixed comments

commit 6287a890404d5262abff8fd50c11f10f4cf373e4
Author: Oleg Ignatenko 
Date:   2018-01-22T15:09:35Z

IGNITE-6899 GA Grid - preliminary check for licenses and javadocs
- fixed javadoc issues that were picked by merge from master
-- verified with diffs overview




---

[jira] [Created] (IGNITE-7489) Weird FillFactor metric fluctuation.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-7489:


 Summary: Weird FillFactor metric fluctuation.
 Key: IGNITE-7489
 URL: https://issues.apache.org/jira/browse/IGNITE-7489
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Mashenkov
 Attachments: FillFactorTest.java

PFA a repro.

There is 2 node grid with no persistence configure. Topology is stable.

Cache is populated with unique keys (no updates) and observe allocated data 
pages metric grows constantly as expected.

Used memory is calculated as PhysicalMemoryPages*PageSize*FillFactor and 
expected it will be constantly grows (or may be with a small error).

But the error look too large, used memory (and FillFactor as well) may 2-10+ 
time differs.

 

E.g. allocated pages, fillFactor, usedMem (bytes):
node-0: 13789 0.851563 48096032
node-1: 14447 0.781250 46230400

In next second:

node-0: 13958 0.039063 2233280
node-1: 14624 0.347656 20824576

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3417: IGNITE-2766 Opportunistically reopen cache after ...

[alamar]

GitHub user alamar opened a pull request:

https://github.com/apache/ignite/pull/3417

IGNITE-2766 Opportunistically reopen cache after client reconnect.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2766

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3417.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3417


commit a70620ca6398ba151541b5ff92c7f941eea07527
Author: Ilya Kasnacheev 
Date:   2018-01-22T15:29:36Z

IGNITE-2766 Opportunistically reopen cache after client reconnect.




---

[GitHub] ignite pull request #2600: IGNITE-6193 ML profile is missing in 2.1 binary r...

[oignatenko]

Github user oignatenko closed the pull request at:

https://github.com/apache/ignite/pull/2600


---

[GitHub] ignite pull request #3415: IGNITE-7477 Ignite.NET does not work on Java 9

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3415


---

[jira] [Created] (IGNITE-7488) fix javadoc and license check failures introduced per IGNITE-7284

[Oleg Ignatenko (JIRA)]

Oleg Ignatenko created IGNITE-7488:
--

 Summary: fix javadoc and license check failures introduced per 
IGNITE-7284
 Key: IGNITE-7488
 URL: https://issues.apache.org/jira/browse/IGNITE-7488
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Oleg Ignatenko


fix javadoc and license check failures introduced per IGNITE-7284. One example 
is:
{noformat}
[15:22:32][Step 7/7] [WARNING] Javadoc Warnings
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:97:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:117:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:137:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:168:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:199:
 warning - @implSpec is an unknown tag. {noformat}

and there may be others. Link for Teamcity task to verify that there are no 
violations: 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7487) .NET: Thin client: Documentation

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7487:
--

 Summary: .NET: Thin client: Documentation
 Key: IGNITE-7487
 URL: https://issues.apache.org/jira/browse/IGNITE-7487
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Document .NET Thin Client usage on readme.io



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Hello

[Roman Guseinov]

Hello Ignite Community!

My name is Roman. I want to contribute to Apache Ignite. Any help on this
will be appreciated.

Thanks!

Best Regards, Roman
Email: ro...@gromtech.ru
Username at Jira: guseinov

[jira] [Created] (IGNITE-7486) Сache operation failed after transaction rolled back due to deadlock

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7486:


 Summary: Сache operation failed after transaction rolled back due 
to deadlock
 Key: IGNITE-7486
 URL: https://issues.apache.org/jira/browse/IGNITE-7486
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Kuznetsov
 Attachments: CacheOperationAfterTxDeadlockDetectedTest.java

When you have your transaction rolled back due to detected deadlock, you are 
unabled to perform cache operations (in thread where tx was started and rolled 
back), because it leads to TransactionTimeoutException.

The reason of such behavior is that tx thread map (txManager#threadMap) was not 
cleared from tx when roll back occured.

In GridNearTxLocal#onTimeout you can find comment on that :

// Note: if rollback asynchronously on timeout should not clear thread map
// since thread started tx still should be able to see this 
tx.

Cache operation picks up tx from that map and throws exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3416: IGNITE-7485 add support for authentication parame...

[macrergate]

GitHub user macrergate opened a pull request:

https://github.com/apache/ignite/pull/3416

IGNITE-7485 add support for authentication parameters



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite IGNITE-7485

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3416.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3416


commit ee446b4079df3ab07db299041607431a6fc99dab
Author: macrergate 
Date:   2018-01-22T10:10:58Z

IGNITE-7485 add support for authentication parameters




---

Re: cache operation failed after transaction rolled back due to deadlock

[ALEKSEY KUZNETSOV]

Sure

пн, 22 янв. 2018 г. в 12:25, Andrey Gura :

> It seems that problem isn't related with deadlock detection and should be
> reproducible when deadlock detection disabled.
>
> Anyway it sounds like a bug. Could you please file a ticket and provide
> minimal reproducer?
>
> 19 янв. 2018 г. 3:55 PM пользователь "ALEKSEY KUZNETSOV" <
> alkuznetsov...@gmail.com> написал:
>
> > Hi, Igntrs!
> >
> >
> >
> > When you have your transaction rolled back due to detected deadlock, you
> > are unabled to perform cache operations (in thread where tx was started
> and
> > rolled back), because it leads to TransactionTimeoutException.
> >
> >
> >
> > The reason of such behavior is that tx thread map (txManager#threadMap)
> was
> > not cleared from tx when roll back occured.
> >
> > In GridNearTxLocal#onTimeout you can find comment on that :
> >
> > *// Note: if rollback asynchronously on timeout should not clear thread
> > map*
> >
> > *// since thread started tx still should be able to see this tx.*
> >
> > Cache operation picks up tx from that map and throws exception.
> >
> >
> >
> > So, one must create new thread in order to perform cache operations?
> >
> >
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>


-- 

*Best Regards,*

*Kuznetsov Aleksey*

[GitHub] ignite pull request #3415: IGNITE-7477 Ignite.NET does not work on Java 9

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/3415

IGNITE-7477 Ignite.NET does not work on Java 9



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-7477

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3415.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3415


commit c69ce7b5e0339cec245df1ba2246238645d3efcd
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:05:12Z

IGNITE-7477 .NET: Add JVM options to start on Java 9

commit 33ab0cb6cb6daff6fc6e155efc3119e07c8f413d
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:09:34Z

wip

commit a7612ab44e89d3a931eb3fc8a33a53b680d1c3fc
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:20:41Z

Fix Java9Options

commit 98cc21b0c6f852d96c01c49cf3df72a68fa2fd46
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:25:34Z

Fix assert

commit 851567bf6e01bbb5f0677bf54e74278f65d70c84
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:30:31Z

Refactor JVM options cleanup

commit 5c970fea1e34aeed693fd0f4c13f02108b9ea48a
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:50:42Z

wip

commit e1556018c6f2dd0a716cccb523ecb7725432df1a
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:32:58Z

wip java version detect

commit 510601740fb914a3b76bca8a722f5d10cc1d4795
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:37:51Z

wip

commit d090fcae8a07f1ebb0f413a961bcfdcd58629407
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:38:40Z

wip

commit 658accfa5ac4b1a83ea8cecd9bd0376bc28dd9ff
Author: Pavel Tupitsyn 
Date:   2018-01-22T08:53:20Z

wip

commit cb19997cba88f2928a594e1d8dc5f06f43433768
Author: Pavel Tupitsyn 
Date:   2018-01-22T08:55:35Z

wip

commit 4deac669014e93e3cf7d4421245d9a67234d99d1
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:18:22Z

wip IsJava9

commit 45ed0e7220212974088993930d4dd8d36e349d4b
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:22:36Z

Java 9 detection done

commit fe0907b45a4f47f43346fd2a5601a1f238f316ae
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:24:17Z

Fixed

commit 4a0c15a10a17ff9edcab14c9f79e177cecbae045
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:37:07Z

wip

commit e683cff718040ba03bf19e14aed041301e20a7b6
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:40:30Z

JNI_GetDefaultJavaVMInitArgs on Linux / macOS




---

[jira] [Created] (IGNITE-7485) control.sh utility does not support authentication

[Sergey Kosarev (JIRA)]

Sergey Kosarev created IGNITE-7485:
--

 Summary: control.sh utility does not support authentication
 Key: IGNITE-7485
 URL: https://issues.apache.org/jira/browse/IGNITE-7485
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Sergey Kosarev
Assignee: Sergey Kosarev


Currently controls.sh utility does not work if cluster is running under 
authentication.

Error is shown:

Failed to get cluster state.
Authentication error.

 

it is suggested to introduce authentication parameters to the utitlity

--login LOGIN

--password PASSWORD

 

Main Utility class ( CommandHandler )  is located in ignite-core module 
currently. 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3414: Ignite 2.4

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/3414

Ignite 2.4



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/ignite ignite-2.4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3414.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3414


commit cbd69d6b3b0948c686786ec322ff90bacd48
Author: Denis Magda 
Date:   2017-12-05T20:44:10Z

Merge remote-tracking branch 'origin/master'

commit 1367bc98eb08233f9e47ba45335f9dda1fbb7bbd
Author: Dmitriy Shabalin 
Date:   2017-12-06T03:36:42Z

IGNITE-6390 Web Console: Added component for cluster selection.

commit f905442e72ef4ad202410b5492caba23874d9804
Author: Alexander Paschenko 
Date:   2017-12-06T13:18:17Z

IGNITE-7120: SQL: fixed falky failures in AbstractSchemaSelfTest. This 
closes #3156.

commit 92042475186515fc5041aaa5bb10d669f31d0e62
Author: Alexey Popov 
Date:   2017-12-06T13:21:20Z

IGNITE-6971 Ignite Logger type & logging file config indication. This 
closes #3095.

Signed-off-by: nikolay_tikhonov 

commit ac6b872d4144a1133f9ca186f2df876a2e933cc4
Author: Alexey Goncharuk 
Date:   2017-12-06T13:58:41Z

Fixed javadoc warning

commit d75101083a19b23aaac163cc15f29abf597dad29
Author: Alexey Kuznetsov 
Date:   2017-12-06T14:33:34Z

IGNITE-7106 Optimized cache metrics collection.

commit 81324739979d1a3e0dd167d66fe5bdc9ddc0548c
Author: vsisko 
Date:   2017-12-06T15:23:02Z

IGNITE-6987 Showed actual client connector configuration "Thread pool size" 
property.

commit 280acbf831a0611c15d2b8d7b103bcb8d08c40d7
Author: nikolay_tikhonov 
Date:   2017-12-06T16:30:56Z

IGNITE-7080 Check env variable names to only pass IGNITE_* to nodes. This 
closes #3161.

Signed-off-by: nikolay_tikhonov 

commit 4717570cfc6263ca3beb2ef6df53f5edef365fdc
Author: Pavel Tupitsyn 
Date:   2017-12-06T16:44:12Z

IGNITE-7123 .NET: Verify metrics API parity with tests

commit 936dc9570d6f7f752ff2f6265d8093f8ee75934f
Author: vsisko 
Date:   2017-12-06T16:49:35Z

IGNITE-6897 Visor: Show valid message for caches when cluster is inactive.

commit 9813c626b3ac49e99d8b404aec44992e48dd1fed
Author: Pavel Tupitsyn 
Date:   2017-12-06T17:14:55Z

IGNITE-7124 .NET: Thin client: Cache benchmark

commit cab5cc56245ae5035de18d373227ce8aa22955f9
Author: Ilya Borisov 
Date:   2017-12-07T07:59:12Z

IGNITE-7133 Web Console: Implemented service for managing icons.

commit bbeb2050877d064cf937c12a4f1536079da40b17
Author: Evgenii Zhuravlev 
Date:   2017-12-07T12:42:33Z

IGNITE-7088 Fix implementation of DIRECT comparator for ordering cache 
start operations. This closes #3136.

Signed-off-by: nikolay_tikhonov 

commit c5c512e460140c91fb77b527ff909ddbe3d1fd72
Author: Oleg Ignatenko 
Date:   2017-12-07T15:14:51Z

IGNITE-6872: Linear regression should implement Model API

This closes #3168

commit e39283e88d5948ebfe1d8a166e3ed74a9304b7b2
Author: Andrey V. Mashenkov 
Date:   2017-12-07T16:16:25Z

IGNITE-7008 TcpDiscoverySharedFsIpFinder fails with NPE if address can't be 
resolved. This closes #3087.

Signed-off-by: nikolay_tikhonov 

commit 1f63b8115127c0ea38430c85bf9fc7a1d85ca210
Author: YuriBabak 
Date:   2017-12-07T16:33:27Z

IGNITE-7110: Javadoc package descriptions missed for ML

this closes #3174

commit a7893b6307bc752d7b7f1432967a964f30716858
Author: Oleg Ignatenko 
Date:   2017-12-07T17:34:14Z

IGNITE-6373: Create example for local and distributed k-means algorithm

this closes #3173

commit c7698383331b9680d28fbd8eca1d8584d41c062e
Author: dkarachentsev 
Date:   2017-12-08T10:36:28Z

IGNITE-7086 - Backups are not updated when ReadFromBackup=true and 
ReadThrough happens.

commit 3c20b0e4e32443977cbc18b61ef03d94b1cd5407
Author: Alexander Fedotov 
Date:   2017-12-08T12:32:27Z

IGNITE-7085 When PDS is enabled and IGNITE_BINARY_SORT_OBJECT_FIELDS is set 
and IgniteCache#put is called node hangs - Fixes #3121.

Signed-off-by: Alexey Goncharuk 

commit 93e133c5bc4e69f2b7571e33c3d4dc4ecc3f68db
Author: Alexey Popov 
Date:   2017-12-08T15:42:08Z

IGNITE-7052 S3 IP finder: add an ability to provide endpoint address. This 
closes #3179.

Signed-off-by: nikolay_tikhonov 

commit 1e8b5501ee9fde61f979c104b4d271a1a458eb1d
Author: vsisko 
Date:   2017-12-10T13:13:05Z

IGNITE-6999 Visor CMD: Added support for "-quiet" option in batch mode.

commit 592fb3320bdf417b3d351f8a404073a78ea75c71
Author: vsisko 
Date:   2017-12-11T04:55:06Z

WC-253 Web Console: Show user-friendly error message.

commit 0dd16a7ebdec3d88841250bc19d24cc1430ad3f3
Author: Alexey Kuznetsov 
Date:   2017-12-11T08:03:33Z

IGNITE-4835 Visor CMD: Added ability to start cache rebalance.

commit 80801cb2fe471967435155e55

Re: cache operation failed after transaction rolled back due to deadlock

[Andrey Gura]

It seems that problem isn't related with deadlock detection and should be
reproducible when deadlock detection disabled.

Anyway it sounds like a bug. Could you please file a ticket and provide
minimal reproducer?

19 янв. 2018 г. 3:55 PM пользователь "ALEKSEY KUZNETSOV" <
alkuznetsov...@gmail.com> написал:

> Hi, Igntrs!
>
>
>
> When you have your transaction rolled back due to detected deadlock, you
> are unabled to perform cache operations (in thread where tx was started and
> rolled back), because it leads to TransactionTimeoutException.
>
>
>
> The reason of such behavior is that tx thread map (txManager#threadMap) was
> not cleared from tx when roll back occured.
>
> In GridNearTxLocal#onTimeout you can find comment on that :
>
> *// Note: if rollback asynchronously on timeout should not clear thread
> map*
>
> *// since thread started tx still should be able to see this tx.*
>
> Cache operation picks up tx from that map and throws exception.
>
>
>
> So, one must create new thread in order to perform cache operations?
>
>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[jira] [Created] (IGNITE-7484) Documentation for new lin reg trainer.

[Yury Babak (JIRA)]

Yury Babak created IGNITE-7484:
--

 Summary: Documentation for new lin reg trainer.
 Key: IGNITE-7484
 URL: https://issues.apache.org/jira/browse/IGNITE-7484
 Project: Ignite
  Issue Type: Task
  Components: ml
Reporter: Yury Babak






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Documentation for Binary Client Protocol

[Pavel Tupitsyn]

Thanks Denis, makes sense.

On Fri, Jan 19, 2018 at 10:55 PM, Denis Magda  wrote:

> Added the proposed callout to the top of the page:
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 9+Thin+Client+Protocol
>
> > On Jan 19, 2018, at 9:36 AM, Denis Magda  wrote:
> >
> > Pavel,
> >
> > Do you plan to maintain this page? Frankly, since it’s an IEP and Prachi
> already prepared an official documentation I would suggest us to but a
> teaser on the top of the page saying that the most up-to-date and detailed
> information about the protocol is on readme.io . Agree?
> >
> > —
> > Denis
> >
> >> On Jan 18, 2018, at 11:37 PM, Pavel Tupitsyn 
> wrote:
> >>
> >> Hi everyone,
> >>
> >> Just a reminder that initial spec is on wiki:
> >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 9+Thin+Client+Protocol
> >>
> >> It is quite terse and may be harder to understand.
> >> Prachi tried to document all of this in a more user-friendly manner with
> >> examples and so on.
> >>
> >> On Fri, Jan 19, 2018 at 6:30 AM, Denis Magda  wrote:
> >>
> >>> Lucas, thanks for chiming in,
> >>>
> >>> The protocol itself consists of all these magic constants (type and
> >>> operations codes). See type codes table from this section:
> >>> https://apacheignite.readme.io/docs/binary-client-
> >>> protocol#section-data-objects  >>> io/docs/binary-client-protocol>
> >>>
> >>> Hope that my explanation given to Alexey makes sense to both of you.
> >>>
> >>> Initially, we didn’t plan to have the code snippets at all and wanted
> to
> >>> document the protocol in a way similar to Mongo’s protocol:
> >>> https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/ <
> >>> https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/>
> >>>
> >>> But after several iterations we agreed to simplify a life of those who
> >>> will be developing thin clients on top of the protocol and filled out
> the
> >>> doc with as many code snippets as possible. Again, the snippets are
> not a
> >>> complete application and this is why we ignored some of the best
> practices
> >>> used by Java developers.
> >>>
> >>> —
> >>> Denis
> >>>
>  On Jan 18, 2018, at 7:11 PM, Lucas Beeler 
> >>> wrote:
> 
>  Hi Igniters,
> 
>  I’m with Alexey here: hard-coded “magic” literals make code hard to
> read
> >>> and neither communicate coding professionalism nor comport with
> published
> >>> Sun/Oracle style guides. So I suggest that:
>  For already defined symbolic constants, let’s use them instead of
> >>> literal values
>  If there are literal values for which symbolic constants haven’t yet
> >>> been defined, let’s define symbolic constants for them, commit this
> change
> >>> to master, and start using the newly defined symbolic constants
>  Anyhoo, that’s just my two cents.
> 
>  As always, it’s a pleasure to be a part of Ignite development...
> 
>  Cheers guys & gals,
>  Lucas
> 
>  --
>  Lucas BEELER
>  Technical Consultant, Professional Services
>  GridGain Systems
>  www.gridgain.com 
> 
> > On Jan 18, 2018, at 6:47 PM, Alexey Kuznetsov  >>> > wrote:
> >
> > Prachi, Denis,
> >
> >
> > It is OK that we are using numbers in code samples instead of named
> > constants?
> >
> > For example:
> > writeByteLittleEndian(3, out);  // Integer type code
> >
> > It could be smth. like this:
> > writeByteLittleEndian(TYPE_INT, out);  // Integer type code
> >
> > Where TYPE_INT is declared at some place:
> > 
> > public static final int TYPE_INT = 3;
> > 
> >
> > Make sense?
> >
> >
> > On Fri, Jan 19, 2018 at 4:47 AM, Prachi Garg  >>> > wrote:
> >
> >> Igniters,
> >>
> >> The document for Binary Client Protocol (awaiting 2.4 release) is
> >>> ready on
> >> Apache Ignite readme.io . This document
> explains:
> >>
> >> - How to connect to Ignite cluster
> >> - Common message format (Request/Response header)
> >> - Supported Data types and their format
> >> - Request/Response format for each message type
> >>
> >> Here are the links -
> >>
> >> https://apacheignite.readme.io/docs/binary-client-protocol <
> >>> https://apacheignite.readme.io/docs/binary-client-protocol>
> >>
> >> https://apacheignite.readme.io/docs/binary-client-protocol-
> >> key-value-operations
> >>
> >> https://apacheignite.readme.io/docs/binary-client-
> >>> protocol-sql-operations
> >>
> >> https://apacheignite.readme.io/docs/binary-client-protocol-
> >> binary-type-operations
> >>
> >> https://apacheignite.readme.io/docs/binary-client-protocol-
> >> cache-configuration-operations
> >>
> >>
> >> Currently these pages are hidden and are accessible onl

Re: .Net standard target for Ignite.Net client

[Pavel Tupitsyn]

Hi Raymond,

Upcoming Ignite 2.4 has a lot of changes to run Ignite.NET under .NET Core
on Linux and macOS (as well as Windows).
However, we are not targeting .NET Standard, since it misses some crucial
things like DynamicMethod.

Please make sure that you don't confuse .NET Standard and .NET Core: only
class libraries can target .NET Standard.
Actual applications target .NET Core.

In my understanding, nothing should prevent you from doing dockerized
deployments on any OS with Ignite.NET 2.4.
You can try nightly build and see if it works for your environment:
https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds

Thanks,
Pavel

On Sun, Jan 21, 2018 at 11:55 PM, Raymond Wilson  wrote:

> All,
>
>
>
> Are there any plans for porting the current Ignite.Net client to .Net
> Standard? Has anyone investigated how much effort there would be involved?
>
>
>
> We would like to use dockerised deployments and as we use a .Net
> development stack .Net Standard is our target platform for those
> deployments.
>
>
>
> Thanks,
>
> Raymond.
>
>
>

[jira] [Created] (IGNITE-7483) Queries: transformers are not executed when paging the result

[Sascha Hofer (JIRA)]

Sascha Hofer created IGNITE-7483:


 Summary: Queries: transformers are not executed when paging the 
result
 Key: IGNITE-7483
 URL: https://issues.apache.org/jira/browse/IGNITE-7483
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.3
Reporter: Sascha Hofer


It seems that transformers are not executed during pagination which leads to 
{{ClassCastExceptions}} because the result list also contains instances of 
{{GridCacheQueryResponseEntry}}.

To reproduce open {{GridCacheQueryTransformerSelfTest.testGetKeys()}} and set a 
page size of 1 so that

{code:java}
List keys = cache.query(new ScanQuery(), 
transformer).getAll();
{code}

becomes to

{code:java}
List keys = cache.query(new ScanQuery().setPageSize(1), transformer).getAll();
{code}

this leads to following stack trace:
{noformat}
java.lang.ClassCastException: 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryResponseEntry 
cannot be cast to java.lang.Comparable

at java.util.ComparableTimSort.binarySort(ComparableTimSort.java:249)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:207)
at java.util.Arrays.sort(Arrays.java:1312)
at java.util.Arrays.sort(Arrays.java:1506)
at java.util.ArrayList.sort(ArrayList.java:1454)
at java.util.Collections.sort(Collections.java:141)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryTransformerSelfTest.testGetKeys(GridCacheQueryTransformerSelfTest.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)