Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Peter Ivanov]

Pavel,


Can you give a cue where can be uploaded Nuget packages found?

On Mon, 16 Jul 2018 at 23:37, Pavel Tupitsyn  wrote:

> Petr,
>
> This is the same build that I have linked. Is there anything I should pay
> attention to?
>
> On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov  wrote:
>
> > Pavel,
> >
> >
> > Before uploading, please check this [1] build.
> >
> >
> > [1]
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> > <
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> > >
> >
> >
> >
> >
> > > On 16 Jul 2018, at 22:56, Pavel Tupitsyn  wrote:
> > >
> > > I will upload NuGet packages. Is this the right TC build?
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv
> > >
> > > On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura  wrote:
> > >
> > >> Ignite site is updated. Most artifacts are published.
> > >>
> > >> Waiting for publishing of Docker images and 2.6 related docs. Also it
> > >> would be great to check NuGet packages.
> > >> On Mon, Jul 16, 2018 at 7:32 PM Denis Magda 
> wrote:
> > >>>
> > >>> Andrey,
> > >>>
> > >>> I'll publish the docs later today.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>> On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura 
> wrote:
> > >>>
> >  Dmitry,
> > 
> >  I'm updating the site at this moment. Could somebody publish 2.6
> >  documentation on readme.io site?
> >  On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>
> >  wrote:
> > >
> > > Is there a reason why 2.6 has not been uploaded to the website yet?
> > >
> > > D.
> > >
> > > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura 
> > >> wrote:
> > >
> > >> Igniters,
> > >>
> > >> Apache Ignite 2.6.0 release (RC1) has been accepted.
> > >>
> > >> 5 "+1" binding votes received:
> > >>
> > >> - Alexey Goncharuk
> > >> - Alexey Kuznetsov
> > >> - Andrey Gura
> > >> - Anton Vinogradov
> > >> - Denis Magda
> > >>
> > >> Vote thread:
> > >>
> > >> *http://apache-ignite-developers.2346864.n4.nabble.
> > >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > >>  > >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > >>
> > >> Ignite 2.6.0 will be released soon.
> > >>
> > 
> > >>
> >
> >
>

[GitHub] ignite pull request #4370: Ignite 2.4.7.b5

[slukyano]

GitHub user slukyano opened a pull request:

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

Ignite 2.4.7.b5



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

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

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

https://github.com/apache/ignite/pull/4370.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 #4370


commit 9c6a52250e058c4546aef0d0ecee977c07076a1a
Author: Alexey Kuznetsov 
Date:   2018-02-02T10:09:37Z

IGNITE-7612 Web Console: Refactored mongoose schemas to separate module.

(cherry picked from commit 71db707)

commit 89e15830dedcb46f24d9cc9b922ba3b013331a18
Author: Vasiliy Sisko 
Date:   2018-02-12T10:22:10Z

Web Agent: Fixed wrong config of IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE in 
demo startup.

(cherry picked from commit 1a6e544)

commit 18966673570425192e1b89fbb2c63d164b47eaca
Author: Vasiliy Sisko 
Date:   2018-02-12T13:24:30Z

IGNITE-7578 Actualized client connector configuration.

(cherry picked from commit 819d746)

commit 237063efa35c54bb9e9800ecf63ea223ec20a9ef
Author: alexdel 
Date:   2018-02-19T04:25:24Z

IGNITE-7650 Extracted signin/signup form to separate page, improved landing 
page.

(cherry picked from commit 1925674)

commit 679aeca7a3ff60a9dd478966d3949107d302d5db
Author: Andrey Novikov 
Date:   2018-02-19T07:56:07Z

IGNITE-7650 Fixed headers.

(cherry picked from commit 67922b3)

commit 5d5a6a05ec49f895e8a5edd505e496dcfe58a208
Author: Vasiliy Sisko 
Date:   2018-02-21T04:21:02Z

IGNITE-6094 Web Agent: Enabled persistent in demo mode.

(cherry picked from commit 3c35900)

commit e35d8cfb06f52765959fc2e1883bf70fe0259f45
Author: Alexander Kalinin 
Date:   2018-02-21T07:03:20Z

IGNITE-7320 Web Console - Fixed table headers for Safari.

(cherry picked from commit 04a025b)

commit 20cb1439f48b9a3c985f65784af36ef2c6f45e4f
Author: Andrey Novikov 
Date:   2018-02-22T02:54:05Z

IGNITE-7650 Fixed counties codes.

(cherry picked from commit fc40261)

commit 50d1389cd60e148005701e3450c8ae9998fd5fc9
Author: Alexey Kuznetsov 
Date:   2018-02-22T03:28:32Z

IGNITE-6287 Web Console: Fixed regression for EXPLAIN.

(cherry picked from commit 2bee8f8)

commit 330e502d5effea485254151ebf9b666e67d68475
Author: Alexander Kalinin 
Date:   2018-02-26T08:13:52Z

IGNITE-7729. Web Console. Added roles support in E2E tests.

(cherry picked from commit a83b264)

commit 3579db951abec81b7201ad91326ddc73ee828387
Author: Vasiliy Sisko 
Date:   2018-01-26T03:22:50Z

IGNITE-7392 Visor Cmd: Added missing word 'factory'.

(cherry picked from commit c0b14e5)

commit c125fa2068b62ab5286888ab2a16b5b034964dfd
Author: Vasiliy Sisko 
Date:   2018-02-12T03:13:06Z

IGNITE-2093 Visor CMD: Added support to scan near cache.

(cherry picked from commit a5a907b)

commit 2f074c05492439e1860a6920fff2861a071b58a8
Author: Alexey Kuznetsov 
Date:   2018-02-28T11:53:26Z

IGNITE-7578 Backport for ignite-2.4.3.

commit 8b1e77bac2d4fe125463f8978ca905d34a45b82f
Author: Alexey Kuznetsov 
Date:   2018-02-28T11:57:53Z

ignite-2.4.3 Fixed versions list.

commit bad7053586cccbbae4eb3d6dcba0d1ada5d2d2f2
Author: Alexey Kuznetsov 
Date:   2018-03-01T09:18:17Z

IGNITE-6920 Fixed missed require.

(cherry picked from commit fe89fc4)

commit 0294cf293ea35a355f18b218b842ec60e2583f42
Author: devozerov 
Date:   2018-03-01T12:11:39Z

Merge branch 'ignite-2.4' into ignite-2.4.3

commit e899d0a0fa8fb1692ddc7f74ee43dc9ca50f885d
Author: Pavel Kovalenko 
Date:   2018-03-01T12:41:52Z

IGNITE-7717 Fixed missed updateTopologyVersion call in case of a merged 
exchange - Fixes #3536.

Signed-off-by: Alexey Goncharuk 

commit 1948dc73f36ddfda6bc55b9c1ea7421fb8c62ff1
Author: Sergey Kosarev 
Date:   2018-02-12T03:51:57Z

IGNITE-7485 Added support for authentication parameters in control.sh.

(cherry picked from commit f53c48a)

commit 20611b28b89adde162ad380cb3a6d9bd4608eb8b
Author: Vasiliy Sisko 
Date:   2018-03-01T16:13:53Z

IGNITE-7462 Web Console: Actualized configuration generation.

(cherry picked from commit 30fab74)

commit d4a07b6f195be963cc7f48bb4d63829e348948cf
Author: alexdel 
Date:   2018-03-02T02:30:29Z

IGNITE-7033 Web console: Adjusted width of columns on admin page.

(cherry picked from commit 6733a4d)

commit e6dda9769568bcd1538005e21256d2ff3a1f7b73
Author: devozerov 
Date:   2018-03-02T10:48:31Z

Merge branch 'ignite-2.4' into ignite-2.4.3

commit f9ce2c07046a1a413ea69ef5d32f91af70c06863
Author: Dmitriy Govorukhin 
Date:   2018-03-02T12:11:50Z

IGNITE-7865 Supported serializerVersion method for WAL manager - Fixes 
#3594.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 9

[MTCGA]: new failures in builds [1499957] needs to be handled

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New test failure in master 
CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=139506597706397620&branch=%3Cdefault%3E&tab=testDetails
 Changes may led to failure were done by - ivandasch 
