Re: WAL iterator unexpected behavior

[Dmitriy Govorukhin]

Dmitriy,

Sorry, my mistake, I meant unknown exception of course.

On Sun, Jun 3, 2018 at 11:53 PM, Dmitriy Setrakyan 
wrote:

> I got a bit confused by your initial statement. So, the iterator is stopped
> in case of any exception, known or unknown. In that case, sounds good.
>
> D.
>
> On Sun, Jun 3, 2018, 12:11 Dmitriy Govorukhin <
> dmitriy.govoruk...@gmail.com>
> wrote:
>
> > Dmitriy,
> >
> > The iterator will be stopped. and method "it.next()" will throw the
> > exception.
> >
> > On Sat, Jun 2, 2018 at 4:27 PM, Dmitriy Setrakyan  >
> > wrote:
> >
> > > Dmitriy, what happens in case of unknown exceptions?
> > >
> > >
> > > On Thu, May 31, 2018 at 6:35 AM, Dmitriy Govorukhin <
> > > dmitriy.govoruk...@gmail.com> wrote:
> > >
> > > > Folks,
> > > >
> > > > I created the issue to solve this issue.
> > > >
> > > > IGNITE-8661 
> > > > WALItreater
> > > > is not stopped if can not deserialize record
> > > >
> > > > I suggest to make the following changes:
> > > > 1. We should only stop iteration on known exceptions
> > > > 2. Also, need to provide ability skip records by type or some pointer
> > for
> > > > the StandaloneWalRecordsIterator
> > > >
> > > > Comments are welcome.
> > > >
> > > > On Thu, May 31, 2018 at 12:53 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >
> > > > wrote:
> > > >
> > > > > On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin <
> > > > > dmitriy.govoruk...@gmail.com> wrote:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > I agree that in normal mode we should stop and report that error
> > > > > according.
> > > > > > I prefer to add ability skip records for offline mode.
> > > > > >
> > > > >
> > > > > Sounds good.
> > > > >
> > > >
> > >
> >
>

Re: WAL iterator unexpected behavior

[Dmitriy Setrakyan]

I got a bit confused by your initial statement. So, the iterator is stopped
in case of any exception, known or unknown. In that case, sounds good.

D.

On Sun, Jun 3, 2018, 12:11 Dmitriy Govorukhin 
wrote:

> Dmitriy,
>
> The iterator will be stopped. and method "it.next()" will throw the
> exception.
>
> On Sat, Jun 2, 2018 at 4:27 PM, Dmitriy Setrakyan 
> wrote:
>
> > Dmitriy, what happens in case of unknown exceptions?
> >
> >
> > On Thu, May 31, 2018 at 6:35 AM, Dmitriy Govorukhin <
> > dmitriy.govoruk...@gmail.com> wrote:
> >
> > > Folks,
> > >
> > > I created the issue to solve this issue.
> > >
> > > IGNITE-8661 
> > > WALItreater
> > > is not stopped if can not deserialize record
> > >
> > > I suggest to make the following changes:
> > > 1. We should only stop iteration on known exceptions
> > > 2. Also, need to provide ability skip records by type or some pointer
> for
> > > the StandaloneWalRecordsIterator
> > >
> > > Comments are welcome.
> > >
> > > On Thu, May 31, 2018 at 12:53 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > wrote:
> > >
> > > > On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin <
> > > > dmitriy.govoruk...@gmail.com> wrote:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > I agree that in normal mode we should stop and report that error
> > > > according.
> > > > > I prefer to add ability skip records for offline mode.
> > > > >
> > > >
> > > > Sounds good.
> > > >
> > >
> >
>

Re: WAL iterator unexpected behavior

[Dmitriy Govorukhin]

Dmitriy,

The iterator will be stopped. and method "it.next()" will throw the
exception.

On Sat, Jun 2, 2018 at 4:27 PM, Dmitriy Setrakyan 
wrote:

> Dmitriy, what happens in case of unknown exceptions?
>
>
> On Thu, May 31, 2018 at 6:35 AM, Dmitriy Govorukhin <
> dmitriy.govoruk...@gmail.com> wrote:
>
> > Folks,
> >
> > I created the issue to solve this issue.
> >
> > IGNITE-8661 
> > WALItreater
> > is not stopped if can not deserialize record
> >
> > I suggest to make the following changes:
> > 1. We should only stop iteration on known exceptions
> > 2. Also, need to provide ability skip records by type or some pointer for
> > the StandaloneWalRecordsIterator
> >
> > Comments are welcome.
> >
> > On Thu, May 31, 2018 at 12:53 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin <
> > > dmitriy.govoruk...@gmail.com> wrote:
> > >
> > > > Dmitriy,
> > > >
> > > > I agree that in normal mode we should stop and report that error
> > > according.
> > > > I prefer to add ability skip records for offline mode.
> > > >
> > >
> > > Sounds good.
> > >
> >
>

[GitHub] ignite pull request #4113: Ignite 2.5.2

[Jokser]

GitHub user Jokser opened a pull request:

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

Ignite 2.5.2



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

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

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

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


