Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Denis, where should i make my PR to update documentation? To my understanding there was a discussion whether to make PR into master or into a release branch (at least release notes are merged into master) but the general consensus wasn't reached. On Wed, Dec 16, 2020 at 9:24 PM Yaroslav Molochkov wrote: > Will do. > > On Wed, Dec 16, 2020 at 9:15 PM Denis Magda wrote: > >> +1 (binding). Reverting my previous -1. We agreed that the release won't >> be >> announced and referenced from the website until the docs are ready. >> >> Yaroslav, could you please help to prepare the tickets and put together a >> draft? Nikita, thanks a lot for stepping up and agreeing to help with the >> review! >> >> >> - >> Denis >> >> >> On Wed, Dec 16, 2020 at 10:12 AM Yaroslav Molochkov < >> molochko...@gmail.com> >> wrote: >> >> > Hello everyone! >> > >> > Yeah, guys, sorry, absolutely my mishap with docs. >> > >> > Denis, of course, i will see to it that docs are ready first and >> foremost. >> > >> > On Wed, Dec 16, 2020 at 8:30 PM Denis Magda wrote: >> > >> > > Hi Maxim, >> > > >> > > Ignite 2.9 docs were completed by the time we were running a vote for >> the >> > > last release candidate. Once the vote passed, I released the docs >> through >> > > the website. What happened next is an ongoing process of keeping the >> docs >> > > actual - addressing users' feedback, merging generic changes to the >> > master >> > > and the latest release branch, etc. >> > > >> > > Anyway, speaking about 2.9.1. This is, in fact, a release blocker. >> > > Otherwise, I wouldn't have cast the -1 vote. We're doing those >> features >> > for >> > > application developers who shouldn't consult with the Ignite source >> > > codebase on how to leverage the new capabilities. >> > > >> > > But, I hear you. Let's make an exception this time, considering a >> small >> > > number of documentation tasks. As the community, I do believe that we >> > will >> > > eventually develop a habit of preparing all necessary changes by the >> > time a >> > > vote starts. So, do we agree that the release won't be announced, and >> > > binaries won't be referenced from the website until the docs are >> ready? >> > My >> > > guess the docs might be ready this or early next week. >> > > >> > > - >> > > Denis >> > > >> > > >> > > On Wed, Dec 16, 2020 at 7:00 AM Maxim Muzafarov >> > wrote: >> > > >> > > > Denis, >> > > > >> > > > I remember the agreement, but also we are always fixing >> documentation >> > > > pages even after a release announced (like for 2.9.0 and the >> > > > ignite-2.9 release branch). Can we go the same way here? For >> instance, >> > > > we can add all necessary documentation pages prior to the 2.9.1 wide >> > > > announce. >> > > > >> > > > It doesn't seem to be the release blocker here, as the same as the >> > > > checkstyle issues weren't for 2.9.0. Isn't it? >> > > > >> > > > On Wed, 16 Dec 2020 at 17:14, Denis Magda >> wrote: >> > > > > >> > > > > Yaroslav, thanks for checking, >> > > > > >> > > > > - 1 (binding) - I have to cast this vote as long as the docs need >> to >> > be >> > > > > ready by the time of the vote. >> > > > > >> > > > > Yaroslav, could you please help to prepare a draft with the >> > > documentation >> > > > > updates? Nikita, would you mind reviewing the changes? >> > > > > >> > > > > Denis >> > > > > >> > > > > On Wednesday, December 16, 2020, Yaroslav Molochkov < >> > > > molochko...@gmail.com> >> > > > > wrote: >> > > > > >> > > > > > Denis, actually, i'm mistaken, totally forgot about these: >> > > > > > * Added System view for binary metadata >> > > > > > * Added System view for metastorage items >> > > > > > * Added RebalancingPartitionsTotal metrics >> > > > > > >> > > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov < >> > > > molochko...@gmail.com> >> > > > > > wrote: >> > > > > > >> > > > > > > Denis, hello! >> > > > > > > >> > > > > > > Since it's a minor bug-fixing release the update is not needed >> > > > > > > >> > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda < >> dma...@apache.org> >> > > > wrote: >> > > > > > > >> > > > > > >> Hi Yaroslav, >> > > > > > >> >> > > > > > >> Do we need to update documentation? >> > > > > > >> >> > > > > > >> - >> > > > > > >> Denis >> > > > > > >> >> > > > > > >> >> > > > > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < >> > > > > > >> molochko...@gmail.com> >> > > > > > >> wrote: >> > > > > > >> >> > > > > > >> > Dear Community, >> > > > > > >> > >> > > > > > >> > I have uploaded release candidate to >> > > > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ >> > > > > > >> > >> > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ >> > > > > > >> > >> > > > > > >> > The following staging can be used for testing: >> > > > > > >> > >> > > > > > >> https://repository.apache.org/content/repositories/ >> > > > > > orgapacheignite-1490/ >> > > > > > >> > >> > > > > > >> > Tag name is 2.9.1-rc1: >> > > > > > >> > >>
[jira] [Created] (IGNITE-13870) Remove GridCacheAdapter#validateCacheKey cause it seems to be obsolete
Alexander Lapin created IGNITE-13870: Summary: Remove GridCacheAdapter#validateCacheKey cause it seems to be obsolete Key: IGNITE-13870 URL: https://issues.apache.org/jira/browse/IGNITE-13870 Project: Ignite Issue Type: Bug Reporter: Alexander Lapin Assignee: Alexander Lapin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13869) Add extra map query logging within the debug level.
Alexander Lapin created IGNITE-13869: Summary: Add extra map query logging within the debug level. Key: IGNITE-13869 URL: https://issues.apache.org/jira/browse/IGNITE-13869 Project: Ignite Issue Type: Bug Components: sql Reporter: Alexander Lapin Assignee: Alexander Lapin For some cases, particularly partition pruning and affinity awareness checks, it would be useful to log map queries on a recipient nodes in case of debug log level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13868) Create caches simultaneously in same non-existing cache group led to NPE
Alexander Lapin created IGNITE-13868:
Summary: Create caches simultaneously in same non-existing cache
group led to NPE
Key: IGNITE-13868
URL: https://issues.apache.org/jira/browse/IGNITE-13868
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
Assignee: Alexander Lapin
1 server 1 client
Case:
server create cache and group
client create cache in previous group
{code:java}
Caused by: java.lang.NullPointerException
at
java.util.Collections$UnmodifiableCollection.(Collections.java:1026)
at java.util.Collections$UnmodifiableList.(Collections.java:1302)
at java.util.Collections.unmodifiableList(Collections.java:1287)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentV2.(GridAffinityAssignmentV2.java:108)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.initialize(GridAffinityAssignmentCache.java:205)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.init(GridAffinityAssignmentCache.java:750)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CacheGroupHolder.(CacheAffinitySharedManager.java:2635)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CacheGroupAffNodeHolder.(CacheAffinitySharedManager.java:2692)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initStartedGroup(CacheAffinitySharedManager.java:1339)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.lambda$initAffinityOnCacheGroupsStart$641a38d$1(CacheAffinitySharedManager.java:1001)
at
org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10575)
at
org.apache.ignite.internal.util.IgniteUtils.doInParallel(IgniteUtils.java:10498)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.initAffinityOnCacheGroupsStart(CacheAffinitySharedManager.java:997)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:975)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:833)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1238)
... 5 more
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13867) IgniteCacheTxExpiryPolicyTest.testNearAccess almost stably fails in CE master
Alexander Lapin created IGNITE-13867:
Summary: IgniteCacheTxExpiryPolicyTest.testNearAccess almost
stably fails in CE master
Key: IGNITE-13867
URL: https://issues.apache.org/jira/browse/IGNITE-13867
Project: Ignite
Issue Type: Bug
Reporter: Alexander Lapin
Assignee: Alexander Lapin
[TC|https://ci.ignite.apache.org/project.html?testNameId=-5197950048275421802&projectId=IgniteTests24Java8&buildTypeId=IgniteTests24Java8_CacheExpiryPolicy&tab=testDetails&branch_IgniteTests24Java8=ignite-2.9.1&fromExperimentalUI=true&showExperimentalUIOptout=true]
{code:java}
java.lang.AssertionError: Unexpected non-null value for grid 1 expected null,
but was:<1>
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13866) Validate index does not stop after process of control.sh was interrupted
Vladislav Pyatkov created IGNITE-13866: -- Summary: Validate index does not stop after process of control.sh was interrupted Key: IGNITE-13866 URL: https://issues.apache.org/jira/browse/IGNITE-13866 Project: Ignite Issue Type: Bug Reporter: Vladislav Pyatkov Validate index command might to continue in a cluster even after the command is emergency terminated. For example: we can type CTRL+c in console for terminate an incorrect command invocation, but this command does not be terminated in cluster. In the end of this we have a several processes the result of which does not need anymore. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[MTCGA]: new failures in builds [5786205] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master-nightly ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-6680146643417075475&branch=%3Cdefault%3E&tab=testDetails No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 21:50:58 16-12-2020
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Will do. On Wed, Dec 16, 2020 at 9:15 PM Denis Magda wrote: > +1 (binding). Reverting my previous -1. We agreed that the release won't be > announced and referenced from the website until the docs are ready. > > Yaroslav, could you please help to prepare the tickets and put together a > draft? Nikita, thanks a lot for stepping up and agreeing to help with the > review! > > > - > Denis > > > On Wed, Dec 16, 2020 at 10:12 AM Yaroslav Molochkov > > wrote: > > > Hello everyone! > > > > Yeah, guys, sorry, absolutely my mishap with docs. > > > > Denis, of course, i will see to it that docs are ready first and > foremost. > > > > On Wed, Dec 16, 2020 at 8:30 PM Denis Magda wrote: > > > > > Hi Maxim, > > > > > > Ignite 2.9 docs were completed by the time we were running a vote for > the > > > last release candidate. Once the vote passed, I released the docs > through > > > the website. What happened next is an ongoing process of keeping the > docs > > > actual - addressing users' feedback, merging generic changes to the > > master > > > and the latest release branch, etc. > > > > > > Anyway, speaking about 2.9.1. This is, in fact, a release blocker. > > > Otherwise, I wouldn't have cast the -1 vote. We're doing those features > > for > > > application developers who shouldn't consult with the Ignite source > > > codebase on how to leverage the new capabilities. > > > > > > But, I hear you. Let's make an exception this time, considering a small > > > number of documentation tasks. As the community, I do believe that we > > will > > > eventually develop a habit of preparing all necessary changes by the > > time a > > > vote starts. So, do we agree that the release won't be announced, and > > > binaries won't be referenced from the website until the docs are ready? > > My > > > guess the docs might be ready this or early next week. > > > > > > - > > > Denis > > > > > > > > > On Wed, Dec 16, 2020 at 7:00 AM Maxim Muzafarov > > wrote: > > > > > > > Denis, > > > > > > > > I remember the agreement, but also we are always fixing documentation > > > > pages even after a release announced (like for 2.9.0 and the > > > > ignite-2.9 release branch). Can we go the same way here? For > instance, > > > > we can add all necessary documentation pages prior to the 2.9.1 wide > > > > announce. > > > > > > > > It doesn't seem to be the release blocker here, as the same as the > > > > checkstyle issues weren't for 2.9.0. Isn't it? > > > > > > > > On Wed, 16 Dec 2020 at 17:14, Denis Magda wrote: > > > > > > > > > > Yaroslav, thanks for checking, > > > > > > > > > > - 1 (binding) - I have to cast this vote as long as the docs need > to > > be > > > > > ready by the time of the vote. > > > > > > > > > > Yaroslav, could you please help to prepare a draft with the > > > documentation > > > > > updates? Nikita, would you mind reviewing the changes? > > > > > > > > > > Denis > > > > > > > > > > On Wednesday, December 16, 2020, Yaroslav Molochkov < > > > > molochko...@gmail.com> > > > > > wrote: > > > > > > > > > > > Denis, actually, i'm mistaken, totally forgot about these: > > > > > > * Added System view for binary metadata > > > > > > * Added System view for metastorage items > > > > > > * Added RebalancingPartitionsTotal metrics > > > > > > > > > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov < > > > > molochko...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Denis, hello! > > > > > > > > > > > > > > Since it's a minor bug-fixing release the update is not needed > > > > > > > > > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda > > > > > wrote: > > > > > > > > > > > > > >> Hi Yaroslav, > > > > > > >> > > > > > > >> Do we need to update documentation? > > > > > > >> > > > > > > >> - > > > > > > >> Denis > > > > > > >> > > > > > > >> > > > > > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > > > > > > >> molochko...@gmail.com> > > > > > > >> wrote: > > > > > > >> > > > > > > >> > Dear Community, > > > > > > >> > > > > > > > >> > I have uploaded release candidate to > > > > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > > > > > >> > > > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > > > > > >> > > > > > > > >> > The following staging can be used for testing: > > > > > > >> > > > > > > > >> https://repository.apache.org/content/repositories/ > > > > > > orgapacheignite-1490/ > > > > > > >> > > > > > > > >> > Tag name is 2.9.1-rc1: > > > > > > >> > > > > > > > >> > > > > > > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > > > > > > h=refs/tags/2.9.1-rc1 > > > > > > >> > > > > > > > >> > 2.9.1 changes: > > > > > > >> > * Added support to graceful shutdown for > ZookeeperDiscoverySpi > > > > > > >> > * Added System view for binary metadata > > > > > > >> > * Added System view for metastorage items > > > > > > >> > * Added RebalancingPartitionsTotal metrics > > > > > > >> > * Improved checkpoint concurrent behaviour > > > > > > >> > * Fixed
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
+1 (binding). Reverting my previous -1. We agreed that the release won't be announced and referenced from the website until the docs are ready. Yaroslav, could you please help to prepare the tickets and put together a draft? Nikita, thanks a lot for stepping up and agreeing to help with the review! - Denis On Wed, Dec 16, 2020 at 10:12 AM Yaroslav Molochkov wrote: > Hello everyone! > > Yeah, guys, sorry, absolutely my mishap with docs. > > Denis, of course, i will see to it that docs are ready first and foremost. > > On Wed, Dec 16, 2020 at 8:30 PM Denis Magda wrote: > > > Hi Maxim, > > > > Ignite 2.9 docs were completed by the time we were running a vote for the > > last release candidate. Once the vote passed, I released the docs through > > the website. What happened next is an ongoing process of keeping the docs > > actual - addressing users' feedback, merging generic changes to the > master > > and the latest release branch, etc. > > > > Anyway, speaking about 2.9.1. This is, in fact, a release blocker. > > Otherwise, I wouldn't have cast the -1 vote. We're doing those features > for > > application developers who shouldn't consult with the Ignite source > > codebase on how to leverage the new capabilities. > > > > But, I hear you. Let's make an exception this time, considering a small > > number of documentation tasks. As the community, I do believe that we > will > > eventually develop a habit of preparing all necessary changes by the > time a > > vote starts. So, do we agree that the release won't be announced, and > > binaries won't be referenced from the website until the docs are ready? > My > > guess the docs might be ready this or early next week. > > > > - > > Denis > > > > > > On Wed, Dec 16, 2020 at 7:00 AM Maxim Muzafarov > wrote: > > > > > Denis, > > > > > > I remember the agreement, but also we are always fixing documentation > > > pages even after a release announced (like for 2.9.0 and the > > > ignite-2.9 release branch). Can we go the same way here? For instance, > > > we can add all necessary documentation pages prior to the 2.9.1 wide > > > announce. > > > > > > It doesn't seem to be the release blocker here, as the same as the > > > checkstyle issues weren't for 2.9.0. Isn't it? > > > > > > On Wed, 16 Dec 2020 at 17:14, Denis Magda wrote: > > > > > > > > Yaroslav, thanks for checking, > > > > > > > > - 1 (binding) - I have to cast this vote as long as the docs need to > be > > > > ready by the time of the vote. > > > > > > > > Yaroslav, could you please help to prepare a draft with the > > documentation > > > > updates? Nikita, would you mind reviewing the changes? > > > > > > > > Denis > > > > > > > > On Wednesday, December 16, 2020, Yaroslav Molochkov < > > > molochko...@gmail.com> > > > > wrote: > > > > > > > > > Denis, actually, i'm mistaken, totally forgot about these: > > > > > * Added System view for binary metadata > > > > > * Added System view for metastorage items > > > > > * Added RebalancingPartitionsTotal metrics > > > > > > > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov < > > > molochko...@gmail.com> > > > > > wrote: > > > > > > > > > > > Denis, hello! > > > > > > > > > > > > Since it's a minor bug-fixing release the update is not needed > > > > > > > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda > > > wrote: > > > > > > > > > > > >> Hi Yaroslav, > > > > > >> > > > > > >> Do we need to update documentation? > > > > > >> > > > > > >> - > > > > > >> Denis > > > > > >> > > > > > >> > > > > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > > > > > >> molochko...@gmail.com> > > > > > >> wrote: > > > > > >> > > > > > >> > Dear Community, > > > > > >> > > > > > > >> > I have uploaded release candidate to > > > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > > > > >> > > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > > > > >> > > > > > > >> > The following staging can be used for testing: > > > > > >> > > > > > > >> https://repository.apache.org/content/repositories/ > > > > > orgapacheignite-1490/ > > > > > >> > > > > > > >> > Tag name is 2.9.1-rc1: > > > > > >> > > > > > > >> > > > > > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > > > > > h=refs/tags/2.9.1-rc1 > > > > > >> > > > > > > >> > 2.9.1 changes: > > > > > >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi > > > > > >> > * Added System view for binary metadata > > > > > >> > * Added System view for metastorage items > > > > > >> > * Added RebalancingPartitionsTotal metrics > > > > > >> > * Improved checkpoint concurrent behaviour > > > > > >> > * Fixed critical system error when unregister a JMX bean > > > > > >> > * Fixed IgniteCache#isClosed() returns false on server node > even > > > if > > > > > the > > > > > >> > cache had been closed before > > > > > >> > * Fixed inability to eagerly remove expired cache entries > > > > > >> > * Fixed partial index rebuild issue in case indexed cache > >
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Hello everyone! Yeah, guys, sorry, absolutely my mishap with docs. Denis, of course, i will see to it that docs are ready first and foremost. On Wed, Dec 16, 2020 at 8:30 PM Denis Magda wrote: > Hi Maxim, > > Ignite 2.9 docs were completed by the time we were running a vote for the > last release candidate. Once the vote passed, I released the docs through > the website. What happened next is an ongoing process of keeping the docs > actual - addressing users' feedback, merging generic changes to the master > and the latest release branch, etc. > > Anyway, speaking about 2.9.1. This is, in fact, a release blocker. > Otherwise, I wouldn't have cast the -1 vote. We're doing those features for > application developers who shouldn't consult with the Ignite source > codebase on how to leverage the new capabilities. > > But, I hear you. Let's make an exception this time, considering a small > number of documentation tasks. As the community, I do believe that we will > eventually develop a habit of preparing all necessary changes by the time a > vote starts. So, do we agree that the release won't be announced, and > binaries won't be referenced from the website until the docs are ready? My > guess the docs might be ready this or early next week. > > - > Denis > > > On Wed, Dec 16, 2020 at 7:00 AM Maxim Muzafarov wrote: > > > Denis, > > > > I remember the agreement, but also we are always fixing documentation > > pages even after a release announced (like for 2.9.0 and the > > ignite-2.9 release branch). Can we go the same way here? For instance, > > we can add all necessary documentation pages prior to the 2.9.1 wide > > announce. > > > > It doesn't seem to be the release blocker here, as the same as the > > checkstyle issues weren't for 2.9.0. Isn't it? > > > > On Wed, 16 Dec 2020 at 17:14, Denis Magda wrote: > > > > > > Yaroslav, thanks for checking, > > > > > > - 1 (binding) - I have to cast this vote as long as the docs need to be > > > ready by the time of the vote. > > > > > > Yaroslav, could you please help to prepare a draft with the > documentation > > > updates? Nikita, would you mind reviewing the changes? > > > > > > Denis > > > > > > On Wednesday, December 16, 2020, Yaroslav Molochkov < > > molochko...@gmail.com> > > > wrote: > > > > > > > Denis, actually, i'm mistaken, totally forgot about these: > > > > * Added System view for binary metadata > > > > * Added System view for metastorage items > > > > * Added RebalancingPartitionsTotal metrics > > > > > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov < > > molochko...@gmail.com> > > > > wrote: > > > > > > > > > Denis, hello! > > > > > > > > > > Since it's a minor bug-fixing release the update is not needed > > > > > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda > > wrote: > > > > > > > > > >> Hi Yaroslav, > > > > >> > > > > >> Do we need to update documentation? > > > > >> > > > > >> - > > > > >> Denis > > > > >> > > > > >> > > > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > > > > >> molochko...@gmail.com> > > > > >> wrote: > > > > >> > > > > >> > Dear Community, > > > > >> > > > > > >> > I have uploaded release candidate to > > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > > > >> > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > > > >> > > > > > >> > The following staging can be used for testing: > > > > >> > > > > > >> https://repository.apache.org/content/repositories/ > > > > orgapacheignite-1490/ > > > > >> > > > > > >> > Tag name is 2.9.1-rc1: > > > > >> > > > > > >> > > > > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > > > > h=refs/tags/2.9.1-rc1 > > > > >> > > > > > >> > 2.9.1 changes: > > > > >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi > > > > >> > * Added System view for binary metadata > > > > >> > * Added System view for metastorage items > > > > >> > * Added RebalancingPartitionsTotal metrics > > > > >> > * Improved checkpoint concurrent behaviour > > > > >> > * Fixed critical system error when unregister a JMX bean > > > > >> > * Fixed IgniteCache#isClosed() returns false on server node even > > if > > > > the > > > > >> > cache had been closed before > > > > >> > * Fixed inability to eagerly remove expired cache entries > > > > >> > * Fixed partial index rebuild issue in case indexed cache > contains > > > > >> > different datatypes > > > > >> > * Fixed local metastorage system view error if unmarshallable > > values > > > > >> > present > > > > >> > * Fixed deadlock between grid-timeout-worker and a thread > opening > > a > > > > >> > communication connection > > > > >> > * Fixed deadlock in IgniteServiceProcessor > > > > >> > * Fixed issue when rebalance future might hang in no final state > > > > though > > > > >> all > > > > >> > partitions are owned > > > > >> > * Fixed issue when scan query fails with an assertion error: > > > > Unexpected > > > > >> row > > > > >> > key > > > > >> > * Fixed issue with a
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Hi Maxim, Ignite 2.9 docs were completed by the time we were running a vote for the last release candidate. Once the vote passed, I released the docs through the website. What happened next is an ongoing process of keeping the docs actual - addressing users' feedback, merging generic changes to the master and the latest release branch, etc. Anyway, speaking about 2.9.1. This is, in fact, a release blocker. Otherwise, I wouldn't have cast the -1 vote. We're doing those features for application developers who shouldn't consult with the Ignite source codebase on how to leverage the new capabilities. But, I hear you. Let's make an exception this time, considering a small number of documentation tasks. As the community, I do believe that we will eventually develop a habit of preparing all necessary changes by the time a vote starts. So, do we agree that the release won't be announced, and binaries won't be referenced from the website until the docs are ready? My guess the docs might be ready this or early next week. - Denis On Wed, Dec 16, 2020 at 7:00 AM Maxim Muzafarov wrote: > Denis, > > I remember the agreement, but also we are always fixing documentation > pages even after a release announced (like for 2.9.0 and the > ignite-2.9 release branch). Can we go the same way here? For instance, > we can add all necessary documentation pages prior to the 2.9.1 wide > announce. > > It doesn't seem to be the release blocker here, as the same as the > checkstyle issues weren't for 2.9.0. Isn't it? > > On Wed, 16 Dec 2020 at 17:14, Denis Magda wrote: > > > > Yaroslav, thanks for checking, > > > > - 1 (binding) - I have to cast this vote as long as the docs need to be > > ready by the time of the vote. > > > > Yaroslav, could you please help to prepare a draft with the documentation > > updates? Nikita, would you mind reviewing the changes? > > > > Denis > > > > On Wednesday, December 16, 2020, Yaroslav Molochkov < > molochko...@gmail.com> > > wrote: > > > > > Denis, actually, i'm mistaken, totally forgot about these: > > > * Added System view for binary metadata > > > * Added System view for metastorage items > > > * Added RebalancingPartitionsTotal metrics > > > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov < > molochko...@gmail.com> > > > wrote: > > > > > > > Denis, hello! > > > > > > > > Since it's a minor bug-fixing release the update is not needed > > > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda > wrote: > > > > > > > >> Hi Yaroslav, > > > >> > > > >> Do we need to update documentation? > > > >> > > > >> - > > > >> Denis > > > >> > > > >> > > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > > > >> molochko...@gmail.com> > > > >> wrote: > > > >> > > > >> > Dear Community, > > > >> > > > > >> > I have uploaded release candidate to > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > > >> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > > >> > > > > >> > The following staging can be used for testing: > > > >> > > > > >> https://repository.apache.org/content/repositories/ > > > orgapacheignite-1490/ > > > >> > > > > >> > Tag name is 2.9.1-rc1: > > > >> > > > > >> > > > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > > > h=refs/tags/2.9.1-rc1 > > > >> > > > > >> > 2.9.1 changes: > > > >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi > > > >> > * Added System view for binary metadata > > > >> > * Added System view for metastorage items > > > >> > * Added RebalancingPartitionsTotal metrics > > > >> > * Improved checkpoint concurrent behaviour > > > >> > * Fixed critical system error when unregister a JMX bean > > > >> > * Fixed IgniteCache#isClosed() returns false on server node even > if > > > the > > > >> > cache had been closed before > > > >> > * Fixed inability to eagerly remove expired cache entries > > > >> > * Fixed partial index rebuild issue in case indexed cache contains > > > >> > different datatypes > > > >> > * Fixed local metastorage system view error if unmarshallable > values > > > >> > present > > > >> > * Fixed deadlock between grid-timeout-worker and a thread opening > a > > > >> > communication connection > > > >> > * Fixed deadlock in IgniteServiceProcessor > > > >> > * Fixed issue when rebalance future might hang in no final state > > > though > > > >> all > > > >> > partitions are owned > > > >> > * Fixed issue when scan query fails with an assertion error: > > > Unexpected > > > >> row > > > >> > key > > > >> > * Fixed issue with archiving and enabled wal compaction setting on > > > >> server > > > >> > restart > > > >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE > > > >> strategy > > > >> > * Fixed synchronization problems when different classloaders are > used > > > >> for > > > >> > deployment of same class > > > >> > * Fixed exception on SQL caches when client reconnect > > > >> > * Fixed deadlock on multiple cache delete > > > >> > * Fixed NPE in Ign
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Hi everyone, Denis, yes, I'll review the new documentation. Regards, Nikita ср, 16 дек. 2020 г. в 18:00, Maxim Muzafarov : > Denis, > > I remember the agreement, but also we are always fixing documentation > pages even after a release announced (like for 2.9.0 and the > ignite-2.9 release branch). Can we go the same way here? For instance, > we can add all necessary documentation pages prior to the 2.9.1 wide > announce. > > It doesn't seem to be the release blocker here, as the same as the > checkstyle issues weren't for 2.9.0. Isn't it? > > On Wed, 16 Dec 2020 at 17:14, Denis Magda wrote: > > > > Yaroslav, thanks for checking, > > > > - 1 (binding) - I have to cast this vote as long as the docs need to be > > ready by the time of the vote. > > > > Yaroslav, could you please help to prepare a draft with the documentation > > updates? Nikita, would you mind reviewing the changes? > > > > Denis > > > > On Wednesday, December 16, 2020, Yaroslav Molochkov < > molochko...@gmail.com> > > wrote: > > > > > Denis, actually, i'm mistaken, totally forgot about these: > > > * Added System view for binary metadata > > > * Added System view for metastorage items > > > * Added RebalancingPartitionsTotal metrics > > > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov < > molochko...@gmail.com> > > > wrote: > > > > > > > Denis, hello! > > > > > > > > Since it's a minor bug-fixing release the update is not needed > > > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda > wrote: > > > > > > > >> Hi Yaroslav, > > > >> > > > >> Do we need to update documentation? > > > >> > > > >> - > > > >> Denis > > > >> > > > >> > > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > > > >> molochko...@gmail.com> > > > >> wrote: > > > >> > > > >> > Dear Community, > > > >> > > > > >> > I have uploaded release candidate to > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > > >> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > > >> > > > > >> > The following staging can be used for testing: > > > >> > > > > >> https://repository.apache.org/content/repositories/ > > > orgapacheignite-1490/ > > > >> > > > > >> > Tag name is 2.9.1-rc1: > > > >> > > > > >> > > > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > > > h=refs/tags/2.9.1-rc1 > > > >> > > > > >> > 2.9.1 changes: > > > >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi > > > >> > * Added System view for binary metadata > > > >> > * Added System view for metastorage items > > > >> > * Added RebalancingPartitionsTotal metrics > > > >> > * Improved checkpoint concurrent behaviour > > > >> > * Fixed critical system error when unregister a JMX bean > > > >> > * Fixed IgniteCache#isClosed() returns false on server node even > if > > > the > > > >> > cache had been closed before > > > >> > * Fixed inability to eagerly remove expired cache entries > > > >> > * Fixed partial index rebuild issue in case indexed cache contains > > > >> > different datatypes > > > >> > * Fixed local metastorage system view error if unmarshallable > values > > > >> > present > > > >> > * Fixed deadlock between grid-timeout-worker and a thread opening > a > > > >> > communication connection > > > >> > * Fixed deadlock in IgniteServiceProcessor > > > >> > * Fixed issue when rebalance future might hang in no final state > > > though > > > >> all > > > >> > partitions are owned > > > >> > * Fixed issue when scan query fails with an assertion error: > > > Unexpected > > > >> row > > > >> > key > > > >> > * Fixed issue with archiving and enabled wal compaction setting on > > > >> server > > > >> > restart > > > >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE > > > >> strategy > > > >> > * Fixed synchronization problems when different classloaders are > used > > > >> for > > > >> > deployment of same class > > > >> > * Fixed exception on SQL caches when client reconnect > > > >> > * Fixed deadlock on multiple cache delete > > > >> > * Fixed NPE in IgniteServiceProcessor when destroying a cache > > > >> > * Fixed issue when DurableBackgroundTask can abandon incomplete > task > > > >> > * Fixed issue related to cache interceptor deserialization on > client > > > >> nodes > > > >> > * Fixed issue when control.sh doesn't start if JMX port was set > > > >> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator > can > > > >> return > > > >> > invalid node as coordinator > > > >> > * Fixed issue when valid blocking section in GridNioWorker and > > > >> > GridNioClientWorker leads to false positive blocking thread > detection > > > >> > * Fixed several logging issues > > > >> > * Fixed issue when exchange worker, waiting for new task from > queue, > > > >> > considered as blocked > > > >> > * Fixed incorrect topology snapshot logger output about > coordinator > > > >> change > > > >> > * Fixed slowdown during node initialization > > > >> > * Fixed incorrect usage of Class.isAssignableFrom in > Syst
[GitHub] [ignite-3] kgusakov commented on pull request #8: IGNITE-13857 Update java version to 11
kgusakov commented on pull request #8: URL: https://github.com/apache/ignite-3/pull/8#issuecomment-746534590 Merged This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [ignite-3] kgusakov closed pull request #8: IGNITE-13857 Update java version to 11
kgusakov closed pull request #8: URL: https://github.com/apache/ignite-3/pull/8 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] Ignite 3.0 development approach
Folks, I'm a little bit concerned about the simultaneous - existence of the repo https://github.com/apache/ignite-3 and PRs for that repo - and a couple of downvotes from PMC members. Is it all fine here? Was there any vote /discussion where it was discussed and consensus approved? What is the status of the ignite-3 repo? вт, 15 дек. 2020 г. в 17:30, Carbone, Adam : > I don't believe Java 7 was LTS, and I hope that others will have upgraded > long before that. If that is the release timeframe for 3.0, then I suppose > that would makes sense, I would still doubt that people would be going > newer than java 11, just my opinion of what I'm seeing. > > Regards > ~adam > > Adam Carbone | Director of Innovation – Intelligent Platform Team | > Bottomline Technologies > Office: 603-501-6446 | Mobile: 603-570-8418 > www.bottomline.com > > > > On 12/15/20, 4:25 AM, "Ilya Kasnacheev" > wrote: > > Hello! > > I guess Ignite 3.0 will be ready for production use somewhere in 2022, > realistically. By that time, Java 8 will be long enough out of support > so > that most companies will actually forbid its use, WRT vulnerabilities > et > all. > > After all we have managed to upgrade from Java 7 to Java 8 and only > got a > minor amount of complaints. > > Regards, > -- > Ilya Kasnacheev > > > пн, 14 дек. 2020 г. в 19:06, Carbone, Adam < > adam.carb...@bottomline.com>: > > > So just one bit to consider... Are there features that you need to > use in > > these newer versions of java? Or are we just updating to stay > current? The > > reason I ask is that there are still lots of people in an enterprise > space > > that are beholden to having to support legacy JAVAEE supported > applications > > on Websphere, Weblogic, Redhat, etc... and the organizations that > use those > > platforms are slow to move... Most of them are still on Java8 > > > > So as a platform I think a strong consideration needs to be towards > having > > the broadest possible support profile until it becomes an impediment > to > > doing things that the platform needs. So far I haven't seen huge > things in > > the newer versions of java that are must haves ( a few exceptions are > > things that would be really nice to take advantage of ). > > > > I think that apache commons has taken the right approach by staying > on > > java 8 giving the largest possible user base. > > > > Even standardizing on java 11 would have to make us reconsider > Ignite as > > the platform we are using, we are not so invested in it as of now, > even > > though we have big plans to leverage it. Just because we aren't sure > when > > we are going to be able to upgrade from java8. It has support > through 2022, > > so I imagine that is when we will be discussing that. > > > > Regards > > > > ~Adam > > > > Adam Carbone | Director of Innovation – Intelligent Platform Team | > > Bottomline Technologies > > Office: 603-501-6446 | Mobile: 603-570-8418 > > www.bottomline.com > > > > > > > > On 11/24/20, 7:38 AM, "Alexey Zinoviev" > wrote: > > > > Java 15 is better, VarHandles, ForeignMemory access and so on. > > > > In both cases, I support the Java version 11 and higher for the > > development! > > > > вт, 24 нояб. 2020 г. в 15:21, Andrey Mashenkov < > > andrey.mashen...@gmail.com>: > > > > > Let's add maven plugins for sanity checks at the early stage. > > > I've created a ticket for this [1]. > > > > > > Also, I've found initial pom.xml has a target version Java 8. > > > Do we intend to move to Java 11 (or may be next LTS) and drop > Java 8 > > in > > > Ignite 3.0? > > > > > > [1] > > > https://urldefense.com/v3/__https://issues.apache.org/jira/browse/IGNITE-13751__;!!O3mv9RujDHg!37ujwREhL1l-B3DmRXix6yaN1dE1KgH1Tx_tSl0eLZe4x1y0NnUlF4MzW5FeKAO2Ejs8$ > > > > > > On Tue, Nov 24, 2020 at 5:40 AM Valentin Kulichenko < > > > valentin.kuliche...@gmail.com> wrote: > > > > > > > Folks, > > > > > > > > I went ahead and created the repository [1]. I also > configured a > > TeamCity > > > > project [2] that runs all available JUnit tests on every PR > > creation or > > > > update. It also sends the status update to GitHub so that > it's > > reflected > > > in > > > > the PR itself so that we can do merges directly from GitHub. > Basic > > steps > > > to > > > > make a change are described on the Wiki page [3]. > > > > > > > > Let me know if you have any questions. > > > > > > > > [1] > > > https://urldefense.com/v3/__https://github.com/apache/ignite-3__;!!O3mv9RujDHg!37ujwREhL1l-B3DmRXix6yaN1dE1KgH1Tx_tSl0eLZe4x1y0NnUlF4MzW5FeKIq24lxF$ > >
Re: Hello
Hi Varvara, Thank you for your interest in Apache Ignite and welcome to the Apache Ignite Community. I've added a contributor role to the account, so now you should be able to assign a ticket. See also short intro how to contribute https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite Sincerely Dmitriy Pavlov ср, 16 дек. 2020 г. в 18:14, Varvara Kozhukhova : > Hello Ignite Community, > > My name is Varvara and I'm a Big Data junior developer with 3 months > experience. My current knowledge includes Hadoop, Spark, Kafka, Hive. > > I would like to take part in the Apache Ignite project and make a > contribution to it. > > I'm thinking to start with some easy fix or bugfix to get more acquainted > with the code. > > Could someone give me access, please, so that I will be able to book a > ticket. > > My Jira Id is saventune. > > >
Hello
Hello Ignite Community, My name is Varvara and I'm a Big Data junior developer with 3 months experience. My current knowledge includes Hadoop, Spark, Kafka, Hive. I would like to take part in the Apache Ignite project and make a contribution to it. I'm thinking to start with some easy fix or bugfix to get more acquainted with the code. Could someone give me access, please, so that I will be able to book a ticket. My Jira Id is saventune.
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Denis, I remember the agreement, but also we are always fixing documentation pages even after a release announced (like for 2.9.0 and the ignite-2.9 release branch). Can we go the same way here? For instance, we can add all necessary documentation pages prior to the 2.9.1 wide announce. It doesn't seem to be the release blocker here, as the same as the checkstyle issues weren't for 2.9.0. Isn't it? On Wed, 16 Dec 2020 at 17:14, Denis Magda wrote: > > Yaroslav, thanks for checking, > > - 1 (binding) - I have to cast this vote as long as the docs need to be > ready by the time of the vote. > > Yaroslav, could you please help to prepare a draft with the documentation > updates? Nikita, would you mind reviewing the changes? > > Denis > > On Wednesday, December 16, 2020, Yaroslav Molochkov > wrote: > > > Denis, actually, i'm mistaken, totally forgot about these: > > * Added System view for binary metadata > > * Added System view for metastorage items > > * Added RebalancingPartitionsTotal metrics > > > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov > > wrote: > > > > > Denis, hello! > > > > > > Since it's a minor bug-fixing release the update is not needed > > > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda wrote: > > > > > >> Hi Yaroslav, > > >> > > >> Do we need to update documentation? > > >> > > >> - > > >> Denis > > >> > > >> > > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > > >> molochko...@gmail.com> > > >> wrote: > > >> > > >> > Dear Community, > > >> > > > >> > I have uploaded release candidate to > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > >> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > >> > > > >> > The following staging can be used for testing: > > >> > > > >> https://repository.apache.org/content/repositories/ > > orgapacheignite-1490/ > > >> > > > >> > Tag name is 2.9.1-rc1: > > >> > > > >> > > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > > h=refs/tags/2.9.1-rc1 > > >> > > > >> > 2.9.1 changes: > > >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi > > >> > * Added System view for binary metadata > > >> > * Added System view for metastorage items > > >> > * Added RebalancingPartitionsTotal metrics > > >> > * Improved checkpoint concurrent behaviour > > >> > * Fixed critical system error when unregister a JMX bean > > >> > * Fixed IgniteCache#isClosed() returns false on server node even if > > the > > >> > cache had been closed before > > >> > * Fixed inability to eagerly remove expired cache entries > > >> > * Fixed partial index rebuild issue in case indexed cache contains > > >> > different datatypes > > >> > * Fixed local metastorage system view error if unmarshallable values > > >> > present > > >> > * Fixed deadlock between grid-timeout-worker and a thread opening a > > >> > communication connection > > >> > * Fixed deadlock in IgniteServiceProcessor > > >> > * Fixed issue when rebalance future might hang in no final state > > though > > >> all > > >> > partitions are owned > > >> > * Fixed issue when scan query fails with an assertion error: > > Unexpected > > >> row > > >> > key > > >> > * Fixed issue with archiving and enabled wal compaction setting on > > >> server > > >> > restart > > >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE > > >> strategy > > >> > * Fixed synchronization problems when different classloaders are used > > >> for > > >> > deployment of same class > > >> > * Fixed exception on SQL caches when client reconnect > > >> > * Fixed deadlock on multiple cache delete > > >> > * Fixed NPE in IgniteServiceProcessor when destroying a cache > > >> > * Fixed issue when DurableBackgroundTask can abandon incomplete task > > >> > * Fixed issue related to cache interceptor deserialization on client > > >> nodes > > >> > * Fixed issue when control.sh doesn't start if JMX port was set > > >> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can > > >> return > > >> > invalid node as coordinator > > >> > * Fixed issue when valid blocking section in GridNioWorker and > > >> > GridNioClientWorker leads to false positive blocking thread detection > > >> > * Fixed several logging issues > > >> > * Fixed issue when exchange worker, waiting for new task from queue, > > >> > considered as blocked > > >> > * Fixed incorrect topology snapshot logger output about coordinator > > >> change > > >> > * Fixed slowdown during node initialization > > >> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal > > and > > >> > SystemViewMBean classes > > >> > * Fixed several concurrent metrics issues > > >> > * Fixed issue related to incorrect work of predicates (< and >) in > > where > > >> > clause with compound primary key > > >> > * Removed unnecessary dependency to curator-client from and improved > > >> > ZookeeperDiscoverySpi > > >> > * Removed unnecessary failure trace in IgnitionEx > > >> > * Fixed issue when thin client conn
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Yaroslav, thanks for checking, - 1 (binding) - I have to cast this vote as long as the docs need to be ready by the time of the vote. Yaroslav, could you please help to prepare a draft with the documentation updates? Nikita, would you mind reviewing the changes? Denis On Wednesday, December 16, 2020, Yaroslav Molochkov wrote: > Denis, actually, i'm mistaken, totally forgot about these: > * Added System view for binary metadata > * Added System view for metastorage items > * Added RebalancingPartitionsTotal metrics > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov > wrote: > > > Denis, hello! > > > > Since it's a minor bug-fixing release the update is not needed > > > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda wrote: > > > >> Hi Yaroslav, > >> > >> Do we need to update documentation? > >> > >> - > >> Denis > >> > >> > >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < > >> molochko...@gmail.com> > >> wrote: > >> > >> > Dear Community, > >> > > >> > I have uploaded release candidate to > >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > >> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > >> > > >> > The following staging can be used for testing: > >> > > >> https://repository.apache.org/content/repositories/ > orgapacheignite-1490/ > >> > > >> > Tag name is 2.9.1-rc1: > >> > > >> > > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag; > h=refs/tags/2.9.1-rc1 > >> > > >> > 2.9.1 changes: > >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi > >> > * Added System view for binary metadata > >> > * Added System view for metastorage items > >> > * Added RebalancingPartitionsTotal metrics > >> > * Improved checkpoint concurrent behaviour > >> > * Fixed critical system error when unregister a JMX bean > >> > * Fixed IgniteCache#isClosed() returns false on server node even if > the > >> > cache had been closed before > >> > * Fixed inability to eagerly remove expired cache entries > >> > * Fixed partial index rebuild issue in case indexed cache contains > >> > different datatypes > >> > * Fixed local metastorage system view error if unmarshallable values > >> > present > >> > * Fixed deadlock between grid-timeout-worker and a thread opening a > >> > communication connection > >> > * Fixed deadlock in IgniteServiceProcessor > >> > * Fixed issue when rebalance future might hang in no final state > though > >> all > >> > partitions are owned > >> > * Fixed issue when scan query fails with an assertion error: > Unexpected > >> row > >> > key > >> > * Fixed issue with archiving and enabled wal compaction setting on > >> server > >> > restart > >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE > >> strategy > >> > * Fixed synchronization problems when different classloaders are used > >> for > >> > deployment of same class > >> > * Fixed exception on SQL caches when client reconnect > >> > * Fixed deadlock on multiple cache delete > >> > * Fixed NPE in IgniteServiceProcessor when destroying a cache > >> > * Fixed issue when DurableBackgroundTask can abandon incomplete task > >> > * Fixed issue related to cache interceptor deserialization on client > >> nodes > >> > * Fixed issue when control.sh doesn't start if JMX port was set > >> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can > >> return > >> > invalid node as coordinator > >> > * Fixed issue when valid blocking section in GridNioWorker and > >> > GridNioClientWorker leads to false positive blocking thread detection > >> > * Fixed several logging issues > >> > * Fixed issue when exchange worker, waiting for new task from queue, > >> > considered as blocked > >> > * Fixed incorrect topology snapshot logger output about coordinator > >> change > >> > * Fixed slowdown during node initialization > >> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal > and > >> > SystemViewMBean classes > >> > * Fixed several concurrent metrics issues > >> > * Fixed issue related to incorrect work of predicates (< and >) in > where > >> > clause with compound primary key > >> > * Removed unnecessary dependency to curator-client from and improved > >> > ZookeeperDiscoverySpi > >> > * Removed unnecessary failure trace in IgnitionEx > >> > * Fixed issue when thin client connect/disconnect during topology > update > >> > may lead to partition divergence in ignite-sys-cache > >> > * Fixed issue when thin client silently closes channel after > inactivity > >> > * Fixed unsupported protocol version exception when getting cache > >> > configuration from Java thin client > >> > * Fixed thin driver reports incorrect property names > >> > * Updated JDBC metadata to match actual capabilities > >> > * Improved slow Enum serialization > >> > * Fixed issue when deserializing IBinaryObject containing an > >> IBinaryObject > >> > field fails > >> > * Fixed issue TransactionImpl finalizer can crash the process > >> > * Fixed child processes become zombies when persi
[jira] [Created] (IGNITE-13865) .Net: DateTime can't be used as a cache key or value
Nikolay Izhikov created IGNITE-13865:
Summary: .Net: DateTime can't be used as a cache key or value
Key: IGNITE-13865
URL: https://issues.apache.org/jira/browse/IGNITE-13865
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
For now, DateTime can't be used as an interoperable cache key or value because
{{BinaryReflectiveSerializer#forceTimestamp}} works only for object fields.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSSION] Unified CLI tool
Hi, Valentin. PR is ready for review, some smoke tests added. On Sat, Dec 12, 2020 at 2:40 AM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Kirill, > > I've played with the tool a little bit and it looks great! I definitely > like the overall approach of a single script responsible for all the > operations. This should significantly improve the usability of the product. > > Looks like there is a significant amount of functionality already > implemented. I think we should merge the code to the main branch so that > any other contributors could also participate and build on top of it. What > do you think? Is the PR ready for review? > > -Val > > On Fri, Dec 11, 2020 at 8:55 AM Kirill Gusakov wrote: > > > Hi, everyone. > > > > I want to propose for discussion the PoC cli tool, which was born to > check > > and demonstrate approaches explained in [0] and [1]. > > This tool will be the all-in-one cli tool for ignite cluster management > and > > ignite installation/update. > > > > One unified tool will: > > - lower the entry threshold for Ignite newbies (it should be as simple as > > wget ignite && ignite init && ignite node start new-node) > > - be the one entry point for any ignite operation > > - be used for the smooth automated upgrade of local nodes and modules > > - use abstract REST API for communication with nodes in the future. so, > you > > can implement your own processes around this REST API if needed > > > > Work in progress PR can be found here > > https://github.com/apache/ignite-3/pull/4 > > > > You can: > > - see a small demo here https://asciinema.org/a/378647 > > - build it from the PR and try it by yourself > > > > For building it from the sources and have a fully working demo setup you > > need firstly: > > - "mvn install" the root dir here > > https://github.com/apache/ignite-3/pull/5 > > - "mvn install" the root dir here > > https://github.com/apache/ignite-3/pull/6 > > - "mvn install" tool itself from > https://github.com/apache/ignite-3/pull/4 > > > > > > [0] > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158873958 > > [1] > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration > > >
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
+1 (binding) > 16 дек. 2020 г., в 13:13, Yaroslav Molochkov > написал(а): > > Denis, actually, i'm mistaken, totally forgot about these: > * Added System view for binary metadata > * Added System view for metastorage items > * Added RebalancingPartitionsTotal metrics > > On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov > wrote: > >> Denis, hello! >> >> Since it's a minor bug-fixing release the update is not needed >> >> On Tue, Dec 15, 2020 at 9:38 PM Denis Magda wrote: >> >>> Hi Yaroslav, >>> >>> Do we need to update documentation? >>> >>> - >>> Denis >>> >>> >>> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < >>> molochko...@gmail.com> >>> wrote: >>> Dear Community, I have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ The following staging can be used for testing: >>> https://repository.apache.org/content/repositories/orgapacheignite-1490/ Tag name is 2.9.1-rc1: >>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.9.1-rc1 2.9.1 changes: * Added support to graceful shutdown for ZookeeperDiscoverySpi * Added System view for binary metadata * Added System view for metastorage items * Added RebalancingPartitionsTotal metrics * Improved checkpoint concurrent behaviour * Fixed critical system error when unregister a JMX bean * Fixed IgniteCache#isClosed() returns false on server node even if the cache had been closed before * Fixed inability to eagerly remove expired cache entries * Fixed partial index rebuild issue in case indexed cache contains different datatypes * Fixed local metastorage system view error if unmarshallable values present * Fixed deadlock between grid-timeout-worker and a thread opening a communication connection * Fixed deadlock in IgniteServiceProcessor * Fixed issue when rebalance future might hang in no final state though >>> all partitions are owned * Fixed issue when scan query fails with an assertion error: Unexpected >>> row key * Fixed issue with archiving and enabled wal compaction setting on >>> server restart * Fixed NPE during Cassandra Store initialization with PRIMITIVE >>> strategy * Fixed synchronization problems when different classloaders are used >>> for deployment of same class * Fixed exception on SQL caches when client reconnect * Fixed deadlock on multiple cache delete * Fixed NPE in IgniteServiceProcessor when destroying a cache * Fixed issue when DurableBackgroundTask can abandon incomplete task * Fixed issue related to cache interceptor deserialization on client >>> nodes * Fixed issue when control.sh doesn't start if JMX port was set * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can >>> return invalid node as coordinator * Fixed issue when valid blocking section in GridNioWorker and GridNioClientWorker leads to false positive blocking thread detection * Fixed several logging issues * Fixed issue when exchange worker, waiting for new task from queue, considered as blocked * Fixed incorrect topology snapshot logger output about coordinator >>> change * Fixed slowdown during node initialization * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal and SystemViewMBean classes * Fixed several concurrent metrics issues * Fixed issue related to incorrect work of predicates (< and >) in where clause with compound primary key * Removed unnecessary dependency to curator-client from and improved ZookeeperDiscoverySpi * Removed unnecessary failure trace in IgnitionEx * Fixed issue when thin client connect/disconnect during topology update may lead to partition divergence in ignite-sys-cache * Fixed issue when thin client silently closes channel after inactivity * Fixed unsupported protocol version exception when getting cache configuration from Java thin client * Fixed thin driver reports incorrect property names * Updated JDBC metadata to match actual capabilities * Improved slow Enum serialization * Fixed issue when deserializing IBinaryObject containing an >>> IBinaryObject field fails * Fixed issue TransactionImpl finalizer can crash the process * Fixed child processes become zombies when persistence is used with direct-io on Linux * Added Windows support to CMake build system * Fixed issue when odbc-example loses values if run with 1 additional >>> node RELEASE NOTES: >>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;hb=ignite-2.9.1 Complete list of resolved issues: >>> https://issues.apache.org/jira/browse/IGNITE-13770?jql=proje
[jira] [Created] (IGNITE-13864) Assertion error happens on stale latch's acknowledge
Vladislav Pyatkov created IGNITE-13864:
--
Summary: Assertion error happens on stale latch's acknowledge
Key: IGNITE-13864
URL: https://issues.apache.org/jira/browse/IGNITE-13864
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
There are several Assertion errors on TC logs, they are bounded with exchange
latch.
Seem it happens because latch manager is not handling stale acknowledge.
{noformat}
{{[18:39:26]W: [org.gridgain:ignite-core] [2020-03-26
18:39:26,680][ERROR][sys-#53190%distributed.CacheLoadingConcurrentGridStartSelfTest2%][GridIoManager]
An error occurred processing the message [msg=GridIoMessage [plc=2,
topic=TOPIC_EXCHANGE, topicOrd=31, or
dered=false, timeout=0, skipOnTimeout=false,
msg=org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.LatchAckMessage@779ce9da],
nodeId=5bd19ec1-da96-41a1-a3e0-ebb55321].
[18:39:26]W: [org.gridgain:ignite-core] java.lang.AssertionError
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.processAck(ExchangeLatchManager.java:399)
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.lambda$new$0(ExchangeLatchManager.java:119)
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1654)
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1274)
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4500(GridIoManager.java:145)
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.managers.communication.GridIoManager$8.execute(GridIoManager.java:1159)
[18:39:26]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:50)
[18:39:26]W: [org.gridgain:ignite-core] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[18:39:26]W: [org.gridgain:ignite-core] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[18:39:26]W: [org.gridgain:ignite-core] at
java.lang.Thread.run(Thread.java:748)}}
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Denis, actually, i'm mistaken, totally forgot about these: * Added System view for binary metadata * Added System view for metastorage items * Added RebalancingPartitionsTotal metrics On Wed, Dec 16, 2020 at 1:03 PM Yaroslav Molochkov wrote: > Denis, hello! > > Since it's a minor bug-fixing release the update is not needed > > On Tue, Dec 15, 2020 at 9:38 PM Denis Magda wrote: > >> Hi Yaroslav, >> >> Do we need to update documentation? >> >> - >> Denis >> >> >> On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov < >> molochko...@gmail.com> >> wrote: >> >> > Dear Community, >> > >> > I have uploaded release candidate to >> > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ >> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ >> > >> > The following staging can be used for testing: >> > >> https://repository.apache.org/content/repositories/orgapacheignite-1490/ >> > >> > Tag name is 2.9.1-rc1: >> > >> > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.9.1-rc1 >> > >> > 2.9.1 changes: >> > * Added support to graceful shutdown for ZookeeperDiscoverySpi >> > * Added System view for binary metadata >> > * Added System view for metastorage items >> > * Added RebalancingPartitionsTotal metrics >> > * Improved checkpoint concurrent behaviour >> > * Fixed critical system error when unregister a JMX bean >> > * Fixed IgniteCache#isClosed() returns false on server node even if the >> > cache had been closed before >> > * Fixed inability to eagerly remove expired cache entries >> > * Fixed partial index rebuild issue in case indexed cache contains >> > different datatypes >> > * Fixed local metastorage system view error if unmarshallable values >> > present >> > * Fixed deadlock between grid-timeout-worker and a thread opening a >> > communication connection >> > * Fixed deadlock in IgniteServiceProcessor >> > * Fixed issue when rebalance future might hang in no final state though >> all >> > partitions are owned >> > * Fixed issue when scan query fails with an assertion error: Unexpected >> row >> > key >> > * Fixed issue with archiving and enabled wal compaction setting on >> server >> > restart >> > * Fixed NPE during Cassandra Store initialization with PRIMITIVE >> strategy >> > * Fixed synchronization problems when different classloaders are used >> for >> > deployment of same class >> > * Fixed exception on SQL caches when client reconnect >> > * Fixed deadlock on multiple cache delete >> > * Fixed NPE in IgniteServiceProcessor when destroying a cache >> > * Fixed issue when DurableBackgroundTask can abandon incomplete task >> > * Fixed issue related to cache interceptor deserialization on client >> nodes >> > * Fixed issue when control.sh doesn't start if JMX port was set >> > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can >> return >> > invalid node as coordinator >> > * Fixed issue when valid blocking section in GridNioWorker and >> > GridNioClientWorker leads to false positive blocking thread detection >> > * Fixed several logging issues >> > * Fixed issue when exchange worker, waiting for new task from queue, >> > considered as blocked >> > * Fixed incorrect topology snapshot logger output about coordinator >> change >> > * Fixed slowdown during node initialization >> > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal and >> > SystemViewMBean classes >> > * Fixed several concurrent metrics issues >> > * Fixed issue related to incorrect work of predicates (< and >) in where >> > clause with compound primary key >> > * Removed unnecessary dependency to curator-client from and improved >> > ZookeeperDiscoverySpi >> > * Removed unnecessary failure trace in IgnitionEx >> > * Fixed issue when thin client connect/disconnect during topology update >> > may lead to partition divergence in ignite-sys-cache >> > * Fixed issue when thin client silently closes channel after inactivity >> > * Fixed unsupported protocol version exception when getting cache >> > configuration from Java thin client >> > * Fixed thin driver reports incorrect property names >> > * Updated JDBC metadata to match actual capabilities >> > * Improved slow Enum serialization >> > * Fixed issue when deserializing IBinaryObject containing an >> IBinaryObject >> > field fails >> > * Fixed issue TransactionImpl finalizer can crash the process >> > * Fixed child processes become zombies when persistence is used with >> > direct-io on Linux >> > * Added Windows support to CMake build system >> > * Fixed issue when odbc-example loses values if run with 1 additional >> node >> > >> > RELEASE NOTES: >> > >> > >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;hb=ignite-2.9.1 >> > >> > Complete list of resolved issues: >> > >> > >> https://issues.apache.org/jira/browse/IGNITE-13770?jql=project%20%3D%20IGNITE%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.9.1 >> > >> > DEVNOTES >> > >> > >> https://gitbox.apache
Re: [VOTE] Release Apache Ignite 2.9.1 RC1
Denis, hello! Since it's a minor bug-fixing release the update is not needed On Tue, Dec 15, 2020 at 9:38 PM Denis Magda wrote: > Hi Yaroslav, > > Do we need to update documentation? > > - > Denis > > > On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov > > wrote: > > > Dear Community, > > > > I have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/ > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.9.1-rc1/ > > > > The following staging can be used for testing: > > https://repository.apache.org/content/repositories/orgapacheignite-1490/ > > > > Tag name is 2.9.1-rc1: > > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.9.1-rc1 > > > > 2.9.1 changes: > > * Added support to graceful shutdown for ZookeeperDiscoverySpi > > * Added System view for binary metadata > > * Added System view for metastorage items > > * Added RebalancingPartitionsTotal metrics > > * Improved checkpoint concurrent behaviour > > * Fixed critical system error when unregister a JMX bean > > * Fixed IgniteCache#isClosed() returns false on server node even if the > > cache had been closed before > > * Fixed inability to eagerly remove expired cache entries > > * Fixed partial index rebuild issue in case indexed cache contains > > different datatypes > > * Fixed local metastorage system view error if unmarshallable values > > present > > * Fixed deadlock between grid-timeout-worker and a thread opening a > > communication connection > > * Fixed deadlock in IgniteServiceProcessor > > * Fixed issue when rebalance future might hang in no final state though > all > > partitions are owned > > * Fixed issue when scan query fails with an assertion error: Unexpected > row > > key > > * Fixed issue with archiving and enabled wal compaction setting on server > > restart > > * Fixed NPE during Cassandra Store initialization with PRIMITIVE strategy > > * Fixed synchronization problems when different classloaders are used for > > deployment of same class > > * Fixed exception on SQL caches when client reconnect > > * Fixed deadlock on multiple cache delete > > * Fixed NPE in IgniteServiceProcessor when destroying a cache > > * Fixed issue when DurableBackgroundTask can abandon incomplete task > > * Fixed issue related to cache interceptor deserialization on client > nodes > > * Fixed issue when control.sh doesn't start if JMX port was set > > * Fixed issue when ZookeeperDiscoverySpiMBeanImpl#getCoordinator can > return > > invalid node as coordinator > > * Fixed issue when valid blocking section in GridNioWorker and > > GridNioClientWorker leads to false positive blocking thread detection > > * Fixed several logging issues > > * Fixed issue when exchange worker, waiting for new task from queue, > > considered as blocked > > * Fixed incorrect topology snapshot logger output about coordinator > change > > * Fixed slowdown during node initialization > > * Fixed incorrect usage of Class.isAssignableFrom in SystemViewLocal and > > SystemViewMBean classes > > * Fixed several concurrent metrics issues > > * Fixed issue related to incorrect work of predicates (< and >) in where > > clause with compound primary key > > * Removed unnecessary dependency to curator-client from and improved > > ZookeeperDiscoverySpi > > * Removed unnecessary failure trace in IgnitionEx > > * Fixed issue when thin client connect/disconnect during topology update > > may lead to partition divergence in ignite-sys-cache > > * Fixed issue when thin client silently closes channel after inactivity > > * Fixed unsupported protocol version exception when getting cache > > configuration from Java thin client > > * Fixed thin driver reports incorrect property names > > * Updated JDBC metadata to match actual capabilities > > * Improved slow Enum serialization > > * Fixed issue when deserializing IBinaryObject containing an > IBinaryObject > > field fails > > * Fixed issue TransactionImpl finalizer can crash the process > > * Fixed child processes become zombies when persistence is used with > > direct-io on Linux > > * Added Windows support to CMake build system > > * Fixed issue when odbc-example loses values if run with 1 additional > node > > > > RELEASE NOTES: > > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;hb=ignite-2.9.1 > > > > Complete list of resolved issues: > > > > > https://issues.apache.org/jira/browse/IGNITE-13770?jql=project%20%3D%20IGNITE%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.9.1 > > > > DEVNOTES > > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.9.1 > > > > The vote is formal, see voting guidelines > > https://www.apache.org/foundation/voting.html > > > > +1 - to accept Apache Ignite 2.9.1-rc1 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite Ignite 2.9.1-rc1 (explain why) > > > > See notes on how to verify release here > > https://www.apache.org/info/verif
[jira] [Created] (IGNITE-13863) Python thin client hangs when object has Boolean field
Igor Sapego created IGNITE-13863:
Summary: Python thin client hangs when object has Boolean field
Key: IGNITE-13863
URL: https://issues.apache.org/jira/browse/IGNITE-13863
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.9
Reporter: Igor Sapego
Assignee: Igor Sapego
The first run of python client returns empty result set, all consequence runs
just hang:
{code:java}
from pygridgain import Client, GenericObjectMeta
import collections
from pygridgain.datatypes import *
if __name__ == '__main__':
client = Client()
client.connect('localhost', 10800)
cache = client.get_cache('Batch')
#client.register_binary_type(BatchConfigurationPK)
#client.register_binary_type(BatchConfiguration)
result = cache.scan()
print([b for b in result])
{code}
{code:java}
public class ObjectTest {
@QuerySqlField
private String field1;
@QuerySqlField
private String field2;
@QuerySqlField
private String field3;
@QuerySqlField
private String field4;
@QuerySqlField
private Boolean enabled;
public ObjectTest(String field1, String field2, String field3) {
this.field1 = field1;
this.field2 = field2;
this.field3 = field3;
}
}
{code}
{code:java}
public static void main(String[] args) throws IgniteException {
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
IgniteCache cache = ignite.getOrCreateCache("Batch");
for (int i = 0; i < 100; i++) {
cache.put(i, new ObjectTest("" + i, "" + i, "" + i));
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13862) Python Thin Client: put_all operation on a huge dictionary (say 10000 keys) results in connection timeout, same happens with multiple consecutive put operations using a
Archita Sukhwani created IGNITE-13862: - Summary: Python Thin Client: put_all operation on a huge dictionary (say 1 keys) results in connection timeout, same happens with multiple consecutive put operations using a for loop unless a sleep statement is put. Key: IGNITE-13862 URL: https://issues.apache.org/jira/browse/IGNITE-13862 Project: Ignite Issue Type: Bug Components: python, thin client Reporter: Archita Sukhwani [Reproducible code|https://stackoverflow.com/questions/65303573/pyignite-connection-timeout-error-when-trying-to-load-json-into-cache-using-put] -- This message was sent by Atlassian Jira (v8.3.4#803005)