http://ci.ignite.apache.org/viewModification.html?modId=825683&personal=false

- If your changes can led to this failure(s), please create issue with 
label MakeTeamCityGreenAgain and assign it to you.
-- If you have fix, please set ticket to PA state and write to dev list 
fix is ready 
-- For case fix will require some time please mute test and set label 
Muted_Test to issue 
- If you know which change caused failure please contact change author 
directly
- If you don't know which change caused failure please send message to 
dev list to find out
Should you have any questions please contact dpav...@apache.org or write to 
dev.list 
Best Regards,
MTCGA.Bot 
Notification generated at Tue Jul 17 02:06:49 MSK 2018 

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Denis Magda]

Released 2.6 readme.io documentation.

Andrey, I'll send you an announcement template privately. This time there
is no sense to publish a blog post for me, so you can announce the release
once all the post-steps are completed.

--
Denis

On Mon, Jul 16, 2018 at 1:37 PM Pavel Tupitsyn  wrote:

> Petr,
>
> This is the same build that I have linked. Is there anything I should pay
> attention to?
>
> On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov  wrote:
>
> > Pavel,
> >
> >
> > Before uploading, please check this [1] build.
> >
> >
> > [1]
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> > <
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> > >
> >
> >
> >
> >
> > > On 16 Jul 2018, at 22:56, Pavel Tupitsyn  wrote:
> > >
> > > I will upload NuGet packages. Is this the right TC build?
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv
> > >
> > > On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura  wrote:
> > >
> > >> Ignite site is updated. Most artifacts are published.
> > >>
> > >> Waiting for publishing of Docker images and 2.6 related docs. Also it
> > >> would be great to check NuGet packages.
> > >> On Mon, Jul 16, 2018 at 7:32 PM Denis Magda 
> wrote:
> > >>>
> > >>> Andrey,
> > >>>
> > >>> I'll publish the docs later today.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>> On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura 
> wrote:
> > >>>
> >  Dmitry,
> > 
> >  I'm updating the site at this moment. Could somebody publish 2.6
> >  documentation on readme.io site?
> >  On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan <
> > >> dsetrak...@apache.org>
> >  wrote:
> > >
> > > Is there a reason why 2.6 has not been uploaded to the website yet?
> > >
> > > D.
> > >
> > > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura 
> > >> wrote:
> > >
> > >> Igniters,
> > >>
> > >> Apache Ignite 2.6.0 release (RC1) has been accepted.
> > >>
> > >> 5 "+1" binding votes received:
> > >>
> > >> - Alexey Goncharuk
> > >> - Alexey Kuznetsov
> > >> - Andrey Gura
> > >> - Anton Vinogradov
> > >> - Denis Magda
> > >>
> > >> Vote thread:
> > >>
> > >> *http://apache-ignite-developers.2346864.n4.nabble.
> > >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > >>  > >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > >>
> > >> Ignite 2.6.0 will be released soon.
> > >>
> > 
> > >>
> >
> >
>

Re: Potential OOM while iterating over query cursor. Review needed.

[Dmitriy Setrakyan]

On Mon, Jul 16, 2018 at 5:42 PM, Yakov Zhdanov  wrote:

> Dmitry, let's have only getNext() same as jdbc. All other shortcuts seem to
> overload API without adding much value.
>

Agree. Do you mind creating a ticket?

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Pavel Tupitsyn]

Petr,

This is the same build that I have linked. Is there anything I should pay
attention to?

On Mon, Jul 16, 2018 at 11:05 PM Petr Ivanov  wrote:

> Pavel,
>
>
> Before uploading, please check this [1] build.
>
>
> [1]
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> <
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
> >
>
>
>
>
> > On 16 Jul 2018, at 22:56, Pavel Tupitsyn  wrote:
> >
> > I will upload NuGet packages. Is this the right TC build?
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv
> >
> > On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura  wrote:
> >
> >> Ignite site is updated. Most artifacts are published.
> >>
> >> Waiting for publishing of Docker images and 2.6 related docs. Also it
> >> would be great to check NuGet packages.
> >> On Mon, Jul 16, 2018 at 7:32 PM Denis Magda  wrote:
> >>>
> >>> Andrey,
> >>>
> >>> I'll publish the docs later today.
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura  wrote:
> >>>
>  Dmitry,
> 
>  I'm updating the site at this moment. Could somebody publish 2.6
>  documentation on readme.io site?
>  On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan <
> >> dsetrak...@apache.org>
>  wrote:
> >
> > Is there a reason why 2.6 has not been uploaded to the website yet?
> >
> > D.
> >
> > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura 
> >> wrote:
> >
> >> Igniters,
> >>
> >> Apache Ignite 2.6.0 release (RC1) has been accepted.
> >>
> >> 5 "+1" binding votes received:
> >>
> >> - Alexey Goncharuk
> >> - Alexey Kuznetsov
> >> - Andrey Gura
> >> - Anton Vinogradov
> >> - Denis Magda
> >>
> >> Vote thread:
> >>
> >> *http://apache-ignite-developers.2346864.n4.nabble.
> >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> >>  >> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> >>
> >> Ignite 2.6.0 will be released soon.
> >>
> 
> >>
>
>

Re: Add cluster (de)activation events IGNITE-8376

[Dmitriy Setrakyan]

On Mon, Jul 16, 2018 at 8:36 PM, Sergey Dorozhkin 
wrote:

> Igniters, may be I'm wrong, but in my opinion it slightly different
> functionality.
> Lifecycle is more like user functionality witch provide simple way to add
> additional behavior to cluster.
> I can implement interface LifecycleBean, do some logic (may be inject
> Ignite instance into it),
> add my implementation into class path and change xml configuration. I do no
> need coding something else.
>
> Can I do it by simple events?
>
> For example, if I have one node without persistence, I can inject Ignite
> instance into my LifecycleBean, initiate cache, and load data into it using
> LifecycleEventType.AFTER_NODE_START.
> But if I have the cluster, I can't do it.
>

Not sure what this means. You would subscribe to any event
in BEFORE_NODE_START callback, including the activation events.

D.

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Petr Ivanov]

Pavel,


Before uploading, please check this [1] build.


[1] 
https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog&_focus=230#_state=230
 





> On 16 Jul 2018, at 22:56, Pavel Tupitsyn  wrote:
> 
> I will upload NuGet packages. Is this the right TC build?
> https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv
> 
> On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura  wrote:
> 
>> Ignite site is updated. Most artifacts are published.
>> 
>> Waiting for publishing of Docker images and 2.6 related docs. Also it
>> would be great to check NuGet packages.
>> On Mon, Jul 16, 2018 at 7:32 PM Denis Magda  wrote:
>>> 
>>> Andrey,
>>> 
>>> I'll publish the docs later today.
>>> 
>>> --
>>> Denis
>>> 
>>> On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura  wrote:
>>> 
 Dmitry,
 
 I'm updating the site at this moment. Could somebody publish 2.6
 documentation on readme.io site?
 On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan <
>> dsetrak...@apache.org>
 wrote:
> 
> Is there a reason why 2.6 has not been uploaded to the website yet?
> 
> D.
> 
> On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura 
>> wrote:
> 
>> Igniters,
>> 
>> Apache Ignite 2.6.0 release (RC1) has been accepted.
>> 
>> 5 "+1" binding votes received:
>> 
>> - Alexey Goncharuk
>> - Alexey Kuznetsov
>> - Andrey Gura
>> - Anton Vinogradov
>> - Denis Magda
>> 
>> Vote thread:
>> 
>> *http://apache-ignite-developers.2346864.n4.nabble.
>> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
>> > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
>> 
>> Ignite 2.6.0 will be released soon.
>> 
 
>> 

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Pavel Tupitsyn]

I will upload NuGet packages. Is this the right TC build?
https://ci.ignite.apache.org/viewLog.html?buildId=1502954&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv

On Mon, Jul 16, 2018 at 8:43 PM Andrey Gura  wrote:

> Ignite site is updated. Most artifacts are published.
>
> Waiting for publishing of Docker images and 2.6 related docs. Also it
> would be great to check NuGet packages.
> On Mon, Jul 16, 2018 at 7:32 PM Denis Magda  wrote:
> >
> > Andrey,
> >
> > I'll publish the docs later today.
> >
> > --
> > Denis
> >
> > On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura  wrote:
> >
> > > Dmitry,
> > >
> > > I'm updating the site at this moment. Could somebody publish 2.6
> > > documentation on readme.io site?
> > > On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > > wrote:
> > > >
> > > > Is there a reason why 2.6 has not been uploaded to the website yet?
> > > >
> > > > D.
> > > >
> > > > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura 
> wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Apache Ignite 2.6.0 release (RC1) has been accepted.
> > > > >
> > > > > 5 "+1" binding votes received:
> > > > >
> > > > > - Alexey Goncharuk
> > > > > - Alexey Kuznetsov
> > > > > - Andrey Gura
> > > > > - Anton Vinogradov
> > > > > - Denis Magda
> > > > >
> > > > > Vote thread:
> > > > >
> > > > > *http://apache-ignite-developers.2346864.n4.nabble.
> > > > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > > > >  > > > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > > > >
> > > > > Ignite 2.6.0 will be released soon.
> > > > >
> > >
>

[GitHub] ignite pull request #4369: Ignite-9013

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

Ignite-9013



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

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

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

https://github.com/apache/ignite/pull/4369.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 #4369


commit 63a9aa7d8ae55aeaed98e36aec55854789bbba9e
Author: EdShangGG 
Date:   2018-07-16T13:23:45Z

IGNITE-9012 Test IgniteServiceReassignmentTest.testZombieAssignmentsCleanup 
fails

Signed-off-by: EdShangGG 

commit afd0944f66b0501515478623e88e47a69084205a
Author: EdShangGG 
Date:   2018-07-16T18:49:28Z

IGNITE-9013 Node stop hangs if there was cache activities in Service 
Processor

Signed-off-by: EdShangGG 




---

Re: Neighbors exclusion

[Yakov Zhdanov]

Dmitry, it hink we can do this change right away. All we need is to add
proper error message on cache config validation in order to tell user that
default changed and manual configuration is needed for compatibility.

--Yakov

2018-07-16 15:47 GMT+03:00 Dmitry Karachentsev :

> Created a ticket and mapped to 3.0 version, as it changes basic default
> behavior:
> https://issues.apache.org/jira/browse/IGNITE-9011
>
> Thanks!
>
> 13.07.2018 22:10, Valentin Kulichenko пишет:
>
> Dmitry,
>>
>> Good point. I think it makes sense to even remove (deprecate) the
>> excludeNeighbors property and always distribute primary and backups to
>> different physical hosts in this scenario. Because why would anyone ever
>> set this to false if we switch default to true? This also automatically
>> fixes the confusing behavior of backupFilter - it should never be ignored
>> if it's set.
>>
>> -Val
>>
>> On Fri, Jul 13, 2018 at 8:05 AM Dmitry Karachentsev <
>> dkarachent...@gridgain.com> wrote:
>>
>> Hi folks,
>>>
>>> Why RendezvousAffinityFunction.excludeNeighbors [1] is false by default?
>>> It's not obvious that if user wants to run more than one node per
>>> machine it has also set this flag to true explicitly. Maybe it would be
>>> better to set it to true by default?
>>>
>>> At the same time if excludeNeighbors is true, it ignores backupFilter.
>>> Why it's not vice-versa? For example:
>>>
>>> 1) if backupFilter is set - it will be used,
>>>
>>> 2) if there are not enough backup nodes (or no backupFilter) - try to
>>> distribute according to excludeNeighbors = true,
>>>
>>> 3) if this is not possible too (or excludeNeighbors) = false - assign
>>> partitions as possible.
>>>
>>> [1]
>>>
>>> https://ignite.apache.org/releases/latest/javadoc/org/apache
>>> /ignite/cache/affinity/rendezvous/RendezvousAffinityFunction
>>> .html#setExcludeNeighbors-boolean-
>>>
>>> Are there any drawbacks in such approach?
>>>
>>> Thanks!
>>>
>>>
>>>
>

Re: Ignite guide for community developes

[Dmitry Pavlov]

Sure, I will do. Sign up to JIRA and wiki, it is open for everyone. Then I
need username(s) to add appropriate contributor role.

пн, 16 июл. 2018 г. в 20:53, Yakov Zhdanov :

> I think you need to signup to Apache jira and let us know your user ID so
> we can add you to contributors. Dmitry Pavlov, can you please help.
>
> --Yakov
>
> 2018-07-12 18:54 GMT+03:00 vgrigorev :
>
> > Hi colleges!
> >
> > I would like move topic to suitable place.
> >
> > Please only clarify how to do it:
> > In a page about creating IEP
> > link
> >  > Ignite+Enhancement+Proposal?showChildren=false>
> > There are no appropriate information.
> >
> > If you can do it please do.
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>

Re: Async cache groups rebalance not started with rebalanceOrder ZERO

[Yakov Zhdanov]

Maxim, I looked at the code you provided. I think we need to add some
timeout validation and output warning to logs on demander side in case
there is no supply message within 30 secs and repeat demanding process.
This should apply to any demand message throughout the rebalancing process
not only the 1st one.

You can use the following message

Failed to wait for supply message from node within 30 secs [cache=C,
partId=XX]

Alex Goncharuk do you have comments here?

Yakov Zhdanov
www.gridgain.com

2018-07-14 19:45 GMT+03:00 Maxim Muzafarov :

> Yakov,
>
> Yes, you're right. Whole rebalancing progress will be stopped.
>
> Actually, rebalancing order doesn't matter you right it too. Javadoc just
> says the idea how rebalance should work for caches but in fact it don't
> work as described. Personally, I'd prefer to start rebalance of each cache
> group in async way independently.
>
> Please, look at my reproducer [1].
>
> Scenario:
> Cluster with two REPLICATEDED caches.
> Start new node.
> First rebalance cache group is failed to start (e.g. network issues) - it's
> OK.
> Second rebalance cache group will neber be started - whole futher progress
> stucks (I think rebalance here should be started!).
>
>
> [1]
> https://github.com/Mmuzaf/ignite/blob/rebalance-cancel/
> modules/core/src/test/java/org/apache/ignite/internal/
> processors/cache/distributed/rebalancing/GridCacheRebalancingCancelSelf
> Test.java
>
> пт, 13 июл. 2018 г. в 17:46, Yakov Zhdanov :
>
> > Maxim, I do not understand the problem. Imagine I do not have any
> ordering
> > but rebalancing of some cache fails to start - so in my understanding
> > overall rebalancing progress becomes blocked. Is that true?
> >
> > Can you pleaes provide reproducer for your problem?
> >
> > --Yakov
> >
> > 2018-07-09 16:42 GMT+03:00 Maxim Muzafarov :
> >
> > > Hello Igniters,
> > >
> > > Each cache group has “rebalance order” property. As javadoc for
> > > getRebalanceOrder() says: “Note that cache with order {@code 0} does
> not
> > > participate in ordering. This means that cache with rebalance order
> > {@code
> > > 0} will never wait for any other caches. All caches with order {@code
> 0}
> > > will be rebalanced right away concurrently with each other and ordered
> > > rebalance processes. If not set, cache order is 0, i.e. rebalancing is
> > not
> > > ordered.”
> > >
> > > In fact GridCachePartitionExchangeManager always build the chain of
> > > rebalancing cache groups to start (even for cache order ZERO):
> > >
> > > ignite-sys-cache -> cacheR -> cacheR3 -> cacheR2 -> cacheR5 -> cacheR1.
> > >
> > > If one of these groups will fail to start further groups will never be
> > run.
> > >
> > > * Question 1*: Should we fix javadoc description or create a bug for
> > fixing
> > > such rebalance behavior?
> > >
> > > [1]
> > > https://github.com/apache/ignite/blob/master/modules/
> > > core/src/main/java/org/apache/ignite/internal/processors/cache/
> > > GridCachePartitionExchangeManager.java#L2630
> > >
> >
> --
> --
> Maxim Muzafarov
>