commit 1cea80d29f4f1c61ed56ad1261b74ed42611bf64
Author: Ilya Lantukh 
Date:   2018-04-06T10:49:10Z

IGNITE-8018 Optimized GridCacheMapEntry initialValue() - Fixes #3686.

Signed-off-by: Alexey Goncharuk 

commit 37fc72542eb6baa8be8b41aecd08a194102d13c1
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 

(cherry picked from commit e491f10)

commit 76e293654e34c927d6c9efc85a12e736b58a21f2
Author: Eduard Shangareev 
Date:   2018-04-06T16:22:07Z

IGNITE-8114 Add fail recovery mechanism to tracking pages - Fixes #3734.

Signed-off-by: dpavlov 

(cherry picked from commit 0829397)

commit 49f11db727febc83297c7f0f5de9e6f98f0197fa
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit 9ad7be2f51b6dcdcdf43fedb298cd4e240f0adab
Author: Ilya Borisov 
Date:   2018-04-09T13:59:32Z

IGNITE-8155 Web Console: Fixed number pattern warning in browser console.

(cherry picked from commit 5d8f570)

commit 4aa56751906e5db7aad025a7193933fa929aae26
Author: Vasiliy Sisko 
Date:   2018-04-09T15:13:21Z

IGNITE-7940 Visor CMD: Added "cache -slp" and "cache -rlp" commands to show 
and reset lost partitions for specified cache.

(cherry picked from commit abfa0f5)

commit cc04c5c70af1bdbba834f73330e73277b60e23fc
Author: Eduard Shangareev 
Date:   2018-04-09T16:15:50Z

IGNITE-8114 Additional fix for Add fail recovery mechanism to tracking pages

(cherry picked from commit 961fc35)

commit c70d85aa36c702ea0f29bd8668e9bf0790f9ba11
Author: Vasiliy Sisko 
Date:   2018-04-10T08:42:24Z

IGNITE-8126 Web Console: Fixed code generation for cache load.

(cherry picked from commit a0a187b)

commit 8d3755b9c58eef12c5fc9cabfc0b1c05f6db716e
Author: Semyon Boikov 
Date:   2018-04-10T08:37:39Z

IGNITE-7222 Added ZooKeeper discovery SPI

commit b096a463c338565a7661f8a853a257518d872997
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

commit 82a4c024fe06ef8c8deeaf762f0cc20a8e481252
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

commit c1745de37891026e0a719f0c1d1afe768dfccbf3
Author: Vasiliy Sisko 
Date:   2018-04-10T10:48:52Z

IGNITE-7927 Web Console: Fixed demo for non-collocated joins.

(cherry picked from commit 647620b)

commit b28287d1861fd841a18d0eef95eff309d21a55ef
Author: Alexey Goncharuk 
Date:   2018-04-10T13:22:28Z

IGNITE-8025 Future must fail if assertion error has been thrown in the 
worker thread

commit a832f2b2e5788c45114c3cb5529d7cf53d08f9a6
Author: Andrey Kuznetsov 
Date:   2018-04-10T14:30:12Z

ignite-7772 System workers critical failures handling

Signed-off-by: Andrey Gura 

commit 912433ba9aa113508d05930691b251eccd8f5870
Author: Aleksey Plekhanov 
Date:   2018-04-10T15:54:03Z

IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly to 
provided failure handler

Signed-off-by: Andrey Gura 

commit 99feab6ace66d011b677fd4d57b44fc54da8fd4f
Author: Alexey Goncharuk 
Date:   2018-04-10T17:33:47Z

IGNITE-6430 Complete failing test early

commit 526fb0ee612ef71fde58a1274db35e8205304a63
Author: Dmitriy Sorokin 
Date:   2018-04-10T19:20:41Z

IGNITE-8101 Ability to terminate system workers by JMX for test purposes.

Signed-off-by: Andrey Gura 

commit b4cb2f0df944534743a9d73811e047eda572258c
Author: mcherkasov 
Date:   2018-04-11T00:27:20Z

IGNITE-8153 Nodes fail to connect each other when SSL is enabled - Fixes 
#3773.

Signed-off-by: Valentin Kulichenko 

commit b4cc9f2d45d78c360abe224165e707c23533469e
Author: Pavel Kovalenko 
Date:   2018-04-11T08:23:46Z

IGNITE-7871 Implemented additional synchronization phase for correct 
partition counters update

commit 9abfee69aa153888456f9e8574ece1f2d0cbe4d9
Author: dmitrievanthony 
Date:   2018-04-10T09:46:43Z

IGNITE-8059: Integrate decision tree 

[GitHub] ignite pull request #4112: IGNITE-7165: check affinity changed

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

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

IGNITE-7165: check affinity changed



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

$ git pull https://github.com/Mmuzaf/ignite mm-fix-7165

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

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


commit ab92cefc8a93462fa68746a3379a9afdc81bea60
Author: Maxim Muzafarov 
Date:   2018-06-03T16:38:17Z

IGNITE-7165: check affinity changed




---

What's new for thin client protocol v1.1.0 vs v1.0.0

[Aleksandr Sokolovskii]

Hi All,

