Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Maxim, https://issues.apache.org/jira/browse/IGNITE-13873 Is ready for review, is it possible to wait for it? On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov wrote: > Folks, > > > I'd like to cherry-pick to the release branch the following fixes: > > Fix security context for JDBC bulk-load operations > https://issues.apache.org/jira/browse/IGNITE-13472 > > Fixed an issue that caused a deadlock when user cache was created in > parallel with TTL worker was in progress. > https://issues.apache.org/jira/browse/IGNITE-14078 > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov wrote: > > > > Maxim, Igor, > > > > Thanks for sharing details. > > Let's wait for these fixes. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > [2] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego wrote: > > > > > > Maxim, > > > > > > I believe I could fix the ticket [1] by the end of the next week. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > Best Regards, > > > Igor > > > > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin > wrote: > > > > > > > Hi! I've today found an issue [1], there is wrong handling of > inlined POJO. > > > > This bug appeared in 2.9.0 and makes it impossible to work with > > > > multi-column indexes created on old AI versions that contain inlined > POJO > > > > keys in the middle. > > > > > > > > I'm working on the fix and asked Konstantin Orlov to review it. I > think > > > > that it will take only a couple of days to fix this issue. From my > side, it > > > > looks like a release blocker, but we've been living with that since > 2.9.0. > > > > WDYT if the release can wait for the fix? > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov > wrote: > > > > > > > > > Folks, > > > > > > > > > > > > > > > Do we have any estimations of how long does it take to fix the > issue > > > > > [1] in C++ thin client? The bug must be fixed for sure, however, I > > > > > tend to continue with the release (if fixing the bug require a few > > > > > weeks) and prepare a batch of fixes for the 2.10.1. > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev < > ilya.kasnach...@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > > Hello! > > > > > > > > > > > > There was a ticket filed about the new feature, transactions in > C++ > > > > thin > > > > > > client, making this feature unusable if there's more than one > > > > connection > > > > > > endpoint: > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > > > I don't think this is a genuine blocker for 2.10, since there is > a > > > > > > workaround (use just one endpoint), nevertheless it is a critical > > > > crasher > > > > > > bug, so I wonder if Igor could take a look at it promptly, > include the > > > > > fix > > > > > > in 2.10. > > > > > > > > > > > > Regards, > > > > > > -- > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky > > > > > > > > > > >: > > > > > > > > > > > > > > > > > > > > > > > > > > > I fill the ticket with drop problem, plz take a look [1] > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14205 > > > > > > > > > > > > > > >Ilya, > > > > > > > > > > > > > > > >Thanks! > > > > > > > >I've added this step to the Release Process wiki page also > [1]. > > > > > > > > > > > > > > > >[1] > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization > > > > > > > > > > > > > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com > > > > > > > > wrote: > > > > > > > >> > > > > > > > >> Hello! > > > > > > > >> > > > > > > > >> I have added ignite-2.10 to Nightly build triggering. I > hope we > > > > will > > > > > > > have a > > > > > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier. > > > > > > > >> > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.10&buildTypeTab=overview&mode=builds > > > > > > > >> > > > > > > > >> Regards, > > > > > > > >> -- > > > > > > > >> Ilya Kasnacheev > > > > > > > >> > > > > > > > >> > > > > > > > >> ср, 17 февр. 2021 г. в 17:37, Maxim Muzafarov < > mmu...@apache.org > > > > > >: > > > > > > > >> > > > > > > > >> > Folks, > > > > > > > >> > > > > > > > > >> > There is a possible issue with the performance for 2.9.1 > vs > > > > 2.10. > > > > > I'm > > > > > > > >> > trying to reproduce on a stress-testing environment. > > > > > > > >> > [1] > > > > > > > >> > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/download/attachments/165224767/atomicPutRandomValueFullSync.jp
Re: Apache Ignite 3.x: order in repository
I'd guess that one of the main problem with inactive PRs is in creation of PR for reviewing but merging it from command line (not via GitHub interface). Also, of course, there are lots of efforts which are abandoned after first review, or even do not have a chance to be reviewed at all. > On 22 Feb 2021, at 11:51, Stephen Darlington > wrote: > > I think we need to be able answer the question “Why are there so many > inactive PRs?" before we automate their removal. If perfectly good changes > are being ignored, we have a problem. > > Removing branches of merged PRs and protecting the main branch make sense. > >> On 20 Feb 2021, at 18:30, Pavel Tupitsyn wrote: >> >> +1 >> >> - Close inactive PRs (1 month or so?) >> - Enable main branch protection (no force pushes, require linear history, >> require status checks) >> >> On Sat, Feb 20, 2021 at 2:31 PM Petr Ivanov wrote: >> >>> Hi, Igniters! >>> >>> >>> When we started Ignite 3.x in new repository, not only we have received a >>> chance to cleanup codebase, but to maintain some order in development >>> tools, like GitHub. >>> Currently in 2.x repository we have lots of stalled PRs and branches, >>> which not only clog the repository, but also indirectly influence TC >>> performance (due to necessity to check for updates every ref: branches and >>> PRs). >>> >>> Could I suggest we devise some recommendations for using PR's and branches >>> in new repo and add some rules about stalled PRs at least, like closing >>> them if inactive for some time. >>> Also we can activate some settings in repo's configuration, like auto >>> delete branch after PR is merged. >>> >>> >>> WDYT? > >
[jira] [Created] (IGNITE-14226) Ducktape test of rebalance
Dmitriy Sorokin created IGNITE-14226: Summary: Ducktape test of rebalance Key: IGNITE-14226 URL: https://issues.apache.org/jira/browse/IGNITE-14226 Project: Ignite Issue Type: Test Reporter: Dmitriy Sorokin Assignee: Dmitriy Sorokin The test should check the rebalance on both in-memory caches and persistent caches. In case of persistent caches, the test also should check both modes of rebalance: full and the historical (asserts is needed that the proper mode of rebalance was worked). Basic scenario: Testing of rebalance triggered by two event types: node enter and node leave (baseline change if persistent mode). Extended scenario: Node entering or leaving during rebalance process. Test parameters: # Initial node count; # Cache count; # Cache entry count; # Cache entry size; # Mode: in-memory or persistence; # Rebalance trigger event: node enter or node leave. Test result: time taken to rebalance process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14227) Partition map exchange may hang if the cluster is deactivated during cache start failure handling.
b-bde2-576e1e70, consistentId=9bc35ede-4ab7-44cb-9d15-0d7215350ed3, addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1614163031766, loc=false, ver=2.11.0#20210224-sha1:, isClient=false], topVer=2, msgTemplate=null, span=o.a.i.i.processors.tracing.NoopSpan@7e02a8f5, nodeId8=02c46b75, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1614163031926]], nodeId=b05182d2, evt=DISCOVERY_CUSTOM_EVT], caches=[o.a.i.i.processors.cache.ExchangeActions$CacheGroupActionData@50838b34]] class org.apache.ignite.IgniteCheckedException: Requested DataRegion is not configured: absent at org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.dataRegion(IgniteCacheDatabaseSharedManager.java:911) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:2467) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.getOrCreateCacheGroupContext(GridCacheProcessor.java:2205) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:2012) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1946) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1821) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCachesIfPossible$14(GridCacheProcessor.java:1791) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1818) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCachesIfPossible(GridCacheProcessor.java:1789) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:996) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:882) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1450) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:948) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3387) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3209) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at java.lang.Thread.run(Thread.java:748) [2021-02-24 13:37:11,945][ERROR][exchange-worker-#61%cache.DynamicCacheStartFailTest0%][GridDhtPartitionsExchangeFuture] Failed to initialize cache(s) (will try to rollback) [exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=2], discoEvt=DiscoveryCustomEvent [customMsg=DynamicCacheChangeBatch [id=af52d93d771-bd608b2d-8308-4556-9f9f-91bae6049b7c, reqs=ArrayList [DynamicCacheChangeRequest [cacheName=cache1, hasCfg=true, nodeId=b05182d2-c6e8-4b5b-bde2-576e1e70, clientStartOnly=false, stop=false, destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions [startCaches=[cache1], stopCaches=null, startGrps=[cache1], stopGrps=[], resetParts=null, stateChangeRequest=null], startCaches=false], affTopVer=AffinityTopologyVersion [topVer=2, minorTopVer=2], super=DiscoveryEvent [evtNode=TcpDiscoveryNode [id=b05182d2-c6e8-4b5b-bde2-576e1e70, consistentId=9bc35ede-4ab7-44cb-9d15-0d7215350ed3, addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1614163031926, loc=true, ver=2.11.0#20210224-sha1:, isClient=false], topVer=2, msgTemplate=null, span=o.a.i.i.processors.tracing.NoopSpan@7e02a8f5, nodeId8=b05182d2, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1614163031926]], nodeId=b05182d2, evt=DISCOVERY_CUSTOM_EVT], caches=[o.a.i.i.processors.cache.ExchangeActions$CacheGroupActionData@cc19771]] class org.apache.ignite.IgniteCheckedException: Requested DataRegion is not configured: absent at org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.dataRegion(IgniteCacheDatabaseSharedManager.java:911) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:2467) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.getOrCreateCacheGroupContext(GridCacheProcessor.java:2205) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.pr
[jira] [Created] (IGNITE-14228) Ducktape test of rebalance for in-memory mode
Dmitriy Sorokin created IGNITE-14228: Summary: Ducktape test of rebalance for in-memory mode Key: IGNITE-14228 URL: https://issues.apache.org/jira/browse/IGNITE-14228 Project: Ignite Issue Type: Sub-task Reporter: Dmitriy Sorokin Assignee: Dmitriy Sorokin This test should check the rebalance on in-memory caches in basic scenario. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14229) Calcite bug. Engine can hangs
Yury Gerzhedovich created IGNITE-14229:
--
Summary: Calcite bug. Engine can hangs
Key: IGNITE-14229
URL: https://issues.apache.org/jira/browse/IGNITE-14229
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Yury Gerzhedovich
The Calcite SQL engine can hang during query execution due to some Exception
which not properly handled.
For example, try to execute query 'select reverse('NAME') from person'. As
result will be following exception and hangs execution.
{code:java}
java.lang.NullPointerException
at
org.apache.calcite.rex.RexBuilder.deriveReturnType(RexBuilder.java:283)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJson.toRex(RelJson.java:444)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader$RelInputImpl.getExpressionList(RelJsonReader.java:239)
at
org.apache.ignite.internal.processors.query.calcite.trait.TraitUtils$1.getExpressionList(TraitUtils.java:308)
at
org.apache.ignite.internal.processors.query.calcite.rel.ProjectableFilterableTableScan.(ProjectableFilterableTableScan.java:85)
at
org.apache.ignite.internal.processors.query.calcite.rel.IgniteTableScan.(IgniteTableScan.java:46)
at SC.apply(Unknown Source)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJson$RelFactory.apply(RelJson.java:115)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.readRel(RelJsonReader.java:112)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.readRels(RelJsonReader.java:104)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.read(RelJsonReader.java:93)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.fromJson(RelJsonReader.java:78)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareFragment(ExecutionServiceImpl.java:528)
at
org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.onMessage(ExecutionServiceImpl.java:847)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.lambda$init$1(ExecutionServiceImpl.java:440)
at
org.apache.ignite.internal.processors.query.calcite.message.MessageServiceImpl.onMessageInternal(MessageServiceImpl.java:276)
at
org.apache.ignite.internal.processors.query.calcite.message.MessageServiceImpl.lambda$onMessage$0(MessageServiceImpl.java:256)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[2021-02-24
17:04:40,816][ERROR][calciteQry-#265%calcite.AggregatesIntegrationTest1%][IgniteTestResources]
Critical system error detected. Will be handled accordingly to configured
handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED,
SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext
[type=CRITICAL_ERROR, err=java.lang.NullPointerException]]
java.lang.NullPointerException
at
org.apache.calcite.rex.RexBuilder.deriveReturnType(RexBuilder.java:283)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJson.toRex(RelJson.java:444)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader$RelInputImpl.getExpressionList(RelJsonReader.java:239)
at
org.apache.ignite.internal.processors.query.calcite.trait.TraitUtils$1.getExpressionList(TraitUtils.java:308)
at
org.apache.ignite.internal.processors.query.calcite.rel.ProjectableFilterableTableScan.(ProjectableFilterableTableScan.java:85)
at
org.apache.ignite.internal.processors.query.calcite.rel.IgniteTableScan.(IgniteTableScan.java:46)
at SC.apply(Unknown Source)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJson$RelFactory.apply(RelJson.java:115)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.readRel(RelJsonReader.java:112)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.readRels(RelJsonReader.java:104)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.read(RelJsonReader.java:93)
at
org.apache.ignite.internal.processors.query.calcite.externalize.RelJsonReader.fromJson(RelJsonReader.java:78)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareFragment(ExecutionServiceImpl.java:528)
[jira] [Created] (IGNITE-14230) Port DynamicConfiguration to new underlying configuration framework.
Ivan Bessonov created IGNITE-14230: -- Summary: Port DynamicConfiguration to new underlying configuration framework. Key: IGNITE-14230 URL: https://issues.apache.org/jira/browse/IGNITE-14230 Project: Ignite Issue Type: Sub-task Reporter: Ivan Bessonov Assignee: Ivan Bessonov -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Re[2]: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Anton, Your improvement is very important, for sure, but it's almost 2 months have passed since the initiation of the release branch. I think we should prepare the changes as fast as possible for now and initiate with the next one release. In general, it would be nice to have a release plan for the year ahead so each developer will understand on which release his changes can get into. That's why I'm going to prepare an RC-build on Monday 1-st March. On Wed, 24 Feb 2021 at 11:13, Anton Vinogradov wrote: > > Maxim, > > https://issues.apache.org/jira/browse/IGNITE-13873 > Is ready for review, is it possible to wait for it? > > On Wed, Feb 24, 2021 at 12:01 AM Maxim Muzafarov wrote: > > > Folks, > > > > > > I'd like to cherry-pick to the release branch the following fixes: > > > > Fix security context for JDBC bulk-load operations > > https://issues.apache.org/jira/browse/IGNITE-13472 > > > > Fixed an issue that caused a deadlock when user cache was created in > > parallel with TTL worker was in progress. > > https://issues.apache.org/jira/browse/IGNITE-14078 > > > > On Thu, 18 Feb 2021 at 20:26, Maxim Muzafarov wrote: > > > > > > Maxim, Igor, > > > > > > Thanks for sharing details. > > > Let's wait for these fixes. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > > [2] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > On Thu, 18 Feb 2021 at 18:35, Igor Sapego wrote: > > > > > > > > Maxim, > > > > > > > > I believe I could fix the ticket [1] by the end of the next week. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > Best Regards, > > > > Igor > > > > > > > > > > > > On Thu, Feb 18, 2021 at 6:30 PM Max Timonin > > wrote: > > > > > > > > > Hi! I've today found an issue [1], there is wrong handling of > > inlined POJO. > > > > > This bug appeared in 2.9.0 and makes it impossible to work with > > > > > multi-column indexes created on old AI versions that contain inlined > > POJO > > > > > keys in the middle. > > > > > > > > > > I'm working on the fix and asked Konstantin Orlov to review it. I > > think > > > > > that it will take only a couple of days to fix this issue. From my > > side, it > > > > > looks like a release blocker, but we've been living with that since > > 2.9.0. > > > > > WDYT if the release can wait for the fix? > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14206 > > > > > > > > > > On Thu, Feb 18, 2021 at 5:38 PM Maxim Muzafarov > > wrote: > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > > > Do we have any estimations of how long does it take to fix the > > issue > > > > > > [1] in C++ thin client? The bug must be fixed for sure, however, I > > > > > > tend to continue with the release (if fixing the bug require a few > > > > > > weeks) and prepare a batch of fixes for the 2.10.1. > > > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > > > On Thu, 18 Feb 2021 at 13:22, Ilya Kasnacheev < > > ilya.kasnach...@gmail.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > There was a ticket filed about the new feature, transactions in > > C++ > > > > > thin > > > > > > > client, making this feature unusable if there's more than one > > > > > connection > > > > > > > endpoint: > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14204 > > > > > > > > > > > > > > I don't think this is a genuine blocker for 2.10, since there is > > a > > > > > > > workaround (use just one endpoint), nevertheless it is a critical > > > > > crasher > > > > > > > bug, so I wonder if Igor could take a look at it promptly, > > include the > > > > > > fix > > > > > > > in 2.10. > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > чт, 18 февр. 2021 г. в 09:03, Zhenya Stanilovsky > > > > > > > > > > > > >: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I fill the ticket with drop problem, plz take a look [1] > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14205 > > > > > > > > > > > > > > > > >Ilya, > > > > > > > > > > > > > > > > > >Thanks! > > > > > > > > >I've added this step to the Release Process wiki page also > > [1]. > > > > > > > > > > > > > > > > > >[1] > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P1.2ImplementationandScopeFinalization > > > > > > > > > > > > > > > > > >On Wed, 17 Feb 2021 at 18:05, Ilya Kasnacheev < > > > > > > ilya.kasnach...@gmail.com > > > > > > > > > wrote: > > > > > > > > >> > > > > > > > > >> Hello! > > > > > > > > >> > > > > > > > > >> I have added ignite-2.10 to Nightly build triggering. I > > hope we > > > > > will > > > > > > > > have a > > > > > > > > >> 2.10 nightly tomorrow. Shame that I didn't do it earlier. > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > htt
[jira] [Created] (IGNITE-14231) IGNITE_ENABLE_FORCIBLE_NODE_KILL flag is not supported in inverse connection request scenario
Sergey Chugunov created IGNITE-14231: Summary: IGNITE_ENABLE_FORCIBLE_NODE_KILL flag is not supported in inverse connection request scenario Key: IGNITE-14231 URL: https://issues.apache.org/jira/browse/IGNITE-14231 Project: Ignite Issue Type: Bug Affects Versions: 2.9.1 Reporter: Sergey Chugunov Assignee: Sergey Chugunov Fix For: 2.11 IGNITE_ENABLE_FORCIBLE_NODE_KILL flag enables server nodes to forcibly kill clients visible via Discovery but unreachable by Communication protocol. This leads to infinite loops when server tries to establish communication connection to unreachable client fails and tries again effectively ignoring the flag. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14232) IgniteCliInterfaceTest and ProgressBarTest fails in some terminals
Kirill Gusakov created IGNITE-14232: --- Summary: IgniteCliInterfaceTest and ProgressBarTest fails in some terminals Key: IGNITE-14232 URL: https://issues.apache.org/jira/browse/IGNITE-14232 Project: Ignite Issue Type: Task Reporter: Kirill Gusakov Assignee: Kirill Gusakov In Cygwin/Git Bash terminals under the Windows all tests with ANSI symbols are failing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14233) Metrics framework
Vyacheslav Koptilin created IGNITE-14233: Summary: Metrics framework Key: IGNITE-14233 URL: https://issues.apache.org/jira/browse/IGNITE-14233 Project: Ignite Issue Type: New Feature Reporter: Vyacheslav Koptilin Need to adapt and port metrics framework from AI2.x to AI3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14234) Tracing framework
Vyacheslav Koptilin created IGNITE-14234: Summary: Tracing framework Key: IGNITE-14234 URL: https://issues.apache.org/jira/browse/IGNITE-14234 Project: Ignite Issue Type: New Feature Reporter: Vyacheslav Koptilin Need to port and adapt tracing framework from AI2.x to AI3.0. It would be nice to add a new integration with OpenTelemetry. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [MTCGA]: new failures in builds [5882649] needs to be handled
Igniters, Did not we agree on disabling MVCC suites? Why does TC bot still run them? 2021-02-20 8:16 GMT+03:00, Atri Sharma : > I ran the MVCC Test Suite 7 on branch with my changes a couple of > times with no failures. > > On Sat, Feb 20, 2021 at 8:37 AM wrote: >> >> Hi Igniters, >> >> I've detected some new issue on TeamCity to be handled. You are more than >> welcomed to help. >> >> If your changes can lead to this failure(s): We're grateful that you were >> a volunteer to make the contribution to this project, but things change >> and you may no longer be able to finalize your contribution. >> Could you respond to this email and indicate if you wish to continue and >> fix test failures or step down and some committer may revert you commit. >> >> *New Critical Failure in master-nightly MVCC Cache 7 >> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E >> Changes may lead to failure were done by >> - aleksey plekhanov >> https://ci.ignite.apache.org/viewModification.html?modId=917288 >> - atri sharma >> https://ci.ignite.apache.org/viewModification.html?modId=917319 >> - mikhail petrov >> https://ci.ignite.apache.org/viewModification.html?modId=917314 >> >> - 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 06:06:54 20-02-2021 > > -- > Regards, > > Atri > Apache Concerted > -- Best regards, Ivan Pavlukhin
[jira] [Created] (IGNITE-14235) Provide a minimal cache/table configuration
Vyacheslav Koptilin created IGNITE-14235: Summary: Provide a minimal cache/table configuration Key: IGNITE-14235 URL: https://issues.apache.org/jira/browse/IGNITE-14235 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin Need to provide a way to configure a cache/table in accordance with IEP-55 Unified Configuration [1] and IEP-54 Schema first approach. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-55+Unified+Configuration [2] https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
Apache Ignite 3 / RPM
Hi, Igniters. Sincerely asking you to help me with testing new RPM package for apache ignite 3.x [1] Currently what is needed to be tested — successful installation and binary run under most of RHEL based distributions: Red Hat, CentOS, Oracle Linux, Fedora, etc. Any other thoughts and suggestions are more than welcome too. RPM assembly code can be found here [2] Thanks in advance! [1] https://issues.apache.org/jira/secure/attachment/13021121/apache-ignite-3.0.0-1.noarch.rpm [2] https://github.com/apache/ignite-3/pull/29/files
[jira] [Created] (IGNITE-14236) Provide a new version of cache API
Vyacheslav Koptilin created IGNITE-14236:
Summary: Provide a new version of cache API
Key: IGNITE-14236
URL: https://issues.apache.org/jira/browse/IGNITE-14236
Project: Ignite
Issue Type: Sub-task
Reporter: Vyacheslav Koptilin
Need to provide a minimal cache API that includes at least the following
methods:
- reading a value for a given key
- writing a new value for a given key
- remove a value for a given key
- method that determines if the cache contains an entry for the specified key.
- a way to iterate all key/value pairs
- cache/table size (this method is questionable)
Additionally, it can be considered adding a way to execute the user's code for
the specified key - something like {{Cache#invoke()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14237) Affinity function
Vyacheslav Koptilin created IGNITE-14237: Summary: Affinity function Key: IGNITE-14237 URL: https://issues.apache.org/jira/browse/IGNITE-14237 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin It seems that we need to adopt a well-known rendezvous affinity function to AI-3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14238) Creating and destroying caches
Vyacheslav Koptilin created IGNITE-14238: Summary: Creating and destroying caches Key: IGNITE-14238 URL: https://issues.apache.org/jira/browse/IGNITE-14238 Project: Ignite Issue Type: Bug Reporter: Vyacheslav Koptilin Need to implement a new cluster-wide procedure that will be responsible for creating and destroying caches. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14239) Raft based implementation of atomic protocol
Vyacheslav Koptilin created IGNITE-14239: Summary: Raft based implementation of atomic protocol Key: IGNITE-14239 URL: https://issues.apache.org/jira/browse/IGNITE-14239 Project: Ignite Issue Type: Sub-task Reporter: Vyacheslav Koptilin Implement a new atomic protocol based on raft client api [1] [1] IGNITE-14149 -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: TeamCity agent aitc-lin07_04 fails to run Build
Looks like somebody fixed that. An hour ago Build succeeded at last [1]. It was the first successful job for a long time. Thanks! removed directory '/opt/buildagent/.m2/repository/org/apache/ignite' Process exited with code 0 [1] https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/5890154 On Wed, Feb 24, 2021 at 10:10 AM Max Timonin wrote: > Hi! > > My "Build" runs on TC fail with on 1 (Step: Cleanup local maven > repository (Command Line)) > > Error is related to AI 3.0.0: > > + rm -rfv /opt/buildagent/.m2/repository/org/apache/ignite > > rm: cannot remove > '/opt/buildagent/.m2/repository/org/apache/ignite/ignite-configuration/ > *3.0.0-SNAPSHOT*/_remote.repositories': *Permission denied* > > As I can see this error is only on aitc-lin07_04 agent. The first time it > appeared 16th of February [1] > > [1] > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/5876992 > > How can we fix this? >
Re: [DISCUSS] Missed (non-suited) tests
Hi, all! What do you think if we add the check in the TC [Build] job. Currently [Build] runs also check for licences, checkstyle [1]: mvn *install* -Pall-java,all-scala,scala,*licenses*,lgpl,examples, *checkstyle* -DskipTests -Dmaven.javadoc.skip=true %MAVEN_MODULES_STRING%. So let's add the check too to block other jobs. As if there missed tests then TC run may be invalid - missed tests may be broken and then the MTCGA visa too. To made this we should change command line parameters: 1. Add profile check-test-suites; 2. Remove -Dskiptests flag. -Pall-java,all-scala,scala,licenses,lgpl,examples,checkstyle, *check-test-suites *-DskipTests -Dmaven.javadoc.skip=true %MAVEN_MODULES_STRING% WDYT? [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite&tab=buildTypeSettings&branch_IgniteTests24Java8=%3Cdefault On Tue, Feb 9, 2021 at 4:48 PM Ilya Kasnacheev wrote: > Hello again! > > Of course it's 20 minutes, not 20 seconds. > > Regards, > -- > Ilya Kasnacheev > > > вт, 9 февр. 2021 г. в 16:45, Ilya Kasnacheev : > > > Hello! > > > > Java part kicks in if the target not found in pom.xml. Ideally we should > > skip this build if target check-test-suites is not in pom.xml > > > > I have changed its timeout to 20 second which should terminate its > > progression on older builds. Maybe that would be sufficient for now. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 9 февр. 2021 г. в 14:09, Petr Ivanov : > > > >> As much as I understood — we execute internal class as plugin, where all > >> the magic is done. > >> Seems pretty solid in Maven part. Java part, unfortunately, cannot > check. > >> > >> > >> > >> Regards, > >> *Petr Ivanov* > >> Head of IT > >> IT & Development Solutions | > >> *GRIDGAIN SYSTEMS*+7 (911) 945-00-59 > >> > >> On 9 Feb 2021, at 12:32, Ilya Kasnacheev > >> wrote: > >> > >> Hello Peter, > >> > >> Thanks for chiming in. The code is under > >> https://github.com/apache/ignite/pull/8367 > >> > >> Regards, > >> -- > >> Ilya Kasnacheev > >> > >> > >> вт, 9 февр. 2021 г. в 12:20, Petr Ivanov : > >> > >>> Hi, Ilya. > >>> > >>> > >>> I've added Inspections to Run All. > >>> Checkstyle is currently integrated to Build and can be deleted. > >>> > >>> > >>> Where can I find the code for check-test-suites profile? > >>> > >>> > >>> Regards, > >>> *Petr Ivanov* > >>> Head of IT > >>> IT & Development Solutions | > >>> *GRIDGAIN SYSTEMS*+7 (911) 945-00-59 > >>> > >>> On 9 Feb 2021, at 12:16, Ilya Kasnacheev > >>> wrote: > >>> > >>> Hello! > >>> > >>> I have found one issue where it would cause tests to be run if the > >>> change is not present in the target branch. > >>> > >>> This includes e.g. 2.10 nightlies. > >>> > >>> What can we do to avoid that? Is specifying -DskipTests sufficient? Any > >>> chance that it will break the missed tests check? > >>> > >>> Regards, > >>> -- > >>> Ilya Kasnacheev > >>> > >>> > >>> пн, 8 февр. 2021 г. в 14:13, Ilya Kasnacheev < > ilya.kasnach...@gmail.com > >>> >: > >>> > Hello! > > I have created a TC suite: > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MissingTests?mode=builds > > + Peter Ivanov > > Can you please check if everything is alright? > > BTW, it seems that Inspections [Core] is only in Run All Basic (but > not > in Run All), and Check Code Style is not triggered by either one. Is > it > correct? > > Regards, > -- > Ilya Kasnacheev > > > пн, 8 февр. 2021 г. в 10:22, Max Timonin : > > > Hi! > > > > Yes, now it's a part of the Travis check, and there is already a > first > > successful build [1]. But I think it's also required to run the check > > on TC > > too, along with jobs for checking licenses, code style, and core > > inspections. > > > > > > [1] https://travis-ci.com/github/apache/ignite/builds/216363067 > > > > On Fri, Feb 5, 2021 at 7:13 PM Ilya Kasnacheev < > > ilya.kasnach...@gmail.com> > > wrote: > > > > > Hello! > > > > > > I have merged it to master! > > > > > > I wonder what happens next. It will run as a part of travis check? > > Do we > > > also need to add it as a TC suite? > > > > > > Regards, > > > -- > > > Ilya Kasnacheev > > > > > > > > > ср, 3 февр. 2021 г. в 18:50, Ilya Kasnacheev < > > ilya.kasnach...@gmail.com>: > > > > > > > Hello! > > > > > > > > Code mostly looks good, I have added a minor request. I will > check > > how it > > > > works and then we may commit. > > > > > > > > + zaleslaw@gmail.com > > > > > > > > Can you please check whether the new ML suites make sense? > > > > math/distances/DistancesTestSuite.java > > > > naivebayes/NaiveBayesTestSuite.java > > > > > > > > Would we need to add them to some TC runs? > > > > > > > > Regards, > > > > -- >
[jira] [Created] (IGNITE-14240) Handle authentication error on python thin client properly
Ivan Daschinskiy created IGNITE-14240: - Summary: Handle authentication error on python thin client properly Key: IGNITE-14240 URL: https://issues.apache.org/jira/browse/IGNITE-14240 Project: Ignite Issue Type: Bug Components: python, thin client Reporter: Ivan Daschinskiy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14241) IgniteCacheAbstractQuerySelfTest#testClientQueryExecutedEventsIncludeSensitive broken
Nikolay Izhikov created IGNITE-14241:
Summary:
IgniteCacheAbstractQuerySelfTest#testClientQueryExecutedEventsIncludeSensitive
broken
Key: IGNITE-14241
URL: https://issues.apache.org/jira/browse/IGNITE-14241
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
After 2ed8e7c641f8b57986cd50dca55ff4e5026c9fc3
{{IgniteCacheAbstractQuerySelfTest#testClientQueryExecutedEventsIncludeSensitive}}
is broken.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: TeamCity agent aitc-lin07_04 fails to run Build
I'm sorry, I forgot to write on dev-list about this agent. Indeed the target files were removed manually. > On 24 Feb 2021, at 19:32, Max Timonin wrote: > > Looks like somebody fixed that. An hour ago Build succeeded at last [1]. It > was the first successful job for a long time. Thanks! > > removed directory '/opt/buildagent/.m2/repository/org/apache/ignite' > Process exited with code 0 > > [1] > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/5890154 > > On Wed, Feb 24, 2021 at 10:10 AM Max Timonin > wrote: > >> Hi! >> >> My "Build" runs on TC fail with on 1 (Step: Cleanup local maven >> repository (Command Line)) >> >> Error is related to AI 3.0.0: >> >> + rm -rfv /opt/buildagent/.m2/repository/org/apache/ignite >> >> rm: cannot remove >> '/opt/buildagent/.m2/repository/org/apache/ignite/ignite-configuration/ >> *3.0.0-SNAPSHOT*/_remote.repositories': *Permission denied* >> >> As I can see this error is only on aitc-lin07_04 agent. The first time it >> appeared 16th of February [1] >> >> [1] >> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/5876992 >> >> How can we fix this? >>
Re: [DISCUSS] Missed (non-suited) tests
Hi, Petr! Profile "check-test-suites" handles all tests in another way, it just verifies that all tests are suited. No tests run then. As I understand the [BUILD] job goal is preparing a .zip archive to distribute it for other jobs. I think it is a valid place to put sanity checks. If a check fails then no archive is prepared. WDYT? Also I see that there is a flag -Dmaven.javadoc.skip=true. I'd propose to change it to the profile "skip-docs", that was introduced in ticket [1] IGNITE-13623. As the setting "maven.javadoc.skip" does not affect scaladocs. [1] https://issues.apache.org/jira/browse/IGNITE-13623 On Thu, Feb 25, 2021 at 7:34 AM Petr Ivanov wrote: > Won't the absence of -DskipTests flag trigger ALL the tests for all > modules? > This flag was added intentionally. > > Instead, I'd put Non-Suited tests into some kind of sanity check, group > all sanity checks in single Run All, and make tests depend on it's > successful pass. > > > Regards, > *Petr Ivanov* > Head of IT > IT & Development Solutions | > *GRIDGAIN SYSTEMS*+7 (911) 945-00-59 > > On 24 Feb 2021, at 19:58, Max Timonin wrote: > > Hi, all! > > What do you think if we add the check in the TC [Build] job. Currently > [Build] runs also check for licences, checkstyle [1]: > > mvn *install* -Pall-java,all-scala,scala,*licenses*,lgpl,examples, > *checkstyle* -DskipTests -Dmaven.javadoc.skip=true %MAVEN_MODULES_STRING%. > > So let's add the check too to block other jobs. As if there missed tests > then TC run may be invalid - missed tests may be broken and then the MTCGA > visa too. To made this we should change command line parameters: > 1. Add profile check-test-suites; > 2. Remove -Dskiptests flag. > > -Pall-java,all-scala,scala,licenses,lgpl,examples,checkstyle, > *check-test-suites *-DskipTests -Dmaven.javadoc.skip=true > %MAVEN_MODULES_STRING% > > WDYT? > > [1] > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite&tab=buildTypeSettings&branch_IgniteTests24Java8=%3Cdefault > > On Tue, Feb 9, 2021 at 4:48 PM Ilya Kasnacheev > wrote: > >> Hello again! >> >> Of course it's 20 minutes, not 20 seconds. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> вт, 9 февр. 2021 г. в 16:45, Ilya Kasnacheev : >> >> > Hello! >> > >> > Java part kicks in if the target not found in pom.xml. Ideally we should >> > skip this build if target check-test-suites is not in pom.xml >> > >> > I have changed its timeout to 20 second which should terminate its >> > progression on older builds. Maybe that would be sufficient for now. >> > >> > Regards, >> > -- >> > Ilya Kasnacheev >> > >> > >> > вт, 9 февр. 2021 г. в 14:09, Petr Ivanov : >> > >> >> As much as I understood — we execute internal class as plugin, where >> all >> >> the magic is done. >> >> Seems pretty solid in Maven part. Java part, unfortunately, cannot >> check. >> >> >> >> >> >> >> >> Regards, >> >> *Petr Ivanov* >> >> Head of IT >> >> IT & Development Solutions | >> >> *GRIDGAIN SYSTEMS*+7 (911) 945-00-59 >> >> >> >> On 9 Feb 2021, at 12:32, Ilya Kasnacheev >> >> wrote: >> >> >> >> Hello Peter, >> >> >> >> Thanks for chiming in. The code is under >> >> https://github.com/apache/ignite/pull/8367 >> >> >> >> Regards, >> >> -- >> >> Ilya Kasnacheev >> >> >> >> >> >> вт, 9 февр. 2021 г. в 12:20, Petr Ivanov : >> >> >> >>> Hi, Ilya. >> >>> >> >>> >> >>> I've added Inspections to Run All. >> >>> Checkstyle is currently integrated to Build and can be deleted. >> >>> >> >>> >> >>> Where can I find the code for check-test-suites profile? >> >>> >> >>> >> >>> Regards, >> >>> *Petr Ivanov* >> >>> Head of IT >> >>> IT & Development Solutions | >> >>> *GRIDGAIN SYSTEMS*+7 (911) 945-00-59 >> >>> >> >>> On 9 Feb 2021, at 12:16, Ilya Kasnacheev >> >>> wrote: >> >>> >> >>> Hello! >> >>> >> >>> I have found one issue where it would cause tests to be run if the >> >>> change is not present in the target branch. >> >>> >> >>> This includes e.g. 2.10 nightlies. >> >>> >> >>> What can we do to avoid that? Is specifying -DskipTests sufficient? >> Any >> >>> chance that it will break the missed tests check? >> >>> >> >>> Regards, >> >>> -- >> >>> Ilya Kasnacheev >> >>> >> >>> >> >>> пн, 8 февр. 2021 г. в 14:13, Ilya Kasnacheev < >> ilya.kasnach...@gmail.com >> >>> >: >> >>> >> Hello! >> >> I have created a TC suite: >> >> >> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MissingTests?mode=builds >> >> + Peter Ivanov >> >> Can you please check if everything is alright? >> >> BTW, it seems that Inspections [Core] is only in Run All Basic (but >> not >> in Run All), and Check Code Style is not triggered by either one. Is >> it >> correct? >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пн, 8 февр. 2021 г. в 10:22, Max Timonin : >> >> > Hi! >> > >> > Yes, now it's a part of the Travis check, and there is already a >> first >> > successful build [