[jira] [Created] (IGNITE-9013) Node stop hangs if there was cache activities in Service Processor

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-9013:
-

 Summary: Node stop hangs if there was cache activities in Service 
Processor
 Key: IGNITE-9013
 URL: https://issues.apache.org/jira/browse/IGNITE-9013
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev


I have found this issue while running 
IgniteServiceReassignmentTest#testZombieAssignmentsCleanup.

And test hanged with:
{code}
"main@1" prio=5 tid=0x1 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
  at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
  at 
java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1465)
  at 
java.util.concurrent.Executors$DelegatedExecutorService.awaitTermination(Executors.java:675)
  at 
org.apache.ignite.internal.util.IgniteUtils.shutdownNow(IgniteUtils.java:4749)
  at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStop(GridServiceProcessor.java:327)
  at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2130)
  at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2077)
  at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2595)
  - locked <0x273d> (a 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
  at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2558)
  at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
  at org.apache.ignite.Ignition.stop(Ignition.java:229)
  at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1088)
  at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1131)
  at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1109)
  at 
org.apache.ignite.internal.processors.service.IgniteServiceReassignmentTest.afterTest(IgniteServiceReassignmentTest.java:82)
  at 
org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1694)
  at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:497)
  at junit.framework.TestCase.runBare(TestCase.java:146)
  at junit.framework.TestResult$1.protect(TestResult.java:122)
  at junit.framework.TestResult.runProtected(TestResult.java:142)
  at junit.framework.TestResult.run(TestResult.java:125)
  at junit.framework.TestCase.run(TestCase.java:129)
  at junit.framework.TestSuite.runTest(TestSuite.java:255)
  at junit.framework.TestSuite.run(TestSuite.java:250)
  at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
  at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
  at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
  at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54)
  at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
  at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
{code}

{code}
"srvc-deploy-#811%service.IgniteServiceReassignmentTest2%@5000" prio=5 
tid=0x3d9 nid=NA waiting
  java.lang.Thread.State: WAITING
  at sun.misc.Unsafe.park(Unsafe.java:-1)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
  at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter$37.op(GridCacheAdapter.java:2959)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4150)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAndRemove0(GridCacheAdapter.java:2948)
  at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAndRemove(GridCacheAdapter.java:2932)
  at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1897)
  at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2076)
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  at java.lang.Thread.run(Thread.java:745)
{code]



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

Re: Ignite guide for community developes

[Yakov Zhdanov]

I think you need to signup to Apache jira and let us know your user ID so
we can add you to contributors. Dmitry Pavlov, can you please help.

--Yakov

2018-07-12 18:54 GMT+03:00 vgrigorev :

> Hi colleges!
>
> I would like move topic to suitable place.
>
> Please only clarify how to do it:
> In a page about creating IEP
> link
>  Ignite+Enhancement+Proposal?showChildren=false>
> There are no appropriate information.
>
> If you can do it please do.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Andrey Gura]

Ignite site is updated. Most artifacts are published.

Waiting for publishing of Docker images and 2.6 related docs. Also it
would be great to check NuGet packages.
On Mon, Jul 16, 2018 at 7:32 PM Denis Magda  wrote:
>
> Andrey,
>
> I'll publish the docs later today.
>
> --
> Denis
>
> On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura  wrote:
>
> > Dmitry,
> >
> > I'm updating the site at this moment. Could somebody publish 2.6
> > documentation on readme.io site?
> > On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan 
> > wrote:
> > >
> > > Is there a reason why 2.6 has not been uploaded to the website yet?
> > >
> > > D.
> > >
> > > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura  wrote:
> > >
> > > > Igniters,
> > > >
> > > > Apache Ignite 2.6.0 release (RC1) has been accepted.
> > > >
> > > > 5 "+1" binding votes received:
> > > >
> > > > - Alexey Goncharuk
> > > > - Alexey Kuznetsov
> > > > - Andrey Gura
> > > > - Anton Vinogradov
> > > > - Denis Magda
> > > >
> > > > Vote thread:
> > > >
> > > > *http://apache-ignite-developers.2346864.n4.nabble.
> > > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > > >  > > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > > >
> > > > Ignite 2.6.0 will be released soon.
> > > >
> >

Re: Add cluster (de)activation events IGNITE-8376

[Sergey Dorozhkin]

Igniters, may be I'm wrong, but in my opinion it slightly different
functionality.
Lifecycle is more like user functionality witch provide simple way to add
additional behavior to cluster.
I can implement interface LifecycleBean, do some logic (may be inject
Ignite instance into it),
add my implementation into class path and change xml configuration. I do no
need coding something else.

Can I do it by simple events?

For example, if I have one node without persistence, I can inject Ignite
instance into my LifecycleBean, initiate cache, and load data into it using
LifecycleEventType.AFTER_NODE_START.
But if I have the cluster, I can't do it.

Thanks.

чт, 12 июл. 2018 г. в 15:25, Dmitriy Setrakyan :

> On Thu, Jul 12, 2018 at 3:22 PM, Yakov Zhdanov 
> wrote:
>
> > If events are working when grid is not active and adding/removing
> listeners
> > is also possible then I agree/
> >
>
> The events should be working. The cluster is not active, but the node is
> started and should be able to fire events.
>
> AG, can you comment?
>


-- 
*Best regards, Sergey.*

RE: Can .NET thin client have cache expire policy?

[Stanislav Lukyanov]

Oops, wrong link.
The correct one: 
http://apache-ignite-users.70518.x6.nabble.com/Thin-client-doesn-t-support-Expiry-Policies-tt22422.html

From: Stanislav Lukyanov
Sent: 16 июля 2018 г. 14:18
To: dev@ignite.apache.org
Subject: RE: Can .NET thin client have cache expire policy?

The same question is being discussed on the user-list:
https://stackoverflow.com/questions/51314852/is-there-a-workaround-to-use-thin-client-with-cache-expiry-policy-in-apache-igni

Stan 

From: Dmitriy Setrakyan
Sent: 16 июля 2018 г. 3:03
To: dev
Cc: Pavel Tupitsyn
Subject: Can .NET thin client have cache expire policy?

This question has been asked of the Stack Overflow:

https://stackoverflow.com/questions/51314852/is-there-a-workaround-to-use-thin-client-with-cache-expiry-policy-in-apache-igni

Would be nice to provide an answer. Pavel, can you respond?

Thanks,
D.

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Denis Magda]

Andrey,

I'll publish the docs later today.

--
Denis

On Mon, Jul 16, 2018 at 8:46 AM Andrey Gura  wrote:

> Dmitry,
>
> I'm updating the site at this moment. Could somebody publish 2.6
> documentation on readme.io site?
> On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan 
> wrote:
> >
> > Is there a reason why 2.6 has not been uploaded to the website yet?
> >
> > D.
> >
> > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura  wrote:
> >
> > > Igniters,
> > >
> > > Apache Ignite 2.6.0 release (RC1) has been accepted.
> > >
> > > 5 "+1" binding votes received:
> > >
> > > - Alexey Goncharuk
> > > - Alexey Kuznetsov
> > > - Andrey Gura
> > > - Anton Vinogradov
> > > - Denis Magda
> > >
> > > Vote thread:
> > >
> > > *http://apache-ignite-developers.2346864.n4.nabble.
> > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > >  > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > >
> > > Ignite 2.6.0 will be released soon.
> > >
>

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Andrey Gura]

Pavel,

could you please assist with NuGet packages?
On Mon, Jul 16, 2018 at 6:46 PM Andrey Gura  wrote:
>
> Dmitry,
>
> I'm updating the site at this moment. Could somebody publish 2.6
> documentation on readme.io site?
> On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan  
> wrote:
> >
> > Is there a reason why 2.6 has not been uploaded to the website yet?
> >
> > D.
> >
> > On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura  wrote:
> >
> > > Igniters,
> > >
> > > Apache Ignite 2.6.0 release (RC1) has been accepted.
> > >
> > > 5 "+1" binding votes received:
> > >
> > > - Alexey Goncharuk
> > > - Alexey Kuznetsov
> > > - Andrey Gura
> > > - Anton Vinogradov
> > > - Denis Magda
> > >
> > > Vote thread:
> > >
> > > *http://apache-ignite-developers.2346864.n4.nabble.
> > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> > >  > > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> > >
> > > Ignite 2.6.0 will be released soon.
> > >