Is there thin client protocol v1.1.0 release notes with summary of changes vs 
v1.0.0?
It’s necessary to update Golang thin client.
I have added TLS and username/password support for connection already.
But I can’t find information about other changes.

Thanks,
Aleksandr

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

[Dmitriy Setrakyan]

Peter,

I think what is really missing is the installation structure, i.e. where is
the bin, config, lib, work folders. Is IGNITE_HOME pointing somewhere as a
result of the installation? I think, if you explain it to users, there will
be more understanding from the user stand point.

Can you please add that?

D.

On Sat, Jun 2, 2018 at 12:39 PM, Petr Ivanov  wrote:

> Dmitriy,
>
>
> I've added warning snippet in the bottom of the Alternative Installation
> Options section with reference on how to start Apache Ignite installed from
> RPM or DEB packages as standalone Java application (see [1]).
> Hope it will be enough.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8671?
> focusedCommentId=16499157=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16499157
>
>
>
>
> > On 2 Jun 2018, at 21:57, Dmitriy Setrakyan 
> wrote:
> >
> > Peter,
> >
> > We cannot have a distribution that works sometimes.
> >
> > I think you should read the ticket carefully. I don't beleive we need to
> > make any changes to the release, it is a matter of fixing the
> > documentation.
> >
> > Can you confirm this?
> >
> > D.
> >
> >
> > On Jun 2, 2018 11:44, "Peter Ivanov"  wrote:
> >
> > Dmitriy,
> >
> >
> > You suggest removing fully working under corresponding Linux distributive
> > RPM and DEB packages entirely from apache.org/dist/ignite only because
> they
> > do not work in highly unlikely scenario (Windows 10 WSL) as service?
> >
> > I will certainly add reference about running Apache Ignite from the
> > packages as standalone Java application (with corresponding permissions
> > note) but I’d like to hear community opinion on the whole matter -
> > everything that was done, was done with review and approve from lots of
> > Apache Ignite commiters and PMCs, including PMC chair.
> >
> >
> > On Sat, 2 Jun 2018 at 16:12, Dmitriy Setrakyan 
> > wrote:
> >
> >
> >> Peter,
> >>
> >> I have reopened this ticket:
> >> https://issues.apache.org/jira/browse/IGNITE-8671
> >>
> >> I changed the priority to blocker. At this point I suggest the
> following:
> >> - we either remove the DEB and RPM packages from the website and readme
> >> - or we fix this issue ASAP as stated in the ticket.
> >>
> >> I will leave it up to you to decide.
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 10:31 PM, Peter Ivanov 
> >> wrote:
> >>
> >>> Dmitriy,
> >>>
> >>>
> >>> SystemD supports running multiple instances of one service – this is
> done
> >>> through @-like syntax: 'sudo systemctl start apache-ignite@
>  >>> file name>', so that with every unique command string there will be
> >>> started
> >>> / stopped unique instance of Apache Ignite. And all instances can be
> >>> restarted / stopped / enabled on boot / etc. simultaneously through
> 'sudo
> >>> systemctl  apache-ignite@*'.
> >>>
> >>> Still, I can add a note about possibility of starting Apache Ignite
> >>> manually through ignite.sh with a reference to corresponding
> > documentation
> >>> section, information where to look for the root of Apache Ignite
> >>> installation and how to correctly start Apache Ignite in terms of
> >>> permissions.
> >>>
> >>> File the documentation updates ticket?
> >>>
> >>>
> >>> On Fri, 1 Jun 2018 at 01:10, Dmitriy Setrakyan 
> >>> wrote:
> >>>
>  Petr,
> 
>  Most of the users will download and install Ignite so they can develop
> >>> with
>  it. This means that they will be starting more than one node, which is
>  impossible if Ignite is a service. We should provide instructions to
> do
>  both.
> 
>  D.
> 
>  On Thu, May 31, 2018 at 2:47 PM, Peter Ivanov 
> >>> wrote:
> 
> > Dmitriy,
> >
> >
> > Current packages design (both RPM and DEB) was reviewed and approved
> >>> by
> > community. I do not quite remember why service-based startup was
> >>> chosen
>  but
> > it seems rather logical and Unix-compliant – under Linux almost every
> > service software is packed this way, which gives some benefits like
>  service
> > autostart on reboot, centralized running nodes management (through
> > systemctl), etc. There is no point in packing binary into Linux
> >>> packages
>  if
> > it then will be used as standalone executable.
> > Yet, current design does not limit advanced user from running Apache
>  Ignite
> > as standalone process – executing
> >>> /usr/share/apache-ignite/bin/ignite.sh
> > with parameters will start Apache Ignite node as if it was delivered
> >>> by
> > binary archive.
> >
> >
> >
> > On Thu, 31 May 2018 at 20:43, Dmitriy Setrakyan <
> >>> dsetrak...@apache.org>
> > wrote:
> >
> >> Petr,
> >>
> >> Why do we even suggest starting Ignite as a service? Why not just
> >>> start
> >> Ignite instance as a stand-alone process? This should work, no?
> >>
> >> D.
> >>
> >> On Thu, May 31, 2018 at 9:30 AM, Petr Ivanov 
> > wrote:
> >>
> >>>