Re: [DISCUSSION] Hot cache backup

[Alexey Goncharuk]

Maxim,

I've left my comments in the PR.

пн, 20 апр. 2020 г. в 12:52, Maxim Muzafarov :

> Alex P,
> Thank you for the great sophisticated review.
>
>
> Alexey G,
> Will you take a look at my changes[1]?
> The fresh TC.Bot visa attached.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-11073
>
> On Mon, 20 Apr 2020 at 11:54, Alex Plehanov 
> wrote:
> >
> > Maxim, I've reviewed your PR and it looks good to me. Good job!
> >
> > пт, 10 апр. 2020 г. в 19:43, Alexey Goncharuk <
> alexey.goncha...@gmail.com>:
> >
> > > Maxim,
> > >
> > > Thanks for raising this PR. I will do a review during next week.
> > >
> > > --AG
> > >
>

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Ivan Bessonov]

Hello, Igniters,

considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
improvement" - it depends
on https://issues.apache.org/jira/browse/IGNITE-12735 and
https://issues.apache.org/jira/browse/IGNITE-12568,
both were targeted to 2.9, but this has to be changed probably.

There might be other issues that I didn't find, we should probably ask
Andrey Gura about it, he is the author of
those changes.

So, release scope should be expanded a little bit, are you ok with it?

пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :

> Hello, Igniters.
>
> I perform cherry-pick for most commits targeted for 2.8.1 release.
>
> TC bot results -
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
>
> I need help with cherry picking the following commits:
>
> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
> GridSecurityProcessor - Fixes #7523.
> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
> full read to unlock the GridH2Table. (#7551)
> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
> #7494.
> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
>
> Denis Garus,
> Taras Ledkov,
> Alexey Plekhanov,
> Ivan Bessonov,
>
> Can you help me with above commits and cherry-pick your contribution in
> ignite-2.8.1 branch?
>
> CHERRY PICKED:
>
> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method which
> must not be used in production code (#7604)
> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
> if function is used (#7615)
> + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
> is in progress. Fixes #7562
> + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
> deployment. (#7620)
> + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
> + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the Timestamp
> and Guid params. (#7618)
> + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
> removed. (#7549)
> + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
> #7516.
> + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
> + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
> client close when partition awareness is enabled - Fixes #7522.
> + e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
> Fixes #7483.
> + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
> + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
> (#7321)
> + 59917f0731 IGNITE-12624 Java thin client: typeId generation for system
> types fixed - Fixes #7416.
> + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can prevent
> late affinity switch. - Fixes #7425.
> + 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused by
> partition reservation (#7251)
> + 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close.
> + 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - Fixes
> #7411.
> + 100101ccce IGNITE-12605: Reset initial update counter value before
> clearing a partition (#7341)
> + e17887bfbf IGNITE-12654 Some of rentingFutures in
> GridDhtPartitionTopologyImpl may accumulate a huge number of eviction
> callbacks - Fixes #7399.
> + bdbe6a79d0 IGNITE-12651 Non-comparable keys for eviction policy cause
> failure handle and node shutdown - Fixes #7397.
> + 56a515db6d IGNITE-12631 Incorrect rewriting wal record type in
> marshalled mode during iteration - Fixes #7371.
> + 14dd160f90 IGNITE-12621 Node leave may cause NullPointerException during
> IO message processing if security is enabled - Fixes #7366.
> + 67ac1d5d68 IGNITE-12636 Full rebalance instead of a historical one -
> Fixes #7379.
> + 4433485d74 IGNTIE-12468 Java thin client: deserialization of arrays,
> collections and maps fixed - Fixes #7320.
> + 0dfd98388e IGNITE-12618 Affinity cache for version of last server event
> can be wiped from history - Fixes #7359.
> + e2c597fff1 IGNITE-12013 NullPointerException is thrown by
> ExchangeLatchManager during cache creation - Fixes #7335.
> + cebc76f1f5d7d077093ddaecbabcd8db2106c60a - IGNITE-12545 Introduce
> listener interface for components to react to partition map exchange events
> + a9278eedf7 IGNITE-11797 Fixed partition consistency issues for atomic
> and mixed tx-atomic cache groups. - Fixes #7315.
> + e160c8f231 IGNITE-12557 Fix possible IgniteOOM during cache destroy. -
> Fixes #7298.
> + 41ed3294ec IGNITE-12567 H2Tree goes into illegal state when non-indexed
> columns are dropped - Fixes #7290.
> + e89c71d3cb IGNITE-12569 Can't set serialized enum to a BinaryObject's
> field - Fixes #7292.
> + 66593af03aeac37d0e76b6c010e8386f6f0c36c7 - IGNITE-12479 Make binary
> metadata be registered only once per type creation
> + 6668d86ad4 IGNITE-12460 Cluster fails to find 

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Nikolay Izhikov]

Igniters.

Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1 
branch?

> 21 апр. 2020 г., в 11:11, Nikolay Izhikov  написал(а):
> 
>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> 
> 
> Thanks!
> 
>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
>>> improvement" - it depends
>>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>>> https://issues.apache.org/jira/browse/IGNITE-12568,
>>> both were targeted to 2.9, but this has to be changed probably.
> 
> IGNITE-12735 - Metric exporter implementation could lead to 
> NullPointerException from gauge which invoke communication
> IGNITE-12568 - MessageFactory implementations refactoring
> 
> Ivan, 
> Personally, I’m against any refactoring improvements in bug fix release.
> So, I propose to exclude IGNITE-12756 from 2.8.1
> 
> Andrey, what do you think as a committer of this improvements?
> 
> 
>> 21 апр. 2020 г., в 10:44, Alex Plehanov  написал(а):
>> 
>> Nikolay,
>> 
>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>> 
>> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
>> 
>>> Hello, Igniters,
>>> 
>>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
>>> improvement" - it depends
>>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>>> https://issues.apache.org/jira/browse/IGNITE-12568,
>>> both were targeted to 2.9, but this has to be changed probably.
>>> 
>>> There might be other issues that I didn't find, we should probably ask
>>> Andrey Gura about it, he is the author of
>>> those changes.
>>> 
>>> So, release scope should be expanded a little bit, are you ok with it?
>>> 
>>> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
>>> 
 Hello, Igniters.
 
 I perform cherry-pick for most commits targeted for 2.8.1 release.
 
 TC bot results -
 
>>> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
 
 I need help with cherry picking the following commits:
 
 - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
 GridSecurityProcessor - Fixes #7523.
 - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
 - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
 full read to unlock the GridH2Table. (#7551)
 - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
 #7494.
 - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
 
 Denis Garus,
 Taras Ledkov,
 Alexey Plekhanov,
 Ivan Bessonov,
 
 Can you help me with above commits and cherry-pick your contribution in
 ignite-2.8.1 branch?
 
 CHERRY PICKED:
 
 + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
>>> which
 must not be used in production code (#7604)
 + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
 if function is used (#7615)
 + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
 is in progress. Fixes #7562
 + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
 deployment. (#7620)
 + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
 + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
>>> Timestamp
 and Guid params. (#7618)
 + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
 removed. (#7549)
 + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
 #7516.
 + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
 + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
 client close when partition awareness is enabled - Fixes #7522.
 + e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
 Fixes #7483.
 + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
 + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
 (#7321)
 + 59917f0731 IGNITE-12624 Java thin client: typeId generation for system
 types fixed - Fixes #7416.
 + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can prevent
 late affinity switch. - Fixes #7425.
 + 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused by
 partition reservation (#7251)
 + 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close.
 + 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - Fixes
 #7411.
 + 100101ccce IGNITE-12605: Reset initial update counter value before
 clearing a partition (#7341)
 + e17887bfbf IGNITE-12654 Some of rentingFutures in
 GridDhtPartitionTopologyImpl may accumulate a huge number of eviction
 callbacks - Fixes #7399.
 + bdbe6a79d0 IGNITE-12651 Non-comparable keys for eviction policy cause
 failure handle and node shutdown - Fixes #7397.
 + 56a515db6d IGNITE-12631 Incorrect rewriting wal record 

[jira] [Created] (IGNITE-12925) Flaky test SystemViewSelfTest.testContinuousQuery.

[Mikhail Petrov (Jira)]

Mikhail Petrov created IGNITE-12925:
---

 Summary: Flaky test SystemViewSelfTest.testContinuousQuery.
 Key: IGNITE-12925
 URL: https://issues.apache.org/jira/browse/IGNITE-12925
 Project: Ignite
  Issue Type: Test
Reporter: Mikhail Petrov


It is needed to fix SystemViewSelfTest.testContinuousQuery test, which is flaky 
– [TC 
history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2075278944640125900=testDetails_IgniteTests24Java8=pull%2F7696%2Fhead].

It seems that QueryCursor#close method 
 gives no guarantees that CQ routine will be cleared from all nodes before its 
returning. This behavior is due to StopRoutineDiscoveryMessage is immutable and 
so StopRoutineAckDiscoveryMessage can be received (QueryCoursor#close method 
returns) before GridContinuousProcessor#processStopRequest completion on all 
nodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Nikolay Izhikov]

> I've cherry-picked IGNITE-12734 to 2.8.1 branch.


Thanks!

>  considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
>> improvement" - it depends
>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>> https://issues.apache.org/jira/browse/IGNITE-12568,
>> both were targeted to 2.9, but this has to be changed probably.

IGNITE-12735 - Metric exporter implementation could lead to 
NullPointerException from gauge which invoke communication
IGNITE-12568 - MessageFactory implementations refactoring

Ivan, 
Personally, I’m against any refactoring improvements in bug fix release.
So, I propose to exclude IGNITE-12756 from 2.8.1

Andrey, what do you think as a committer of this improvements?


> 21 апр. 2020 г., в 10:44, Alex Plehanov  написал(а):
> 
> Nikolay,
> 
> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> 
> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> 
>> Hello, Igniters,
>> 
>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
>> improvement" - it depends
>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>> https://issues.apache.org/jira/browse/IGNITE-12568,
>> both were targeted to 2.9, but this has to be changed probably.
>> 
>> There might be other issues that I didn't find, we should probably ask
>> Andrey Gura about it, he is the author of
>> those changes.
>> 
>> So, release scope should be expanded a little bit, are you ok with it?
>> 
>> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
>> 
>>> Hello, Igniters.
>>> 
>>> I perform cherry-pick for most commits targeted for 2.8.1 release.
>>> 
>>> TC bot results -
>>> 
>> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
>>> 
>>> I need help with cherry picking the following commits:
>>> 
>>> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
>>> GridSecurityProcessor - Fixes #7523.
>>> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
>>> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
>>> full read to unlock the GridH2Table. (#7551)
>>> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
>>> #7494.
>>> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
>>> 
>>> Denis Garus,
>>> Taras Ledkov,
>>> Alexey Plekhanov,
>>> Ivan Bessonov,
>>> 
>>> Can you help me with above commits and cherry-pick your contribution in
>>> ignite-2.8.1 branch?
>>> 
>>> CHERRY PICKED:
>>> 
>>> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
>> which
>>> must not be used in production code (#7604)
>>> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
>>> if function is used (#7615)
>>> + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
>>> is in progress. Fixes #7562
>>> + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
>>> deployment. (#7620)
>>> + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
>>> + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
>> Timestamp
>>> and Guid params. (#7618)
>>> + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
>>> removed. (#7549)
>>> + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
>>> #7516.
>>> + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
>>> + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
>>> client close when partition awareness is enabled - Fixes #7522.
>>> + e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
>>> Fixes #7483.
>>> + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
>>> + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
>>> (#7321)
>>> + 59917f0731 IGNITE-12624 Java thin client: typeId generation for system
>>> types fixed - Fixes #7416.
>>> + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can prevent
>>> late affinity switch. - Fixes #7425.
>>> + 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused by
>>> partition reservation (#7251)
>>> + 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close.
>>> + 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - Fixes
>>> #7411.
>>> + 100101ccce IGNITE-12605: Reset initial update counter value before
>>> clearing a partition (#7341)
>>> + e17887bfbf IGNITE-12654 Some of rentingFutures in
>>> GridDhtPartitionTopologyImpl may accumulate a huge number of eviction
>>> callbacks - Fixes #7399.
>>> + bdbe6a79d0 IGNITE-12651 Non-comparable keys for eviction policy cause
>>> failure handle and node shutdown - Fixes #7397.
>>> + 56a515db6d IGNITE-12631 Incorrect rewriting wal record type in
>>> marshalled mode during iteration - Fixes #7371.
>>> + 14dd160f90 IGNITE-12621 Node leave may cause NullPointerException
>> during
>>> IO message processing if security is enabled - Fixes #7366.
>>> + 67ac1d5d68 IGNITE-12636 Full rebalance instead of a historical one -
>>> Fixes 

Moving python, php and node.js in separate repos and release cycles

[Igor Sapego]

Guys,

It was discussed on the dev list a few times that it would be a good
idea to move Python, Node.js and PHP thin clients to separate repos
and separate release cycles.

In short there are several arguments for that:

1. There are no dependencies on the core functionality so there is simply
no need for them to be in the main repo.

2. Those thin clients often do not get updates from release to release, but
still
we "release" them, as they are a part of the main release.

3. Moving them to a separate release cycle will allow us to release some hot
fixes for those clients faster and easier.

4. Composer needs a PHP packet that is released to be in a separate
repository.

Thoughts?

Best Regards,
Igor

Re: [jira] [评论] (IGNITE-12852) Comma in field is not supported by COPY command

[18624049226]

Hi community,

if someone can help to merge this patch into repo(2.8.1)?

在 2020/4/17 下午4:52, Roman Kondakov (Jira) 写道:

Message Title
	Roman Kondakov 
 
*在故障 IGNITE-12852 
上评论*


重新发送: Comma in field is not supported by COPY command 



Nikolay Izhikov 
 the 
patch looks good to me.


添加评论  
添加评论 


这条信息是由Atlassian Jira发送的 (v8.3.4#803005-sha1:1f96e09)
Atlassian logo

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Alex Plehanov]

Nikolay,

I've cherry-picked IGNITE-12734 to 2.8.1 branch.

вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :

> Hello, Igniters,
>
> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> improvement" - it depends
> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> https://issues.apache.org/jira/browse/IGNITE-12568,
> both were targeted to 2.9, but this has to be changed probably.
>
> There might be other issues that I didn't find, we should probably ask
> Andrey Gura about it, he is the author of
> those changes.
>
> So, release scope should be expanded a little bit, are you ok with it?
>
> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > I perform cherry-pick for most commits targeted for 2.8.1 release.
> >
> > TC bot results -
> >
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
> >
> > I need help with cherry picking the following commits:
> >
> > - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
> > GridSecurityProcessor - Fixes #7523.
> > - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
> > - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
> > full read to unlock the GridH2Table. (#7551)
> > - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
> > #7494.
> > - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
> >
> > Denis Garus,
> > Taras Ledkov,
> > Alexey Plekhanov,
> > Ivan Bessonov,
> >
> > Can you help me with above commits and cherry-pick your contribution in
> > ignite-2.8.1 branch?
> >
> > CHERRY PICKED:
> >
> > + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
> which
> > must not be used in production code (#7604)
> > + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
> > if function is used (#7615)
> > + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
> > is in progress. Fixes #7562
> > + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
> > deployment. (#7620)
> > + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
> > + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
> Timestamp
> > and Guid params. (#7618)
> > + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
> > removed. (#7549)
> > + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
> > #7516.
> > + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
> > + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
> > client close when partition awareness is enabled - Fixes #7522.
> > + e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
> > Fixes #7483.
> > + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
> > + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
> > (#7321)
> > + 59917f0731 IGNITE-12624 Java thin client: typeId generation for system
> > types fixed - Fixes #7416.
> > + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can prevent
> > late affinity switch. - Fixes #7425.
> > + 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused by
> > partition reservation (#7251)
> > + 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close.
> > + 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - Fixes
> > #7411.
> > + 100101ccce IGNITE-12605: Reset initial update counter value before
> > clearing a partition (#7341)
> > + e17887bfbf IGNITE-12654 Some of rentingFutures in
> > GridDhtPartitionTopologyImpl may accumulate a huge number of eviction
> > callbacks - Fixes #7399.
> > + bdbe6a79d0 IGNITE-12651 Non-comparable keys for eviction policy cause
> > failure handle and node shutdown - Fixes #7397.
> > + 56a515db6d IGNITE-12631 Incorrect rewriting wal record type in
> > marshalled mode during iteration - Fixes #7371.
> > + 14dd160f90 IGNITE-12621 Node leave may cause NullPointerException
> during
> > IO message processing if security is enabled - Fixes #7366.
> > + 67ac1d5d68 IGNITE-12636 Full rebalance instead of a historical one -
> > Fixes #7379.
> > + 4433485d74 IGNTIE-12468 Java thin client: deserialization of arrays,
> > collections and maps fixed - Fixes #7320.
> > + 0dfd98388e IGNITE-12618 Affinity cache for version of last server event
> > can be wiped from history - Fixes #7359.
> > + e2c597fff1 IGNITE-12013 NullPointerException is thrown by
> > ExchangeLatchManager during cache creation - Fixes #7335.
> > + cebc76f1f5d7d077093ddaecbabcd8db2106c60a - IGNITE-12545 Introduce
> > listener interface for components to react to partition map exchange
> events
> > + a9278eedf7 IGNITE-11797 Fixed partition consistency issues for atomic
> > and mixed tx-atomic cache groups. - Fixes #7315.
> > + e160c8f231 IGNITE-12557 Fix possible IgniteOOM during cache destroy. -
> > Fixes #7298.
> > + 41ed3294ec IGNITE-12567 H2Tree goes into illegal state when 

[jira] [Created] (IGNITE-12924) [ignite-extensions] Unused import breaks checkstyle

[Nikolay Izhikov (Jira)]

Nikolay Izhikov created IGNITE-12924:


 Summary: [ignite-extensions] Unused import breaks checkstyle 
 Key: IGNITE-12924
 URL: https://issues.apache.org/jira/browse/IGNITE-12924
 Project: Ignite
  Issue Type: Test
Reporter: Nikolay Izhikov


{noformat}
[INFO] --- maven-checkstyle-plugin:3.0.0:check (style) @ ignite-flume-ext ---
[INFO] Starting audit...
[ERROR] 
/Users/sbt-izhikov-nv/src/ignite-extensions/modules/flume-ext/src/main/java/org/apache/ignite/stream/flume/IgniteSink.java:32:8:
 Unused import - org.apache.ignite.IgniteIllegalStateException. [UnusedImports]
Audit done.
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ignite-flink-ext 1.0.0-SNAPSHOT  SUCCESS [  7.202 s]
[INFO] ignite-flume-ext 1.0.0-SNAPSHOT  FAILURE [  0.390 s]
[INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
[INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT  SKIPPED
[INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
[INFO] apache-ignite-extensions 1.0.0-SNAPSHOT  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  8.169 s
[INFO] Finished at: 2020-04-21T11:47:45+03:00
[INFO] 
[WARNING] The requested profile "lgpl" could not be activated because it does 
not exist.
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (style) on project 
ignite-flume-ext: Failed during checkstyle execution: There is 1 error reported 
by Checkstyle 8.19 with ../checkstyle/checkstyle.xml ruleset. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :ignite-flume-ext

{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Nikolay Izhikov]

OK then, let’s include it in the 2.8.1

Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain 
cherry-pick for all required commits?

> 21 апр. 2020 г., в 17:01, Andrey Gura  написал(а):
> 
> Hi
> 
>> IGNITE-12735 - Metric exporter implementation could lead to 
>> NullPointerException from gauge which invoke communication
>> IGNITE-12568 - MessageFactory implementations refactoring
> 
>> Personally, I’m against any refactoring improvements in bug fix release.
>> So, I propose to exclude IGNITE-12756 from 2.8.1
> 
>> Andrey, what do you think as a committer of this improvements?
> 
> Mainly IGNITE-12756 brings some improvements related with TCP
> communication metrics (performance, memory footprint, IgniteSpiContext
> improved in order to provide ability to implement metrics related
> SPI's without using internal API's, code improvements)
> 
> But! It also fixes potential NPE's which can be thrown on node start.
> So it would be great to include this fix to 2.8.1 release.
> 
> On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov  wrote:
>> 
>>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>> 
>> 
>> Thanks!
>> 
>>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
 improvement" - it depends
 on https://issues.apache.org/jira/browse/IGNITE-12735 and
 https://issues.apache.org/jira/browse/IGNITE-12568,
 both were targeted to 2.9, but this has to be changed probably.
>> 
>> IGNITE-12735 - Metric exporter implementation could lead to 
>> NullPointerException from gauge which invoke communication
>> IGNITE-12568 - MessageFactory implementations refactoring
>> 
>> Ivan,
>> Personally, I’m against any refactoring improvements in bug fix release.
>> So, I propose to exclude IGNITE-12756 from 2.8.1
>> 
>> Andrey, what do you think as a committer of this improvements?
>> 
>> 
>>> 21 апр. 2020 г., в 10:44, Alex Plehanov  
>>> написал(а):
>>> 
>>> Nikolay,
>>> 
>>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>>> 
>>> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
>>> 
 Hello, Igniters,
 
 considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
 improvement" - it depends
 on https://issues.apache.org/jira/browse/IGNITE-12735 and
 https://issues.apache.org/jira/browse/IGNITE-12568,
 both were targeted to 2.9, but this has to be changed probably.
 
 There might be other issues that I didn't find, we should probably ask
 Andrey Gura about it, he is the author of
 those changes.
 
 So, release scope should be expanded a little bit, are you ok with it?
 
 пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
 
> Hello, Igniters.
> 
> I perform cherry-pick for most commits targeted for 2.8.1 release.
> 
> TC bot results -
> 
 https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
> 
> I need help with cherry picking the following commits:
> 
> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
> GridSecurityProcessor - Fixes #7523.
> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
> full read to unlock the GridH2Table. (#7551)
> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
> #7494.
> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
> 
> Denis Garus,
> Taras Ledkov,
> Alexey Plekhanov,
> Ivan Bessonov,
> 
> Can you help me with above commits and cherry-pick your contribution in
> ignite-2.8.1 branch?
> 
> CHERRY PICKED:
> 
> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
 which
> must not be used in production code (#7604)
> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
> if function is used (#7615)
> + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
> is in progress. Fixes #7562
> + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
> deployment. (#7620)
> + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
> + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
 Timestamp
> and Guid params. (#7618)
> + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
> removed. (#7549)
> + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
> #7516.
> + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
> + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
> client close when partition awareness is enabled - Fixes #7522.
> + e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
> Fixes #7483.
> + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
> + f32b44deb1 IGNITE-12590: Fix 

Re: Moving python, php and node.js in separate repos and release cycles

[Nikolay Izhikov]

What about dotnet and cpp thin clients?

> 21 апр. 2020 г., в 16:19, Dmitriy Pavlov  написал(а):
> 
> +1 since
> - Simpler release may allow us to release more often
> - Often releases - users will get updates faster, more chances to grow and
> keep our user base
> - Faster updates and easy to get next update may have positive effect on
> community growth. Since newcomer may want to fix a bug and later use result
> in his/her production environment.
> 
> вт, 21 апр. 2020 г. в 13:27, Alexey Zinoviev :
> 
>> Agree with these non-JVM languages.
>> Especially for Python:)
>> 
>> вт, 21 апр. 2020 г. в 12:58, Igor Sapego :
>> 
>>> Guys,
>>> 
>>> It was discussed on the dev list a few times that it would be a good
>>> idea to move Python, Node.js and PHP thin clients to separate repos
>>> and separate release cycles.
>>> 
>>> In short there are several arguments for that:
>>> 
>>> 1. There are no dependencies on the core functionality so there is simply
>>> no need for them to be in the main repo.
>>> 
>>> 2. Those thin clients often do not get updates from release to release,
>> but
>>> still
>>> we "release" them, as they are a part of the main release.
>>> 
>>> 3. Moving them to a separate release cycle will allow us to release some
>>> hot
>>> fixes for those clients faster and easier.
>>> 
>>> 4. Composer needs a PHP packet that is released to be in a separate
>>> repository.
>>> 
>>> Thoughts?
>>> 
>>> Best Regards,
>>> Igor
>>> 
>> 

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Andrey Gura]

Hi

> IGNITE-12735 - Metric exporter implementation could lead to 
> NullPointerException from gauge which invoke communication
> IGNITE-12568 - MessageFactory implementations refactoring

> Personally, I’m against any refactoring improvements in bug fix release.
> So, I propose to exclude IGNITE-12756 from 2.8.1

> Andrey, what do you think as a committer of this improvements?

Mainly IGNITE-12756 brings some improvements related with TCP
communication metrics (performance, memory footprint, IgniteSpiContext
improved in order to provide ability to implement metrics related
SPI's without using internal API's, code improvements)

But! It also fixes potential NPE's which can be thrown on node start.
So it would be great to include this fix to 2.8.1 release.

On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov  wrote:
>
> > I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>
>
> Thanks!
>
> >  considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> >> improvement" - it depends
> >> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> >> https://issues.apache.org/jira/browse/IGNITE-12568,
> >> both were targeted to 2.9, but this has to be changed probably.
>
> IGNITE-12735 - Metric exporter implementation could lead to 
> NullPointerException from gauge which invoke communication
> IGNITE-12568 - MessageFactory implementations refactoring
>
> Ivan,
> Personally, I’m against any refactoring improvements in bug fix release.
> So, I propose to exclude IGNITE-12756 from 2.8.1
>
> Andrey, what do you think as a committer of this improvements?
>
>
> > 21 апр. 2020 г., в 10:44, Alex Plehanov  
> > написал(а):
> >
> > Nikolay,
> >
> > I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> >
> > вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> >
> >> Hello, Igniters,
> >>
> >> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> >> improvement" - it depends
> >> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> >> https://issues.apache.org/jira/browse/IGNITE-12568,
> >> both were targeted to 2.9, but this has to be changed probably.
> >>
> >> There might be other issues that I didn't find, we should probably ask
> >> Andrey Gura about it, he is the author of
> >> those changes.
> >>
> >> So, release scope should be expanded a little bit, are you ok with it?
> >>
> >> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
> >>
> >>> Hello, Igniters.
> >>>
> >>> I perform cherry-pick for most commits targeted for 2.8.1 release.
> >>>
> >>> TC bot results -
> >>>
> >> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
> >>>
> >>> I need help with cherry picking the following commits:
> >>>
> >>> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
> >>> GridSecurityProcessor - Fixes #7523.
> >>> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
> >>> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
> >>> full read to unlock the GridH2Table. (#7551)
> >>> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
> >>> #7494.
> >>> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
> >>>
> >>> Denis Garus,
> >>> Taras Ledkov,
> >>> Alexey Plekhanov,
> >>> Ivan Bessonov,
> >>>
> >>> Can you help me with above commits and cherry-pick your contribution in
> >>> ignite-2.8.1 branch?
> >>>
> >>> CHERRY PICKED:
> >>>
> >>> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
> >> which
> >>> must not be used in production code (#7604)
> >>> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
> >>> if function is used (#7615)
> >>> + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
> >>> is in progress. Fixes #7562
> >>> + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
> >>> deployment. (#7620)
> >>> + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
> >>> + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
> >> Timestamp
> >>> and Guid params. (#7618)
> >>> + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
> >>> removed. (#7549)
> >>> + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
> >>> #7516.
> >>> + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
> >>> + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
> >>> client close when partition awareness is enabled - Fixes #7522.
> >>> + e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
> >>> Fixes #7483.
> >>> + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
> >>> + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
> >>> (#7321)
> >>> + 59917f0731 IGNITE-12624 Java thin client: typeId generation for system
> >>> types fixed - Fixes #7416.
> >>> + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can prevent
> >>> late affinity switch. - Fixes #7425.
> >>> 

Re: Moving python, php and node.js in separate repos and release cycles

[Dmitriy Pavlov]

+1 since
- Simpler release may allow us to release more often
- Often releases - users will get updates faster, more chances to grow and
keep our user base
- Faster updates and easy to get next update may have positive effect on
community growth. Since newcomer may want to fix a bug and later use result
in his/her production environment.

вт, 21 апр. 2020 г. в 13:27, Alexey Zinoviev :

> Agree with these non-JVM languages.
> Especially for Python:)
>
> вт, 21 апр. 2020 г. в 12:58, Igor Sapego :
>
> > Guys,
> >
> > It was discussed on the dev list a few times that it would be a good
> > idea to move Python, Node.js and PHP thin clients to separate repos
> > and separate release cycles.
> >
> > In short there are several arguments for that:
> >
> > 1. There are no dependencies on the core functionality so there is simply
> > no need for them to be in the main repo.
> >
> > 2. Those thin clients often do not get updates from release to release,
> but
> > still
> > we "release" them, as they are a part of the main release.
> >
> > 3. Moving them to a separate release cycle will allow us to release some
> > hot
> > fixes for those clients faster and easier.
> >
> > 4. Composer needs a PHP packet that is released to be in a separate
> > repository.
> >
> > Thoughts?
> >
> > Best Regards,
> > Igor
> >
>

[jira] [Created] (IGNITE-12926) [ignite-extensions] build failed

[Nikolay Izhikov (Jira)]

Nikolay Izhikov created IGNITE-12926:


 Summary: [ignite-extensions] build failed
 Key: IGNITE-12926
 URL: https://issues.apache.org/jira/browse/IGNITE-12926
 Project: Ignite
  Issue Type: Test
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov


The current master in ignite-extension can't be built.

The reason in parent pom.xml which contains 
org.apache.ignite:ignite-tools:1.0-SNAPSHOT dependency for Javadoc plugin.

The version has taken from the project version.

{noformat}

org.apache.maven.plugins
maven-javadoc-plugin
${maven.javadoc.plugin.version}




org.apache.ignite.tools.javadoc.IgniteLinkTaglet

org.apache.ignite
ignite-tools
${project.version}



Ignite ${project.version}
Ignite ${project.version}
true
true
protected
true
false
false
${javadoc.opts}
{noformat}

{noformat}
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ignite-flink-ext 1.0.0-SNAPSHOT  FAILURE [  5.227 s]
[INFO] ignite-flume-ext 1.0.0-SNAPSHOT  SKIPPED
[INFO] ignite-pub-sub 2.9.0-SNAPSHOT .. SKIPPED
[INFO] ignite-spring-boot-autoconfigure 1.0.0-SNAPSHOT  SKIPPED
[INFO] ignite-client-spring-boot-autoconfigure 1.0.0-SNAPSHOT SKIPPED
[INFO] ignite-zeromq-ext 1.0.0-SNAPSHOT ... SKIPPED
[INFO] apache-ignite-extensions 1.0.0-SNAPSHOT  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  5.812 s
[INFO] Finished at: 2020-04-21T13:56:20+03:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:jar (module-javadoc) on 
project ignite-flink-ext: MavenReportException: Error while generating Javadoc: 
Unable to find artifact:groupId = 'org.apache.ignite'
[ERROR] artifactId = 'ignite-tools'
[ERROR] version = '1.0.0-SNAPSHOT': Failure to find 
org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT in 
https://h2database.com/m2-repo was cached in the local repository, resolution 
will not be reattempted until the update interval of h2database.com has elapsed 
or updates are forced
[ERROR] 
[ERROR]   org.apache.ignite:ignite-tools:pom:1.0.0-SNAPSHOT
[ERROR] 
[ERROR] from the specified remote repositories:
[ERROR]   h2database.com (https://h2database.com/m2-repo, releases=false, 
snapshots=true),
[ERROR]   apache.snapshots (http://repository.apache.org/snapshots, 
releases=false, snapshots=true),
[ERROR]   central (https://repo.maven.apache.org/maven2, releases=true, 
snapshots=false)
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Moving python, php and node.js in separate repos and release cycles

[Alexey Zinoviev]

Agree with these non-JVM languages.
Especially for Python:)

вт, 21 апр. 2020 г. в 12:58, Igor Sapego :

> Guys,
>
> It was discussed on the dev list a few times that it would be a good
> idea to move Python, Node.js and PHP thin clients to separate repos
> and separate release cycles.
>
> In short there are several arguments for that:
>
> 1. There are no dependencies on the core functionality so there is simply
> no need for them to be in the main repo.
>
> 2. Those thin clients often do not get updates from release to release, but
> still
> we "release" them, as they are a part of the main release.
>
> 3. Moving them to a separate release cycle will allow us to release some
> hot
> fixes for those clients faster and easier.
>
> 4. Composer needs a PHP packet that is released to be in a separate
> repository.
>
> Thoughts?
>
> Best Regards,
> Igor
>

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Taras Ledkov]

Hi,

Nikolay, i've created PR [1] that contains the SQL-related tickets to 
port into 2.8.1:
- IGNITE-12790 Introduce distributed SQL configuration and ability to 
disable SQL functions.
- IGNITE-12887 Fix handle type mismatch exception on compare values 
while traversing index tree.

- IGNITE-12848 fix H2Connection leaks on INSERT
- IGNITE-12800  SQL: local queries cursors must be closed or full read 
to unlock the GridH2Table.

- IGNITE-12067 User SQL query execution metrics
- IGNITE-12732 Fix for KILL QUERY command hanging.
- IGNITE-12609: SQL: GridReduceQueryExecutor refactoring.
- IGNITE-12444: SQL: Query reduce can fail with NPE on retry.

Wait to TC results and visa from TC bot.

[1]. https://github.com/apache/ignite/pull/7703

On 21.04.2020 12:52, Nikolay Izhikov wrote:

Igniters.

Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1 
branch?


21 апр. 2020 г., в 11:11, Nikolay Izhikov  написал(а):


I've cherry-picked IGNITE-12734 to 2.8.1 branch.


Thanks!


considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics

improvement" - it depends
on https://issues.apache.org/jira/browse/IGNITE-12735 and
https://issues.apache.org/jira/browse/IGNITE-12568,
both were targeted to 2.9, but this has to be changed probably.

IGNITE-12735 - Metric exporter implementation could lead to 
NullPointerException from gauge which invoke communication
IGNITE-12568 - MessageFactory implementations refactoring

Ivan,
Personally, I’m against any refactoring improvements in bug fix release.
So, I propose to exclude IGNITE-12756 from 2.8.1

Andrey, what do you think as a committer of this improvements?



21 апр. 2020 г., в 10:44, Alex Plehanov  написал(а):

Nikolay,

I've cherry-picked IGNITE-12734 to 2.8.1 branch.

вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :


Hello, Igniters,

considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
improvement" - it depends
on https://issues.apache.org/jira/browse/IGNITE-12735 and
https://issues.apache.org/jira/browse/IGNITE-12568,
both were targeted to 2.9, but this has to be changed probably.

There might be other issues that I didn't find, we should probably ask
Andrey Gura about it, he is the author of
those changes.

So, release scope should be expanded a little bit, are you ok with it?

пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :


Hello, Igniters.

I perform cherry-pick for most commits targeted for 2.8.1 release.

TC bot results -


https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead

I need help with cherry picking the following commits:

- 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
GridSecurityProcessor - Fixes #7523.
- 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
- 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
full read to unlock the GridH2Table. (#7551)
- bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
#7494.
- 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement

Denis Garus,
Taras Ledkov,
Alexey Plekhanov,
Ivan Bessonov,

Can you help me with above commits and cherry-pick your contribution in
ignite-2.8.1 branch?

CHERRY PICKED:

+ d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method

which

must not be used in production code (#7604)
+ 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
if function is used (#7615)
+ b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
is in progress. Fixes #7562
+ f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
deployment. (#7620)
+ 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
+ 2b1d2b4dec IGNITE-12859: Support of .Net service call with the

Timestamp

and Guid params. (#7618)
+ 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
removed. (#7549)
+ 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
#7516.
+ 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
+ ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
client close when partition awareness is enabled - Fixes #7522.
+ e389bb8f55 IGNITE-12728 Collect time statistics on cache#putAllAsync -
Fixes #7483.
+ 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
+ f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
(#7321)
+ 59917f0731 IGNITE-12624 Java thin client: typeId generation for system
types fixed - Fixes #7416.
+ cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can prevent
late affinity switch. - Fixes #7425.
+ 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused by
partition reservation (#7251)
+ 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close.
+ 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. - Fixes
#7411.
+ 100101ccce IGNITE-12605: Reset initial update counter value before
clearing a partition (#7341)
+ e17887bfbf 

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Nikolay Izhikov]

Taras,

Great news! Thank you!
Let me know, when you got the visa.

> 21 апр. 2020 г., в 14:02, Taras Ledkov  написал(а):
> 
> Hi,
> 
> Nikolay, i've created PR [1] that contains the SQL-related tickets to port 
> into 2.8.1:
> - IGNITE-12790 Introduce distributed SQL configuration and ability to disable 
> SQL functions.
> - IGNITE-12887 Fix handle type mismatch exception on compare values while 
> traversing index tree.
> - IGNITE-12848 fix H2Connection leaks on INSERT
> - IGNITE-12800  SQL: local queries cursors must be closed or full read to 
> unlock the GridH2Table.
> - IGNITE-12067 User SQL query execution metrics
> - IGNITE-12732 Fix for KILL QUERY command hanging.
> - IGNITE-12609: SQL: GridReduceQueryExecutor refactoring.
> - IGNITE-12444: SQL: Query reduce can fail with NPE on retry.
> 
> Wait to TC results and visa from TC bot.
> 
> [1]. https://github.com/apache/ignite/pull/7703
> 
> On 21.04.2020 12:52, Nikolay Izhikov wrote:
>> Igniters.
>> 
>> Can someone from Grid Gain help me with setup TC bot to monitor ignite-2.8.1 
>> branch?
>> 
>>> 21 апр. 2020 г., в 11:11, Nikolay Izhikov  
>>> написал(а):
>>> 
 I've cherry-picked IGNITE-12734 to 2.8.1 branch.
>>> 
>>> Thanks!
>>> 
 considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> improvement" - it depends
> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> https://issues.apache.org/jira/browse/IGNITE-12568,
> both were targeted to 2.9, but this has to be changed probably.
>>> IGNITE-12735 - Metric exporter implementation could lead to 
>>> NullPointerException from gauge which invoke communication
>>> IGNITE-12568 - MessageFactory implementations refactoring
>>> 
>>> Ivan,
>>> Personally, I’m against any refactoring improvements in bug fix release.
>>> So, I propose to exclude IGNITE-12756 from 2.8.1
>>> 
>>> Andrey, what do you think as a committer of this improvements?
>>> 
>>> 
 21 апр. 2020 г., в 10:44, Alex Plehanov  
 написал(а):
 
 Nikolay,
 
 I've cherry-picked IGNITE-12734 to 2.8.1 branch.
 
 вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
 
> Hello, Igniters,
> 
> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> improvement" - it depends
> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> https://issues.apache.org/jira/browse/IGNITE-12568,
> both were targeted to 2.9, but this has to be changed probably.
> 
> There might be other issues that I didn't find, we should probably ask
> Andrey Gura about it, he is the author of
> those changes.
> 
> So, release scope should be expanded a little bit, are you ok with it?
> 
> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
> 
>> Hello, Igniters.
>> 
>> I perform cherry-pick for most commits targeted for 2.8.1 release.
>> 
>> TC bot results -
>> 
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
>> I need help with cherry picking the following commits:
>> 
>> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
>> GridSecurityProcessor - Fixes #7523.
>> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
>> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed or
>> full read to unlock the GridH2Table. (#7551)
>> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition - Fixes
>> #7494.
>> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
>> 
>> Denis Garus,
>> Taras Ledkov,
>> Alexey Plekhanov,
>> Ivan Bessonov,
>> 
>> Can you help me with above commits and cherry-pick your contribution in
>> ignite-2.8.1 branch?
>> 
>> CHERRY PICKED:
>> 
>> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
> which
>> must not be used in production code (#7604)
>> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails BatchUpdateException
>> if function is used (#7615)
>> + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory restore
>> is in progress. Fixes #7562
>> + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
>> deployment. (#7620)
>> + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
>> + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
> Timestamp
>> and Guid params. (#7618)
>> + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
>> removed. (#7549)
>> + 795617fc94 IGNITE-12774 Handle "Too many open files" exception - Fixes
>> #7516.
>> + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
>> + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
>> client close when partition awareness is enabled - Fixes #7522.
>> + e389bb8f55 IGNITE-12728 Collect time statistics on 

Why OPTIMIZE_REUSE_RESULT is set to 0 explicitly in o.a.i.i.p.query.h2.ConnectionManager#DEFAULT_DB_OPTIONS

[Ivan Daschinskiy]

Hello folks.

Recently I trying to investigate why when the query, i.e. «SELECT * FROM T1 
WHERE ID IN (SELECT T1_ID FROM T2), is executed locally,
subquery evaluated, even if result is the same. I noticed, that in mentioned in 
subj (.ConnectionManager#DEFAULT_DB_OPTIONS),
parameter OPTIMIZE_REUSE_RESULT explicitly set to 0. This value disable 
internal H2 optimization (see details here org.h2.command.dml.Query#query(int, 
org.h2.result.ResultTarget) and lead the mentioned above query to be 
ineffective.

I cannot understand why this decision was made. Also I don’t find any evidence 
that setting OPTIMIZE_REUSE_RESULT to 1 could break something. Unfortunatelly, 
it is impossible to change this behavior per Session without forking H2, 
because this flag is set in org.h2.engine.Database. 

Let’s discuss possible caveats in enabling this optimization by default in 
DEFAULT_DB_OPTIONS.

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Nikolay Izhikov]

Hello, Igniters.

While cherry-picking to 2.8.1 I found flaky test regarding BPlusTree [1], [2]

All failures of this tests relates to PR’s based on 2.8.
It seems we hav fix in master but doesn’t have it in 2.8 and 2.8.1 

Can someone suggest, what commit fixes this tests?

[1] 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-7895536196794411367=TEST_STATUS_DESC_IgniteTests24Java8=__all_branches__=50

[2] 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-3485591522651012009=TEST_STATUS_DESC_IgniteTests24Java8=__all_branches__=50


> 21 апр. 2020 г., в 17:49, Ivan Bessonov  написал(а):
> 
> Sure, here's PR with 3 cherry-picked commits that I mentioned:
> https://github.com/apache/ignite/pull/7708
> 
> вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov :
> 
>> OK then, let’s include it in the 2.8.1
>> 
>> Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain
>> cherry-pick for all required commits?
>> 
>>> 21 апр. 2020 г., в 17:01, Andrey Gura  написал(а):
>>> 
>>> Hi
>>> 
 IGNITE-12735 - Metric exporter implementation could lead to
>> NullPointerException from gauge which invoke communication
 IGNITE-12568 - MessageFactory implementations refactoring
>>> 
 Personally, I’m against any refactoring improvements in bug fix release.
 So, I propose to exclude IGNITE-12756 from 2.8.1
>>> 
 Andrey, what do you think as a committer of this improvements?
>>> 
>>> Mainly IGNITE-12756 brings some improvements related with TCP
>>> communication metrics (performance, memory footprint, IgniteSpiContext
>>> improved in order to provide ability to implement metrics related
>>> SPI's without using internal API's, code improvements)
>>> 
>>> But! It also fixes potential NPE's which can be thrown on node start.
>>> So it would be great to include this fix to 2.8.1 release.
>>> 
>>> On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov 
>> wrote:
 
> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
 
 
 Thanks!
 
> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
>> metrics
>> improvement" - it depends
>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>> https://issues.apache.org/jira/browse/IGNITE-12568,
>> both were targeted to 2.9, but this has to be changed probably.
 
 IGNITE-12735 - Metric exporter implementation could lead to
>> NullPointerException from gauge which invoke communication
 IGNITE-12568 - MessageFactory implementations refactoring
 
 Ivan,
 Personally, I’m against any refactoring improvements in bug fix release.
 So, I propose to exclude IGNITE-12756 from 2.8.1
 
 Andrey, what do you think as a committer of this improvements?
 
 
> 21 апр. 2020 г., в 10:44, Alex Plehanov 
>> написал(а):
> 
> Nikolay,
> 
> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> 
> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> 
>> Hello, Igniters,
>> 
>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
>> metrics
>> improvement" - it depends
>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
>> https://issues.apache.org/jira/browse/IGNITE-12568,
>> both were targeted to 2.9, but this has to be changed probably.
>> 
>> There might be other issues that I didn't find, we should probably ask
>> Andrey Gura about it, he is the author of
>> those changes.
>> 
>> So, release scope should be expanded a little bit, are you ok with it?
>> 
>> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
>> 
>>> Hello, Igniters.
>>> 
>>> I perform cherry-pick for most commits targeted for 2.8.1 release.
>>> 
>>> TC bot results -
>>> 
>> 
>> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
>>> 
>>> I need help with cherry picking the following commits:
>>> 
>>> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
>>> GridSecurityProcessor - Fixes #7523.
>>> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
>>> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed
>> or
>>> full read to unlock the GridH2Table. (#7551)
>>> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition -
>> Fixes
>>> #7494.
>>> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
>>> 
>>> Denis Garus,
>>> Taras Ledkov,
>>> Alexey Plekhanov,
>>> Ivan Bessonov,
>>> 
>>> Can you help me with above commits and cherry-pick your contribution
>> in
>>> ignite-2.8.1 branch?
>>> 
>>> CHERRY PICKED:
>>> 
>>> + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
>> which
>>> must not be used in production code (#7604)
>>> + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails
>> 

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Ivan Bessonov]

Sure, here's PR with 3 cherry-picked commits that I mentioned:
https://github.com/apache/ignite/pull/7708

вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov :

> OK then, let’s include it in the 2.8.1
>
> Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain
> cherry-pick for all required commits?
>
> > 21 апр. 2020 г., в 17:01, Andrey Gura  написал(а):
> >
> > Hi
> >
> >> IGNITE-12735 - Metric exporter implementation could lead to
> NullPointerException from gauge which invoke communication
> >> IGNITE-12568 - MessageFactory implementations refactoring
> >
> >> Personally, I’m against any refactoring improvements in bug fix release.
> >> So, I propose to exclude IGNITE-12756 from 2.8.1
> >
> >> Andrey, what do you think as a committer of this improvements?
> >
> > Mainly IGNITE-12756 brings some improvements related with TCP
> > communication metrics (performance, memory footprint, IgniteSpiContext
> > improved in order to provide ability to implement metrics related
> > SPI's without using internal API's, code improvements)
> >
> > But! It also fixes potential NPE's which can be thrown on node start.
> > So it would be great to include this fix to 2.8.1 release.
> >
> > On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov 
> wrote:
> >>
> >>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> >>
> >>
> >> Thanks!
> >>
> >>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
> metrics
>  improvement" - it depends
>  on https://issues.apache.org/jira/browse/IGNITE-12735 and
>  https://issues.apache.org/jira/browse/IGNITE-12568,
>  both were targeted to 2.9, but this has to be changed probably.
> >>
> >> IGNITE-12735 - Metric exporter implementation could lead to
> NullPointerException from gauge which invoke communication
> >> IGNITE-12568 - MessageFactory implementations refactoring
> >>
> >> Ivan,
> >> Personally, I’m against any refactoring improvements in bug fix release.
> >> So, I propose to exclude IGNITE-12756 from 2.8.1
> >>
> >> Andrey, what do you think as a committer of this improvements?
> >>
> >>
> >>> 21 апр. 2020 г., в 10:44, Alex Plehanov 
> написал(а):
> >>>
> >>> Nikolay,
> >>>
> >>> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> >>>
> >>> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> >>>
>  Hello, Igniters,
> 
>  considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
> metrics
>  improvement" - it depends
>  on https://issues.apache.org/jira/browse/IGNITE-12735 and
>  https://issues.apache.org/jira/browse/IGNITE-12568,
>  both were targeted to 2.9, but this has to be changed probably.
> 
>  There might be other issues that I didn't find, we should probably ask
>  Andrey Gura about it, he is the author of
>  those changes.
> 
>  So, release scope should be expanded a little bit, are you ok with it?
> 
>  пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
> 
> > Hello, Igniters.
> >
> > I perform cherry-pick for most commits targeted for 2.8.1 release.
> >
> > TC bot results -
> >
> 
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
> >
> > I need help with cherry picking the following commits:
> >
> > - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
> > GridSecurityProcessor - Fixes #7523.
> > - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
> > - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed
> or
> > full read to unlock the GridH2Table. (#7551)
> > - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition -
> Fixes
> > #7494.
> > - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
> >
> > Denis Garus,
> > Taras Ledkov,
> > Alexey Plekhanov,
> > Ivan Bessonov,
> >
> > Can you help me with above commits and cherry-pick your contribution
> in
> > ignite-2.8.1 branch?
> >
> > CHERRY PICKED:
> >
> > + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
>  which
> > must not be used in production code (#7604)
> > + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails
> BatchUpdateException
> > if function is used (#7615)
> > + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory
> restore
> > is in progress. Fixes #7562
> > + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with
> failed
> > deployment. (#7620)
> > + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
> > + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
>  Timestamp
> > and Guid params. (#7618)
> > + 6f3515686f IGNITE-12769: histogramNames cache in
> MetricRegistryMBean
> > removed. (#7549)
> > + 795617fc94 IGNITE-12774 Handle "Too many open files" exception -
> Fixes
> > #7516.
> > + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL 

[jira] [Created] (IGNITE-12927) The CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky

[Amelchev Nikita (Jira)]

Amelchev Nikita created IGNITE-12927:


 Summary: The 
CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime is flacky
 Key: IGNITE-12927
 URL: https://issues.apache.org/jira/browse/IGNITE-12927
 Project: Ignite
  Issue Type: Bug
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita


The {{CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime}} is 
flacky.
[TC 
history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-448222889376376497=%3Cdefault%3E=testDetails]

{noformat}
java.lang.IllegalStateException: Duplicate key 1472820775 (attempted merging 
values 1472820775 and 1472820775)
at 
java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
at 
java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
at 
java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
at 
java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
at 
java.base/java.util.Random$RandomIntsSpliterator.forEachRemaining(Random.java:1044)
at 
java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:699)
at 
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at 
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at 
java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
at 
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at 
java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
at 
org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalancingLastCancelledTime(CacheGroupsMetricsRebalanceTest.java:315)
{noformat}
The reason is that random generated keys can be duplicated and cant be 
collected from stream . 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.8.0 spring services configuration null fields

[Vyacheslav Daradur]

Hi, I looked through your example and can't reproduce it.
Properties injection works fine.

I suppose that you have run Ignite out of Spring context.

Please check your Spring context configuration file once again.

Here is an example:
https://github.com/apache/ignite/blob/53e47e9191d717b3eec495e6246cd957a8d33c7d/examples/src/main/java/org/apache/ignite/examples/misc/springbean/SpringBeanExample.java



On Tue, Apr 7, 2020 at 12:13 PM myset  wrote:

> So igniters,
>
> There are any issue on this ?
> Should I wait for further release ?
>
>
>
> -
> --
> Regards
> Cristian Gheorghe Florescu
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


-- 
Best Regards,
Vyacheslav D.

Re: Apache Ignite 2.8.0 spring services configuration null fields

[Vyacheslav Daradur]

Sorry, wrong link in previous email.

Here is an example:
https://github.com/apache/ignite/blob/master/modules/spring/src/test/java/org/apache/ignite/spring/injection/spring-bean.xml

On Tue, Apr 21, 2020 at 8:02 PM Vyacheslav Daradur 
wrote:

> Hi, I looked through your example and can't reproduce it.
> Properties injection works fine.
>
> I suppose that you have run Ignite out of Spring context.
>
> Please check your Spring context configuration file once again.
>
> Here is an example:
>
> https://github.com/apache/ignite/blob/53e47e9191d717b3eec495e6246cd957a8d33c7d/examples/src/main/java/org/apache/ignite/examples/misc/springbean/SpringBeanExample.java
>
>
>
> On Tue, Apr 7, 2020 at 12:13 PM myset  wrote:
>
>> So igniters,
>>
>> There are any issue on this ?
>> Should I wait for further release ?
>>
>>
>>
>> -
>> --
>> Regards
>> Cristian Gheorghe Florescu
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>
>
>
> --
> Best Regards,
> Vyacheslav D.
>


-- 
Best Regards,
Vyacheslav D.

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Denis Magda]

Nikolay,

@Peter Ivanov  or @Dmitriy Pavlov
 should
be able to help with the TeamCity Bot setup. Let's put all the knowledge on
paper once you figure it out.

-
Denis


On Tue, Apr 21, 2020 at 2:53 AM Nikolay Izhikov  wrote:

> Igniters.
>
> Can someone from Grid Gain help me with setup TC bot to monitor
> ignite-2.8.1 branch?
>
> > 21 апр. 2020 г., в 11:11, Nikolay Izhikov 
> написал(а):
> >
> >> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> >
> >
> > Thanks!
> >
> >> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI metrics
> >>> improvement" - it depends
> >>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> >>> https://issues.apache.org/jira/browse/IGNITE-12568,
> >>> both were targeted to 2.9, but this has to be changed probably.
> >
> > IGNITE-12735 - Metric exporter implementation could lead to
> NullPointerException from gauge which invoke communication
> > IGNITE-12568 - MessageFactory implementations refactoring
> >
> > Ivan,
> > Personally, I’m against any refactoring improvements in bug fix release.
> > So, I propose to exclude IGNITE-12756 from 2.8.1
> >
> > Andrey, what do you think as a committer of this improvements?
> >
> >
> >> 21 апр. 2020 г., в 10:44, Alex Plehanov 
> написал(а):
> >>
> >> Nikolay,
> >>
> >> I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> >>
> >> вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> >>
> >>> Hello, Igniters,
> >>>
> >>> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
> metrics
> >>> improvement" - it depends
> >>> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> >>> https://issues.apache.org/jira/browse/IGNITE-12568,
> >>> both were targeted to 2.9, but this has to be changed probably.
> >>>
> >>> There might be other issues that I didn't find, we should probably ask
> >>> Andrey Gura about it, he is the author of
> >>> those changes.
> >>>
> >>> So, release scope should be expanded a little bit, are you ok with it?
> >>>
> >>> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
> >>>
>  Hello, Igniters.
> 
>  I perform cherry-pick for most commits targeted for 2.8.1 release.
> 
>  TC bot results -
> 
> >>>
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
> 
>  I need help with cherry picking the following commits:
> 
>  - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
>  GridSecurityProcessor - Fixes #7523.
>  - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
>  - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed
> or
>  full read to unlock the GridH2Table. (#7551)
>  - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition -
> Fixes
>  #7494.
>  - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics improvement
> 
>  Denis Garus,
>  Taras Ledkov,
>  Alexey Plekhanov,
>  Ivan Bessonov,
> 
>  Can you help me with above commits and cherry-pick your contribution
> in
>  ignite-2.8.1 branch?
> 
>  CHERRY PICKED:
> 
>  + d0c155fe43 IGNITE-12772 Fixed JmxMetricExporterSpi uses log method
> >>> which
>  must not be used in production code (#7604)
>  + 00cb1ad7a3 IGNITE-12764: Thin JDBC streaming fails
> BatchUpdateException
>  if function is used (#7615)
>  + b8167296b1 IGNITE-12805 Fixed NullPointerException when memory
> restore
>  is in progress. Fixes #7562
>  + f57509e8e6 IGNITE-12828 Fixes NPE during CQ registration with failed
>  deployment. (#7620)
>  + 826aad8890 IGNITE-12726 Long keys support for metastorage. (#7606)
>  + 2b1d2b4dec IGNITE-12859: Support of .Net service call with the
> >>> Timestamp
>  and Guid params. (#7618)
>  + 6f3515686f IGNITE-12769: histogramNames cache in MetricRegistryMBean
>  removed. (#7549)
>  + 795617fc94 IGNITE-12774 Handle "Too many open files" exception -
> Fixes
>  #7516.
>  + 3928bb3a13 IGNITE-12799 Fixed wrong SpEL expression.
>  + ef4f67e351 IGNITE-12743 Java thin client: Fixed thread shutdown on
>  client close when partition awareness is enabled - Fixes #7522.
>  + e389bb8f55 IGNITE-12728 Collect time statistics on
> cache#putAllAsync -
>  Fixes #7483.
>  + 90951c6b2e IGNITE-12711 Fixed tests memory usage. - Fixes #7469.
>  + f32b44deb1 IGNITE-12590: Fix (remove) check KEY at the MERGE command
>  (#7321)
>  + 59917f0731 IGNITE-12624 Java thin client: typeId generation for
> system
>  types fixed - Fixes #7416.
>  + cc6f4d7814 IGNITE-12671 Ignoring single messages during PME can
> prevent
>  late affinity switch. - Fixes #7425.
>  + 02ac292662 IGNITE-11798 Fix memory leak on unstable topology caused
> by
>  partition reservation (#7251)
>  + 8ed8576544 IGNITE-12665: SQL: Fix potential race on MapResult close.
>  + 465cc444d0 IGNITE-12582 Add Spring EL support in Spring Data. -
> Fixes
>  #7411.
>  + 

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

[Pavel Pereslegin]

Hello, Nikolay.

This has been fixed by increasing the test timeout in IGNITE-12683 [1][2].

[1] https://issues.apache.org/jira/browse/IGNITE-12683
[2] 
https://github.com/apache/ignite/commit/bf394a77e1de6432e493eb2818243a82b577f11e

вт, 21 апр. 2020 г. в 18:28, Nikolay Izhikov :
>
> Hello, Igniters.
>
> While cherry-picking to 2.8.1 I found flaky test regarding BPlusTree [1], [2]
>
> All failures of this tests relates to PR’s based on 2.8.
> It seems we hav fix in master but doesn’t have it in 2.8 and 2.8.1
>
> Can someone suggest, what commit fixes this tests?
>
> [1] 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-7895536196794411367=TEST_STATUS_DESC_IgniteTests24Java8=__all_branches__=50
>
> [2] 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-3485591522651012009=TEST_STATUS_DESC_IgniteTests24Java8=__all_branches__=50
>
>
> > 21 апр. 2020 г., в 17:49, Ivan Bessonov  написал(а):
> >
> > Sure, here's PR with 3 cherry-picked commits that I mentioned:
> > https://github.com/apache/ignite/pull/7708
> >
> > вт, 21 апр. 2020 г. в 17:17, Nikolay Izhikov :
> >
> >> OK then, let’s include it in the 2.8.1
> >>
> >> Ivan, can you, please, prepare PR in the ignite-2.8.1 branch that contain
> >> cherry-pick for all required commits?
> >>
> >>> 21 апр. 2020 г., в 17:01, Andrey Gura  написал(а):
> >>>
> >>> Hi
> >>>
>  IGNITE-12735 - Metric exporter implementation could lead to
> >> NullPointerException from gauge which invoke communication
>  IGNITE-12568 - MessageFactory implementations refactoring
> >>>
>  Personally, I’m against any refactoring improvements in bug fix release.
>  So, I propose to exclude IGNITE-12756 from 2.8.1
> >>>
>  Andrey, what do you think as a committer of this improvements?
> >>>
> >>> Mainly IGNITE-12756 brings some improvements related with TCP
> >>> communication metrics (performance, memory footprint, IgniteSpiContext
> >>> improved in order to provide ability to implement metrics related
> >>> SPI's without using internal API's, code improvements)
> >>>
> >>> But! It also fixes potential NPE's which can be thrown on node start.
> >>> So it would be great to include this fix to 2.8.1 release.
> >>>
> >>> On Tue, Apr 21, 2020 at 11:12 AM Nikolay Izhikov 
> >> wrote:
> 
> > I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> 
> 
>  Thanks!
> 
> > considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
> >> metrics
> >> improvement" - it depends
> >> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> >> https://issues.apache.org/jira/browse/IGNITE-12568,
> >> both were targeted to 2.9, but this has to be changed probably.
> 
>  IGNITE-12735 - Metric exporter implementation could lead to
> >> NullPointerException from gauge which invoke communication
>  IGNITE-12568 - MessageFactory implementations refactoring
> 
>  Ivan,
>  Personally, I’m against any refactoring improvements in bug fix release.
>  So, I propose to exclude IGNITE-12756 from 2.8.1
> 
>  Andrey, what do you think as a committer of this improvements?
> 
> 
> > 21 апр. 2020 г., в 10:44, Alex Plehanov 
> >> написал(а):
> >
> > Nikolay,
> >
> > I've cherry-picked IGNITE-12734 to 2.8.1 branch.
> >
> > вт, 21 апр. 2020 г. в 10:02, Ivan Bessonov :
> >
> >> Hello, Igniters,
> >>
> >> considering commit "683f22e64f IGNITE-12756 TcpCommunication SPI
> >> metrics
> >> improvement" - it depends
> >> on https://issues.apache.org/jira/browse/IGNITE-12735 and
> >> https://issues.apache.org/jira/browse/IGNITE-12568,
> >> both were targeted to 2.9, but this has to be changed probably.
> >>
> >> There might be other issues that I didn't find, we should probably ask
> >> Andrey Gura about it, he is the author of
> >> those changes.
> >>
> >> So, release scope should be expanded a little bit, are you ok with it?
> >>
> >> пн, 20 апр. 2020 г. в 19:24, Nikolay Izhikov :
> >>
> >>> Hello, Igniters.
> >>>
> >>> I perform cherry-pick for most commits targeted for 2.8.1 release.
> >>>
> >>> TC bot results -
> >>>
> >>
> >> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead
> >>>
> >>> I need help with cherry picking the following commits:
> >>>
> >>> - 4e6cd2ce04 IGNITE-12759 Getting a SecurityContext from
> >>> GridSecurityProcessor - Fixes #7523.
> >>> - 60ebc23f99 IGNITE-12848 fix H2Connection leaks on INSERT (#7649)
> >>> - 0b185b192f IGNITE-12800  SQL: local queries cursors must be closed
> >> or
> >>> full read to unlock the GridH2Table. (#7551)
> >>> - bcaae8deef IGNITE-12734 Fixed scan query over evicted partition -
> >> Fixes
> >>> #7494.
> >>> - 683f22e64f IGNITE-12756 TcpCommunication SPI metrics 

Re: Moving python, php and node.js in separate repos and release cycles

[Pavel Tupitsyn]

-1

- Ignite is a single Apache project, it follows Apache release guidelines,
with voting and so on. Not sure how are we going to follow that with a
separate repo.
- Thin client features are often tied to server-side changes

> What about dotnet and cpp thin clients?
Those reuse some code with thick counterparts - same way as Java thin does.


On Tue, Apr 21, 2020 at 4:22 PM Nikolay Izhikov  wrote:

> What about dotnet and cpp thin clients?
>
> > 21 апр. 2020 г., в 16:19, Dmitriy Pavlov 
> написал(а):
> >
> > +1 since
> > - Simpler release may allow us to release more often
> > - Often releases - users will get updates faster, more chances to grow
> and
> > keep our user base
> > - Faster updates and easy to get next update may have positive effect on
> > community growth. Since newcomer may want to fix a bug and later use
> result
> > in his/her production environment.
> >
> > вт, 21 апр. 2020 г. в 13:27, Alexey Zinoviev :
> >
> >> Agree with these non-JVM languages.
> >> Especially for Python:)
> >>
> >> вт, 21 апр. 2020 г. в 12:58, Igor Sapego :
> >>
> >>> Guys,
> >>>
> >>> It was discussed on the dev list a few times that it would be a good
> >>> idea to move Python, Node.js and PHP thin clients to separate repos
> >>> and separate release cycles.
> >>>
> >>> In short there are several arguments for that:
> >>>
> >>> 1. There are no dependencies on the core functionality so there is
> simply
> >>> no need for them to be in the main repo.
> >>>
> >>> 2. Those thin clients often do not get updates from release to release,
> >> but
> >>> still
> >>> we "release" them, as they are a part of the main release.
> >>>
> >>> 3. Moving them to a separate release cycle will allow us to release
> some
> >>> hot
> >>> fixes for those clients faster and easier.
> >>>
> >>> 4. Composer needs a PHP packet that is released to be in a separate
> >>> repository.
> >>>
> >>> Thoughts?
> >>>
> >>> Best Regards,
> >>> Igor
> >>>
> >>
>
>

Re: Apache Ignite 2.8.0 spring services configuration null fields

[Vyacheslav Daradur]

Now I see.

Your parent class (called Test in your example) *should implement
'Serializable' interface*, this will help for your case.

We changed default marshaller for services in 2.8, because they have to
be 'Serializable' according to API. 'JdkMarshaller' is default marshaller
for services now.

I think 'BinaryMarshaller' was configured in your case, it marshals
everything even non-serializable objects :)

On Tue, Apr 21, 2020 at 8:41 PM myset  wrote:

> Thank you Vyacheslav,
> Still reproduced in 2.8.0 and in 2.7.6 is not.
> Please take a look carefully at the gist example code.
>
> public class TestServiceImpl extends *Test* implements Service,TestService
>
>
>
>
> -
> Regards
> Cristian Gheorghe Florescu
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


-- 
Best Regards,
Vyacheslav D.

[jira] [Created] (IGNITE-12929) Incorrect setClientMode calls instead of startClientGrid

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-12929:


 Summary: Incorrect setClientMode calls instead of startClientGrid
 Key: IGNITE-12929
 URL: https://issues.apache.org/jira/browse/IGNITE-12929
 Project: Ignite
  Issue Type: Task
Reporter: Maxim Muzafarov


There were some places left after IGNITE-12493 merge where {{setClientMode}} 
instead of {{startClientGrid}}. 
Need to be fixed.

Examples:
https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/database/IgniteDbAbstractTest.java#L168

https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java/org/apache/ignite/internal/processors/cache/SqlCacheStartStopTest.java#L81



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12930) DistributedProcess fails node if unable to send single message to coordinator

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-12930:


 Summary: DistributedProcess fails node if unable to send single 
message to coordinator
 Key: IGNITE-12930
 URL: https://issues.apache.org/jira/browse/IGNITE-12930
 Project: Ignite
  Issue Type: Task
Reporter: Maxim Muzafarov


The 
[DistributedProcess|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/distributed/DistributedProcess.java]
 fails the local node ({{FailureHandler}} CRITICAL_ERROR thrown) if unable to 
send a message to the coordinator (e.g. the coordinator fails right before the 
single message is sent).
{code:java}
try {
ctx.io().sendToGridTopic(p.crdId, 
GridTopic.TOPIC_DISTRIBUTED_PROCESS, singleMsg, SYSTEM_POOL);
}
catch (IgniteCheckedException e) {
log.error("Unable to send message to coordinator.", e);

ctx.failure().process(new FailureContext(CRITICAL_ERROR,
new Exception("Unable to send message to coordinator.", 
e)));
}
{code}
h4. Expected behaviour

If the {{ClusterTopologyCheckedException}} occurs need to wait for the 
NODE_LEFT event of the coordinator node and re-init the distributed process 
future.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: No commits to Ignite website: migration from SVN to Git is in progress

[Saikat Maitra]

Hi Denis,

Thank you, yes I will use the GitHub built-in capabilities.

Regards,
Saikat

On Mon, Apr 20, 2020 at 1:01 PM Denis Magda  wrote:

> Saikat, now I see your point, thanks for breaking it down. As of now, there
> is no need for those scripts, at least, for the website repository. It's
> easy to review and merge changes using GitHub built-in capabilities and
> controls with all the changes propagated to ASF's repos.
>
> -
> Denis
>
>
> On Sun, Apr 19, 2020 at 4:43 AM Dmitriy Pavlov  wrote:
>
> > Yes, most likely there are 2 separate repos (presumably, gitbox servers
> > provided by Microsoft - not 100% sure here), but these repositories have
> > fast 2-way sync now. I remember that Infra fixed something in this sync.
> >
> > вс, 19 апр. 2020 г. в 02:57, Saikat Maitra :
> >
> > > Hi Dmitriy,
> > >
> > > Thank you for your email. I am fine with Github built-in merge tool.
> > >
> > > Since, in ignite repo we were using the apply-pull-request.sh script
> and
> > > pushing changes to gitbox (
> > https://gitbox.apache.org/repos/asf/ignite.git)
> > >
> > > I noted that it was immediately syncing the changes in github as well.
> > >
> > > My understanding is the repo sync is two way and if we merge changes in
> > > github then also it will be synced back to gitbox repo.
> > >
> > > Regards,
> > > Saikat
> > >
> > >
> > >
> > > On Sat, Apr 18, 2020 at 6:40 PM Dmitriy Pavlov 
> > wrote:
> > >
> > > >  Hi Folks,
> > > >
> > > > Thanks, to Denis and Infra
> > > >
> > > > Saikat,
> > > >
> > > > with a slight risk of starting off-topic discussions about that, I
> > > > nevertheless would like to suggest using GitHub build-in merge tool
> for
> > > PRs
> > > > in the ignite-website. It always closes PRs, it closes right PR, so I
> > > find
> > > > this option less error-prone. Since Infra integrated ASF repos with
> > > GitHub
> > > > It is really easy to merge changes.
> > > >
> > > > But still, if you find having apply-pr script useful by any means,
> > sure,
> > > go
> > > > ahead. There are no restrictions there.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > сб, 18 апр. 2020 г. в 21:43, Saikat Maitra  >:
> > > >
> > > > > Hi Denis,
> > > > >
> > > > > Thank you for your email. Yes, the docs looks good.
> > > > >
> > > > > I was asking about this script that we use in ignite repo as well
> for
> > > > > committing changes.
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/ignite/blob/master/scripts/apply-pull-request.sh
> > > > >
> > > > > Regards,
> > > > > Saikat
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Apr 13, 2020 at 11:53 AM Denis Magda 
> > > wrote:
> > > > >
> > > > > > Hello Saikat,
> > > > > >
> > > > > > You can find short website development guidelines on this page
> [1].
> > > > They
> > > > > > are elementary and request to use pull-requests, especially, if
> the
> > > one
> > > > > is
> > > > > > not a committer. Feel free to elaborate on the process.
> > > > > >
> > > > > > Btw, what are the scripts referred by you?
> > > > > >
> > > > > > [1]
> > > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
> > > > > > -
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > > On Sun, Apr 12, 2020 at 12:26 PM Saikat Maitra <
> > > > saikat.mai...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > Are we following the same contribution flow as we are doing for
> > > > ignite
> > > > > > git
> > > > > > > repo?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ClosingaTicket
> > > > > > >
> > > > > > > I have observed that github ignite-website is also mirrored at
> > > > > > > https://gitbox.apache.org/repos/asf?p=ignite-website.git
> > > > > > >
> > > > > > > I can add our scripts folder in ignite-website folder if it
> > helps.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Saikat
> > > > > > >
> > > > > > > On Tue, Apr 7, 2020 at 12:49 AM Ivan Pavlukhin <
> > > vololo...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thank you!
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Ivan Pavlukhin
> > > > > > > >
> > > > > > > > вт, 7 апр. 2020 г. в 00:46, Denis Magda :
> > > > > > > > >
> > > > > > > > > The website is back to normal and serves the content from
> the
> > > Git
> > > > > > > > > repository's "master" branch:
> > > > > > > > > https://github.com/apache/ignite-website/blob/master
> > > > > > > > >
> > > > > > > > > -
> > > > > > > > > Denis
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Apr 6, 2020 at 2:19 PM Denis Magda <
> > dma...@apache.org>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > I'm checking with the INFRA. It's down for at least the
> > last
> > > > > couple
> > > > > > > of
> > > > > > > > > > hours.
> > > > > > > > > >
> > > > > > > > > > -
> > > > > > > > > > Denis
> > > > > > > > > >
> > > > > 

Re: Apache Ignite 2.8.0 spring services configuration null fields

[myset]

Thank you Vyacheslav,

Case closed. It works fine in 2.8.0 if service extended Test class
implements Serializable.

/Keep up good work "Igniters"/



-
Regards
Cristian Gheorghe Florescu
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-12928) CacheMetricsMXBean does not provide proper descriptions for rebalancing attributes

[Maria Makedonskaya (Jira)]

Maria Makedonskaya created IGNITE-12928:
---

 Summary: CacheMetricsMXBean does not provide proper descriptions 
for rebalancing attributes
 Key: IGNITE-12928
 URL: https://issues.apache.org/jira/browse/IGNITE-12928
 Project: Ignite
  Issue Type: Bug
Reporter: Maria Makedonskaya
Assignee: Maria Makedonskaya


When querying MBean info via JMX one expects to get meaningful descriptions for 
all attributes.
However, for bean CacheMetricsMXBean, no descriptions provided for following 
attributes, default value 'Attribute exposed for management' returned instead:

* EstimatedRebalancingFinishTime
* KeysToRebalanceLeft
* RebalancingBytesRate
* RebalancingKeysRate
* RebalancingPartitionsCount
* RebalancingStartTime
* TotalPartitionsCount



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.8.0 spring services configuration null fields

[myset]

Thank you Vyacheslav,
Still reproduced in 2.8.0 and in 2.7.6 is not.
Please take a look carefully at the gist example code.

public class TestServiceImpl extends *Test* implements Service,TestService




-
Regards
Cristian Gheorghe Florescu
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/