[GitHub] ignite pull request #4368: IGNITE-7165 Rebalance control version holds by ex...

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

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

IGNITE-7165 Rebalance control version holds by exchange thread



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

$ git pull https://github.com/Mmuzaf/ignite av-ignit-7165-2

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

https://github.com/apache/ignite/pull/4368.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 #4368


commit e7a80e64da07af5c43c15fd5a7b1abe14d387057
Author: Maxim Muzafarov 
Date:   2018-05-30T16:46:06Z

IGNITE-7165: add fix by suggestions AV

commit 9f7551c15ff62c187422095c0626200245c36a36
Author: Maxim Muzafarov 
Date:   2018-05-30T16:49:01Z

IGNITE-7165: revert some

commit 0ab2d301bd5a100f8dcf1ef964786264ebee6b0a
Author: Maxim Muzafarov 
Date:   2018-05-30T17:39:04Z

IGNITE-7165: changes due to else if

commit 0d37670990f6546202771313ba0869bd2b709ad4
Author: Maxim Muzafarov 
Date:   2018-06-07T12:56:45Z

Merge branch 'master' into av-ignite-7165

commit 7673f1afdb7eaa79d4e03ee16083ee5ea4b92290
Author: Maxim Muzafarov 
Date:   2018-06-07T14:29:51Z

IGNITE-7165: add assignments calculations compare

commit ce2ea0b397f416a764681259911adf04fa397d61
Author: Maxim Muzafarov 
Date:   2018-06-07T20:28:09Z

IGNITE-7165: hasPendingExchanges flag to start rebalance

commit 9f5d9f7871ba9cff079a76097bb4f269fd7f7a5b
Author: Maxim Muzafarov 
Date:   2018-06-07T20:30:39Z

IGNITE-7165: rename rebalance assingns needs

commit 4dcb6270d026f36fb7b3ae2b904ce36bc633ac55
Author: Maxim Muzafarov 
Date:   2018-06-07T20:35:29Z

IGNITE-7165: javadoc

commit cccdd69b86ebcce1626dfc9416f32f88e708d4e9
Author: Maxim Muzafarov 
Date:   2018-06-08T15:06:39Z

IGNITE-7165: remove skip rebalance twice

commit 3410aaca6298be1b3b26c5202b43a1b787123396
Author: Maxim Muzafarov 
Date:   2018-06-10T13:50:00Z

IGNITE-7165: calculate assigns on last running topology version

commit 5f98a480a07d2c0504a60763da482c2792540719
Author: Maxim Muzafarov 
Date:   2018-06-19T11:00:32Z

Merge branch 'master' into av-ignite-7165

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPreloader.java

commit cfb9574d65f64660f36689789b0090ef0be50fcb
Author: Maxim Muzafarov 
Date:   2018-06-20T16:48:28Z

IGNITE-7165: keep last rebalance topology version

commit d15515f3ee83455697dead6ff39e75dafebcfd76
Author: Maxim Muzafarov 
Date:   2018-06-20T17:10:11Z

IGNITE-7165: return last rebalance topology version

commit d0d47eb0eda31165f5c8f1e53ef92ecf82d9c548
Author: Maxim Muzafarov 
Date:   2018-06-21T10:29:15Z

IGNITE-7165: default value for rebalance topVer should be null

commit 68d53d7c317ee676c08d45b6a4be360bb4659fb7
Author: Maxim Muzafarov 
Date:   2018-06-21T10:30:56Z

Merge branch 'master' into av-ignite-7165

commit 4cf7c72e9db55d47a305f93c649d29e6557354e2
Author: Maxim Muzafarov 
Date:   2018-06-21T10:33:55Z

IGNITE-7165: debug messages for update topology version

commit 7bd0be89c66bf5bf78f88c5e30d32c70c79a5fcd
Author: Maxim Muzafarov 
Date:   2018-06-22T09:11:33Z

ignite-7165: skip if null

commit 4b2e232c0d97452986fe79f6c33ec62e5b9ad9a7
Author: Maxim Muzafarov 
Date:   2018-06-22T09:46:34Z

ignite-7165: java doc update

commit 682194b1597a91a86c4b3546a8f3726bdae07254
Author: Maxim Muzafarov 
Date:   2018-06-22T12:20:11Z

ignite-7165: move latest ver to rebalance future

commit d9fbea3af09478332347181c3f2b330541a7e7b5
Author: Maxim Muzafarov 
Date:   2018-06-22T14:29:06Z

ignite-7165: use get topology version method

commit 15d90b01535c9e199286b6cd5cdd16e0eb28e76e
Author: Maxim Muzafarov 
Date:   2018-06-22T14:39:21Z

ignite-7165: fix javadoc exchange

commit 9568763143cf136cfc4e15ab4076f654c9f78131
Author: Maxim Muzafarov 
Date:   2018-06-22T14:47:16Z

ignite-7165: remove unnecessary topology check

commit 648ab2df71f4a06e59843371181ba0c075efed2f
Author: Maxim Muzafarov 
Date:   2018-06-22T14:51:34Z

ignite-7165: java doc fix 2

commit 84d4cfa4b08226f8d2ad8cb163dd3015675692ec
Author: Maxim Muzafarov 
Date:   2018-06-22T15:00:04Z

ignite-7165: force rebalance routine

commit 38218eeea65574c8d3965fddaf2b037e60127ac9
Author: Maxim Muzafarov 
Date:   2018-06-22T15:01:36Z

ignite-7165: force rebalance 2

commit aa21fd2133b0fca74a135795bbab1393ec56fb87
Author: Maxim Muzafarov 
Date:   2018-06-22T15:05:38Z

ignite-7165: simplify topology changed conditions

commit 66b5f76c15cb67b60adeca864a21fdad39acf6f7
Author: Maxim Muzafarov 
Date:   2018-06-22T15:10:43Z

ignite-7165: new java doc for assignments

commit a097a153ed637f2928a1c183af28c3050213df08
Author: Maxim Muzafarov 
Date:   2018-06-22T15:46:56Z

ignite-7165: reorganize newly added methods

commit a0fca19c12045461ba3fc4bac25b75b27dada7ae
Author: Maxi

[GitHub] ignite pull request #4109: Tests fail after IGNITE-6639

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Ability to check and completely fill transactions on creation

[Anton Vinogradov]

Dmitriy,

Yes, this achieves the same purpose, thanks for hint.
Updated PR to use strictly setRollbackOnly().

ср, 11 июл. 2018 г. в 4:17, Dmitriy Setrakyan :

> Anton,
>
> Committing or rolling back from MXBean is OK, because it is not a listener,
> but a direct invocation. However, it is not OK to allow synchronous
> rollback from a filter or a listener. The only action you can do from a
> listener is setRollbackOnly() which will cause the transaction to be rolled
> back eventually. I think it achieves the same purpose.
>
> D.
>
> On Mon, Jul 9, 2018 at 2:25 PM, Anton Vinogradov  wrote:
>
> > Dmitriy,
> >
> > Rollback from remote filter uses rollbackOnlyProxy [1], that's a special
> > proxy allows rollback from another thread.
> > It was specially designed to rollback transactions by "label" if
> necessary.
> > So, I'm just finishing "label feature" to make it more useful at real
> > production.
> >
> > Here's the example of remote filter with rollback (more examples can be
> > found at PR [2])
> >
> > ignite.events().remoteListen(null,
> > (IgnitePredicate)e -> {
> > TransactionStateChangedEvent evt = (TransactionStateChangedEvent)e;
> > Transaction tx = evt.tx();
> > if (tx.label() == null) // Timeout and orher details can be checked as
> > well.
> > tx.rollback();
> > return true;
> > }, EVT_TX_STARTED);
> >
> > >> Calling rollback() or commit() from any filter or listener should not
> be
> > allowed.
> > Only rollback allowed, but reasonable question is "Why?", now I see we
> > already doing this at:
> > - TransactionsMXBean#getActiveTransactions -> foreach.rollback
> > - control.sh --tx kill Xid
> >
> > The only one difference is that filter or listener can validate or/and
> > rollback any tx synchronously, before it breaks something (eg. on start
> or
> > resume),
> > while TransactionsMXBean#getActiveTransactions or control.sh do this in
> > batch way without any sync warranty.
> >
> >
> > [1]
> > org.apache.ignite.internal.processors.cache.distributed.
> > near.GridNearTxLocal#rollbackOnlyProxy
> > [2] https://github.com/apache/ignite/pull/4036
> >
> > пн, 9 июл. 2018 г. в 7:04, Dmitriy Setrakyan :
> >
> > > Anton, how do you plan to rollback the transaction from a remote
> filter?
> > > Are you planning to call setRollbackOnly()? Calling rollback() or
> > commit()
> > > from any filter or listener should not be allowed.
> > >
> > > D.
> > >
> > > On Tue, Jul 3, 2018 at 1:55 AM, Anton Vinogradov 
> wrote:
> > >
> > > > Dmitriy, Yakov,
> > > >
> > > > I've finalized design and prepared the solution [1].
> > > >
> > > > 1) Only events from GridNearTxLocal are registered now.
> > > >
> > > > List of possible events:
> > > >  public static final int[] EVTS_TX = {
> > > > EVT_TX_STARTED,
> > > > EVT_TX_COMMITTED,
> > > > EVT_TX_ROLLED_BACK,
> > > > EVT_TX_SUSPENDED,
> > > > EVT_TX_RESUMED
> > > > };
> > > > 2) Transaction can be rolled back now inside
> > > > - remote filter (always, since it always happens on node started this
> > > > transaction)
> > > > - local listener (only at node started this transaction)
> > > >
> > > > Rollback uses rollbackOnlyProxy [2] specially designed (and tested)
> to
> > > > rollback any tx from any thread at node started the transaction.
> > > >
> > > > I see another public tools doing the same:
> > > > - TransactionsMXBean#getActiveTransactions
> > > > - control.sh --tx kill Xid
> > > >
> > > > Both able to rollback any tx at any state remotely.
> > > >
> > > > Yakov,
> > > > could you please review the code?
> > > >
> > > > [1] https://github.com/apache/ignite/pull/4036 (TC checked)
> > > > [2]
> > > > org.apache.ignite.internal.processors.cache.distributed.
> > > > near.GridNearTxLocal#rollbackOnlyProxy
> > > >
> > > > пт, 1 июн. 2018 г. в 23:33, Dmitriy Setrakyan  >:
> > > >
> > > > > Anton, we are very far from agreement. I think it makes sense to
> step
> > > > back,
> > > > > come up with a clean design and propose it again.
> > > > >
> > > > > On Fri, Jun 1, 2018 at 12:59 PM, Anton Vinogradov 
> > > wrote:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > Unfortunately, we have more than 2 types of txs, full list is
> > > > > >
> > > > > > GridDhtTxLocal
> > > > > > GridDhtTxRemote
> > > > > > GridNearTxLocal
> > > > > > GridNearTxRemote
> > > > > >
> > > > > > BTW, We have no clear documentation about behaviour and
> difference.
> > > > > > I created an issue [1] to solve this, but seems no one interested
> > :(
> > > > > >
> > > > >
> > > > > The reason we do not have a documentation for these transaction
> > classes
> > > > is
> > > > > because they are part of the internal implementation and should
> never
> > > be
> > > > > exposed to users.
> > > > >
> > > > > 1) What I see is that every Grid*Tx* have xid, startTime,
> isolation,
> > > > > > concurrency, etc. So, there is no difference in params.
> > > > > > Label is the only one exception to the rule, but this can be
> fixed.
> > > > > >
> > > > >
> >

[GitHub] ignite pull request #1558: IGNITE-602

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Andrey Gura]

Dmitry,

I'm updating the site at this moment. Could somebody publish 2.6
documentation on readme.io site?
On Mon, Jul 16, 2018 at 5:38 PM Dmitriy Setrakyan  wrote:
>
> Is there a reason why 2.6 has not been uploaded to the website yet?
>
> D.
>
> On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura  wrote:
>
> > Igniters,
> >
> > Apache Ignite 2.6.0 release (RC1) has been accepted.
> >
> > 5 "+1" binding votes received:
> >
> > - Alexey Goncharuk
> > - Alexey Kuznetsov
> > - Andrey Gura
> > - Anton Vinogradov
> > - Denis Magda
> >
> > Vote thread:
> >
> > *http://apache-ignite-developers.2346864.n4.nabble.
> > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
> >  > com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
> >
> > Ignite 2.6.0 will be released soon.
> >

Re: MTCGA: new failures in builds [1485687] needs to be handled

[kcheng.mvp]

I checked the source code and found that this issue may be caused by this
line

org.apache.ignite.internal.processors.cache.GridCacheProcessor #1452

CacheEvictionManager evictMgr = (nearEnabled || cfg.isOnheapCacheEnabled())
? new GridCacheEvictionManager() : new CacheOffheapEvictionManager();

as in this case a new CacheOffheapEvictionManager() will return, but this
implementation does not do any eviction bean register/unregister, as there
are no any policy.

are my findings wrong?



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4217: IGNITE-8820: Add ability to read new value of txT...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4367: IGNITE-9012 Test IgniteServiceReassignmentTest.te...

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

IGNITE-9012 Test IgniteServiceReassignmentTest.testZombieAssignmentsC…

…leanup fails

Signed-off-by: EdShangGG 

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

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

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

https://github.com/apache/ignite/pull/4367.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 #4367


commit 63a9aa7d8ae55aeaed98e36aec55854789bbba9e
Author: EdShangGG 
Date:   2018-07-16T13:23:45Z

IGNITE-9012 Test IgniteServiceReassignmentTest.testZombieAssignmentsCleanup 
fails

Signed-off-by: EdShangGG 




---

Re: Potential OOM while iterating over query cursor. Review needed.

[Yakov Zhdanov]

Dmitry, let's have only getNext() same as jdbc. All other shortcuts seem to
overload API without adding much value.

--Yakov

2018-07-16 17:33 GMT+03:00 Dmitriy Setrakyan :

> Well, instead of getFirst(), I would have getNext(). This way we do not
> have to keep the first entry forever, which could present a problem in case
> if entry is too large.
>
> As far as initializing keepAll() to false - completely agree.
>
> D.
>
> On Mon, Jul 16, 2018 at 4:43 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > No objections from my side. Would be nice to receive some feedback from
> > other community members, though, because this is formally a breaking
> > change.
> >
> > пн, 16 июл. 2018 г. в 16:40, Yakov Zhdanov :
> >
> > > Guys, it seems we need to deprecate getAll() and remove it in 3.0. I
> > think
> > > it is usable only for queries that return 1 row. Every other case needs
> > > iteration. So having getFirst() seems to be better. Thoughts?
> > >
> > > As far as ScanQuery I think we can properly initialize keepAll to false
> > on
> > > scan query instantiation. I am pretty sure none needs getAll() in
> scans.
> > > Alex?
> > >
> > > --
> > > Yakov
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Dmitriy Setrakyan]

Is there a reason why 2.6 has not been uploaded to the website yet?

D.

On Fri, Jul 13, 2018 at 9:02 PM, Andrey Gura  wrote:

> Igniters,
>
> Apache Ignite 2.6.0 release (RC1) has been accepted.
>
> 5 "+1" binding votes received:
>
> - Alexey Goncharuk
> - Alexey Kuznetsov
> - Andrey Gura
> - Anton Vinogradov
> - Denis Magda
>
> Vote thread:
>
> *http://apache-ignite-developers.2346864.n4.nabble.
> com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html
>  com/VOTE-Apache-Ignite-2-6-0-RC1-td32424.html>*
>
> Ignite 2.6.0 will be released soon.
>

[GitHub] ignite pull request #4357: ignite-8897

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Potential OOM while iterating over query cursor. Review needed.

[Dmitriy Setrakyan]

Well, instead of getFirst(), I would have getNext(). This way we do not
have to keep the first entry forever, which could present a problem in case
if entry is too large.

As far as initializing keepAll() to false - completely agree.

D.

On Mon, Jul 16, 2018 at 4:43 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> No objections from my side. Would be nice to receive some feedback from
> other community members, though, because this is formally a breaking
> change.
>
> пн, 16 июл. 2018 г. в 16:40, Yakov Zhdanov :
>
> > Guys, it seems we need to deprecate getAll() and remove it in 3.0. I
> think
> > it is usable only for queries that return 1 row. Every other case needs
> > iteration. So having getFirst() seems to be better. Thoughts?
> >
> > As far as ScanQuery I think we can properly initialize keepAll to false
> on
> > scan query instantiation. I am pretty sure none needs getAll() in scans.
> > Alex?
> >
> > --
> > Yakov
> >
>

[GitHub] ignite pull request #4256: IGNITE-8745 Make tcp-disco-worker thread name ref...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Potential OOM while iterating over query cursor. Review needed.

[Alexey Goncharuk]

No objections from my side. Would be nice to receive some feedback from
other community members, though, because this is formally a breaking change.

пн, 16 июл. 2018 г. в 16:40, Yakov Zhdanov :

> Guys, it seems we need to deprecate getAll() and remove it in 3.0. I think
> it is usable only for queries that return 1 row. Every other case needs
> iteration. So having getFirst() seems to be better. Thoughts?
>
> As far as ScanQuery I think we can properly initialize keepAll to false on
> scan query instantiation. I am pretty sure none needs getAll() in scans.
> Alex?
>
> --
> Yakov
>

[GitHub] ignite pull request #4366: alternative fix for client reconnect with Zookeep...

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

alternative fix for client reconnect with ZookeeperDiscoverySpi



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

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

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

https://github.com/apache/ignite/pull/4366.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 #4366


commit 55fb026a5dc464e1cdad6bbb0b81c3bad0ac51d0
Author: Sergey Chugunov 
Date:   2018-07-16T13:34:46Z

IGNITE-8131 alternative fix for client reconnect with ZookeeperDiscoverySPI




---

Re: Potential OOM while iterating over query cursor. Review needed.

[Yakov Zhdanov]

Guys, it seems we need to deprecate getAll() and remove it in 3.0. I think
it is usable only for queries that return 1 row. Every other case needs
iteration. So having getFirst() seems to be better. Thoughts?

As far as ScanQuery I think we can properly initialize keepAll to false on
scan query instantiation. I am pretty sure none needs getAll() in scans.
Alex?

--
Yakov

[GitHub] ignite pull request #4243: IGNITE-8774 Daemon moves cluster to compatibility...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Delete ticket - issues.apache.org

[Alexey Goncharuk]

Hi,

You can edit the ticket so it does not display any information, but the
content will be still accessible in the history. We can change the ticket
visibility to private, but it will be still be accessible for committers. I
suggest you contact Apache infra team regarding your request.

ср, 20 июн. 2018 г. в 11:15, Puviarasu S :

> Hi Team,
>
> I have created a ticket in https://issues.apache.org/jira. I am in a
> situation to delete the ticket such that it is not accessible over the
> Internet.
>
> Kindly requesting you to help me in deleting the ticket from Apache JIRA.
>
> Thanks in advance!!!
>
> Regards,
> Puviarasu
>

[jira] [Created] (IGNITE-9012) Test IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-9012:
-

 Summary: Test 
IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails 
 Key: IGNITE-9012
 URL: https://issues.apache.org/jira/browse/IGNITE-9012
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev


Example:
https://ci.ignite.apache.org/viewLog.html?buildId=1499947&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Basic1#testNameId4751597304481704825

{test}
[2018-07-16 10:50:03,888][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertFalse(Assert.java:39)
at junit.framework.Assert.assertFalse(Assert.java:47)
at junit.framework.TestCase.assertFalse(TestCase.java:219)
at 
org.apache.ignite.internal.processors.service.IgniteServiceReassignmentTest.testZombieAssignmentsCleanup(IgniteServiceReassignmentTest.java:237)
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:2087)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
at java.lang.Thread.run(Thread.java:748)
{test}



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

[GitHub] ignite pull request #4365: IGNITE-8985 - Node segmented itself after connRec...

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

IGNITE-8985 - Node segmented itself after connRecoveryTimeout. Improv…

…ed loopback resolving from IGNITE-8683.

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

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

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

https://github.com/apache/ignite/pull/4365.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 #4365


commit a61635b306d3e7a3977708ec027ab31c67f8ad1a
Author: dkarachentsev 
Date:   2018-07-16T12:50:32Z

IGNITE-8985 - Node segmented itself after connRecoveryTimeout. Improved 
loopback resolving from IGNITE-8683.




---

Re: Neighbors exclusion

[Dmitry Karachentsev]

Created a ticket and mapped to 3.0 version, as it changes basic default 
behavior:

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

Thanks!

13.07.2018 22:10, Valentin Kulichenko пишет:

Dmitry,

Good point. I think it makes sense to even remove (deprecate) the
excludeNeighbors property and always distribute primary and backups to
different physical hosts in this scenario. Because why would anyone ever
set this to false if we switch default to true? This also automatically
fixes the confusing behavior of backupFilter - it should never be ignored
if it's set.

-Val

On Fri, Jul 13, 2018 at 8:05 AM Dmitry Karachentsev <
dkarachent...@gridgain.com> wrote:


Hi folks,

Why RendezvousAffinityFunction.excludeNeighbors [1] is false by default?
It's not obvious that if user wants to run more than one node per
machine it has also set this flag to true explicitly. Maybe it would be
better to set it to true by default?

At the same time if excludeNeighbors is true, it ignores backupFilter.
Why it's not vice-versa? For example:

1) if backupFilter is set - it will be used,

2) if there are not enough backup nodes (or no backupFilter) - try to
distribute according to excludeNeighbors = true,

3) if this is not possible too (or excludeNeighbors) = false - assign
partitions as possible.

[1]

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html#setExcludeNeighbors-boolean-

Are there any drawbacks in such approach?

Thanks!

[jira] [Created] (IGNITE-9011) RendezvousAffinity.excludeNeighbors should be removed and be a default behavior

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-9011:
---

 Summary: RendezvousAffinity.excludeNeighbors should be removed and 
be a default behavior
 Key: IGNITE-9011
 URL: https://issues.apache.org/jira/browse/IGNITE-9011
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.6
Reporter: Dmitry Karachentsev
 Fix For: 3.0


According to this [discussion | 
http://apache-ignite-developers.2346864.n4.nabble.com/Neighbors-exclusion-td32550.html],
 cache backup distribution should be more straightforward. 

Right now we have not obvious logic on how backups will be stored across nodes. 
For example:
1. If set nodeFilter, it will filter backup nodes and if there are not enough 
nodes there will be less backups...
2. If set property excludeNeighbors, it will ignore manually set backupFilter.
3. By default excludeNeighbors is false.

There seems no need to keep excludeNeighbors property at all and it should be 
removed. Instead, node always must do the best to distribute backups to 
different machines.

If user set backupFilter, it must be used, otherwise distribute backups to 
other machines if it's possible.



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

[jira] [Created] (IGNITE-9010) Move web-console build to dedicated root directory

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-9010:


 Summary: Move web-console build to dedicated root directory
 Key: IGNITE-9010
 URL: https://issues.apache.org/jira/browse/IGNITE-9010
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Ilya Murchenko


# Move web-console docker image build (web-console, frontend and backend) to 
{{/docker}} directory.
# Prepare README.md file in root of {{/docker}} directory with instructions on 
how to build corresponding image. Remove obsolete per-image README's from 
Dockerfile directories.



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

[jira] [Created] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment

[Denis Mekhanikov (JIRA)]

Denis Mekhanikov created IGNITE-9009:


 Summary: Local continuous query listeners may be called on 
partition reassignment
 Key: IGNITE-9009
 URL: https://issues.apache.org/jira/browse/IGNITE-9009
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Denis Mekhanikov
Assignee: Denis Mekhanikov
 Fix For: 2.7
 Attachments: ContinuousQueryReassignmentTest.java

When a node becomes primary for some partitions, then local continuous query 
listeners receive updates on entries from that partitions. Such invocations 
shouldn't happen.

Attached test class demonstrates this behaviour.



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

[jira] [Created] (IGNITE-9008) CPP Thin: Implement benchmark for C++ thin

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-9008:
---

 Summary: CPP Thin: Implement benchmark for C++ thin
 Key: IGNITE-9008
 URL: https://issues.apache.org/jira/browse/IGNITE-9008
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.7


We need a benchmark for C++ thin to understand how is its performance compares 
to to other clients.



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

RE: Can .NET thin client have cache expire policy?

[Stanislav Lukyanov]

The same question is being discussed on the user-list:
https://stackoverflow.com/questions/51314852/is-there-a-workaround-to-use-thin-client-with-cache-expiry-policy-in-apache-igni

Stan 

From: Dmitriy Setrakyan
Sent: 16 июля 2018 г. 3:03
To: dev
Cc: Pavel Tupitsyn
Subject: Can .NET thin client have cache expire policy?

This question has been asked of the Stack Overflow:

https://stackoverflow.com/questions/51314852/is-there-a-workaround-to-use-thin-client-with-cache-expiry-policy-in-apache-igni

Would be nice to provide an answer. Pavel, can you respond?

Thanks,
D.

[GitHub] ignite pull request #4364: IGNITE-8783

[anton-vinogradov]

GitHub user anton-vinogradov opened a pull request:

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

IGNITE-8783

Signed-off-by: Anton Vinogradov 

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

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

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

https://github.com/apache/ignite/pull/4364.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 #4364


commit 87acce74295d483e27794aee2c5e1493b665ee2a
Author: Anton Vinogradov 
Date:   2018-07-13T12:38:26Z

IGNITE-8783

Signed-off-by: Anton Vinogradov 




---

[jira] [Created] (IGNITE-9007) cache.invoke() fails because of UnregisteredClassException

[Roman Guseinov (JIRA)]

Roman Guseinov created IGNITE-9007:
--

 Summary: cache.invoke() fails because of 
UnregisteredClassException 
 Key: IGNITE-9007
 URL: https://issues.apache.org/jira/browse/IGNITE-9007
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.5
Reporter: Roman Guseinov
Assignee: Mikhail Cherkasov
 Attachments: ClientNode.java, CustomEnum.java, CustomObj.java, 
Reproducer.java, ServerNode.java

Here is a stack trace:
{code:java}
[2018-07-16 18:07:30,624][ERROR][main][BinaryContext] Failed to serialize 
object [typeName=o.a.i.reproducers.fd7776.CustomObj]
class org.apache.ignite.binary.BinaryObjectException: Failed to write field 
[name=obj]
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor.write(BinaryFieldAccessor.java:159)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:807)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:216)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:157)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:144)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:254)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:402)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:386)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:881)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:831)
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1802)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.runEntryProcessor(GridCacheMapEntry.java:5350)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4705)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4515)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3083)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2977)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1726)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1610)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1306)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:381)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1761)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2436)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1898)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1740)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1630)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1119)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:827)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:787)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1417)
at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCach

Re: MVCC and IgniteDataStreamer

[Ilya Kasnacheev]

Hello!

Can we also bypass WAL for such mode automatically?

However, we will definitely need a 'normal' mode of DataStreamer operation,
for people who use dataStreamer with custom stream transformers on existing
data in use.

Regards,

-- 
Ilya Kasnacheev

2018-07-14 12:33 GMT+03:00 Vladimir Ozerov :

> Igniters,
>
> Denis is right - please pay attention to IEP-22, as this is how we are
> going to load data into the grid in future. Note that current data streamer
> internals are not efficient enough, primarily because it has to interact
> with page memory, free lists and various BTree's in regular manner. I think
> that when IEP-22 is implemented, it will be integrated with data streamer
> tightly, and the most defautl way to load data would be:
> 1) Obtain exclusive table lock
> 2) Load data bypassing almost all Ignite internals
> 3) Re-build indexes
> 4) Release the lock
>
> Normally all types of data load should obey transactional semantics if MVCC
> is enabled, and we should think separately on how to do that for
> continuous-streaming case.
>
> For now let's focus on immediate goal for MVCC release - data streamer
> should work, no new abstractions or APIs should be introduced. The easiest
> way to do this is to agree that streamer is not transactional and use
> special version as Igor proposed. In future releases, when IEP-22 is
> implemented, it become transactional with help of exclusive table lock. In
> more distant releases we will think about separate optimizations for
> continuous streaming and possibly other cases.
>
> Makes sense?
>
> Vladimir.
>
>
> On Fri, Jul 13, 2018 at 11:30 PM Denis Magda  wrote:
>
> > Agree that initial loading and real-time streaming should be seen as
> > different use cases.
> >
> > For the loading part, I would borrow ideas from direct data load IEP [1].
> > Ignite should assume that no app works with the cluster until it's
> > preloaded. So, no global locks or things like that. Just fasten a seat
> belt
> > and feed data to your nodes.
> >
> > For the streaming part, I would consider 2 or 3 proposed by Igor.
> >
> > --
> > Denis
> >
> > [1]
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 22%3A+Direct+Data+Load
> >
> > On Fri, Jul 13, 2018 at 10:03 AM Seliverstov Igor 
> > wrote:
> >
> > > Ivan,
> > >
> > > Anyway DataStreamer is the fastest way to deliver data to a data node,
> > the
> > > question is how to apply it correctly.
> > >
> > > I don’t thing we need one more tool, which 90% is the same as
> > DataStreamer.
> > >
> > > All we need is just to implement a couple of new stream receivers.
> > >
> > > Regards,
> > > Igor
> > >
> > > > 13 июля 2018 г., в 9:56, Павлухин Иван 
> > написал(а):
> > > >
> > > > Hi Igniters,
> > > >
> > > > I had a look into IgniteDataStreamer. As far as I understand,
> currently
> > > it
> > > > just works incorrectly for MVCC tables. It appears as a blocker for
> > > > releasing MVCC. The simplest thing is to refuse creating streamer for
> > > MVCC
> > > > tables.
> > > >
> > > > Next step could be hair splitting of related use cases. For me,
> initial
> > > > load and continuous streaming look quite different cases and it is
> > better
> > > > to keep them separate at least at API level. Perhaps, it is better to
> > > > separate API basing on user experience. For example, DataStreamer
> could
> > > be
> > > > considered tool without surprises (which means leaving data always
> > > > consistent, transactions). And let's say BulkLoader is a beast for
> > > fastest
> > > > data loading but full of surprises. Such surprises could be locking
> > > tables,
> > > > rolling back user transactions and so on. So, it is of very limited
> use
> > > > (like initial load). Keeping API entities separate looks better for
> me
> > > than
> > > > introducing multiple modes, because separated entities are easier for
> > > > understanding and so less prone to user mistakes.
> > > >
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > >
> > >
> >
>

[jira] [Created] (IGNITE-9006) Add per-call tracing capabilities for IgniteCache#{get, getAll} methods

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-9006:


 Summary: Add per-call tracing capabilities for IgniteCache#{get, 
getAll} methods
 Key: IGNITE-9006
 URL: https://issues.apache.org/jira/browse/IGNITE-9006
 Project: Ignite
  Issue Type: New Feature
Affects Versions: 2.6
Reporter: Alexey Goncharuk
 Fix For: 2.7


As an experimental feature to debug objects visibility issues, we should add an 
API method {{IgniteCache#withTrace()}} which will enable per-call API calls 
tracing.

I think we can start with reads tracing, as a simplest change. We need to 
introduce an additional flag mask to {{NearSingleGetRequest}}, 
{{NearGetRequest}}, {{Near...Response}} to identify such requests, and when 
processing, print out all message processing path (send, receive), entry 
swap/unswap, versions and values read, {{GridCacheEntryRemovedException}}s 
encountered, etc. For transactional caches, I think it also makes sense to 
print out all pending transactions that touch the key being read.



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