Re: Performance drop with New Monitoring.
Hello Nikolay, I will take a look shortly. вт, 2 июл. 2019 г. в 14:30, Nikolay Izhikov : > Guys. > > I've prepared PR to fix this issue. > Who want to review it? > > https://github.com/apache/ignite/pull/6656 > > В Пн, 01/07/2019 в 15:17 +0300, Nikolay Izhikov пишет: > > Hello, Igniter. > > > > I think we should fix the issue with slight changes in internal API (was > not released yet). > > > > Changes in API was independently proposed by me and Alexey Plekhanov [1]: > > > > 1. We should introduce `MetricGroup` - collection of metric of one > specific Ignite entity(io subsystem, data region, cache, etc.). > > > > 2. We can remove entire `MetricGroup` (on cache or cache group destroy) > with complexity of O(1). > > > > 3. We can remove metric from `MetricGroup` with complexity of O(1). > > > > [1] > https://issues.apache.org/jira/browse/IGNITE-11920?jql=labels%20%3D%20IEP-35%20ORDER%20BY%20status%20ASC > > > > В Пт, 28/06/2019 в 19:10 +0300, Nikolay Izhikov пишет: > > > Hello, Maksim. > > > > > > I will take a look shortly. > > > > > > В Пт, 28/06/2019 в 19:02 +0300, Maksim Stepachev пишет: > > > > Hello, Igniters. > > > > > > > > I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" > breaks cache stop performance. It affects next tests: > testParallelStartAndStop, testStartManyCaches > > > > > > > > The spent time was increased 6 times:( > > > > > > > > Look at: > https://ci.ignite.apache.org/project.html?tab=testDetails_IgniteTests24Java8=%3Cdefault%3E=IgniteTests24Java8=-145777872614811891=4 >
Re: Signing off Ignite for export beyond the U.S.
Hi Igniters, I've created a new page https://cwiki.apache.org/confluence/display/IGNITE/Crypto+Notice and added the last step for the release process - Update ECCN matrix. Sincerely, Dmitriy Pavlov ср, 26 июн. 2019 г. в 14:07, Dmitriy Pavlov : > Sure, up to you. > > I've committed the readme (it is mandated by the crypto process). > > Later I will copy all relevant crypto-notice related information to wiki > and update release process with extra double-checking step. > > ср, 26 июн. 2019 г. в 01:04, Denis Magda : > >> Dmitry, thanks. As for the ordering, the list is not fully ordered. Looks >> like the projects were added to the end. I would leave it as is for now. >> >> - >> Denis >> >> >> On Tue, Jun 25, 2019 at 5:42 PM Dmitriy Pavlov >> wrote: >> >> > Denis thank you, >> > >> > I see updates in the matrix so I've removed source XMLs from the local >> > ignite-11932 branch. >> > >> > In the matrix in the ASF site, other projects seem to be sorted >> > alphabetically. Maybe we should place Ignite near Incubator. >> > >> > I will commit & update the wiki, but for now, requests to >> > https://gitbox.apache.org are timed out from my laptop. I will retry >> in >> > 10 >> > hours. >> > >> > Sincerely >> > Dmitriy Pavlov >> > >> > >> > вт, 25 июн. 2019 г. в 23:58, Denis Magda : >> > >> > > In addition to that, how about adding an item for Ignite release >> policy >> > to >> > > validate that there are no cryptography related changes? >> > > http://www.apache.org/licenses/exports/ >> > > >> > > -- >> > > Denis Magda >> > > >> > > >> > > On Tue, Jun 25, 2019 at 1:54 PM Denis Magda >> wrote: >> > > >> > > > Dmitry, >> > > > >> > > > I've updated the ASF website by including Ignite to the exports >> matrix >> > > > [1]. Plus, notified the controlling U.S. entities on the matter. >> > > > >> > > > Could you please do one more favor and help to close these two items >> > > > (flying on a plane and a poor Internet connection makes it >> impossible >> > to >> > > > check them off on my end)? >> > > > >> > > >- Update README.txt in Ignite master with the content prepared >> > earlier >> > > >by you >> > > >- Copy content of this doc [2] to Ignite Wiki >> > > > >> > > > [1] http://www.apache.org/licenses/exports/ >> > > > [2] >> > > > >> > > >> > >> https://docs.google.com/spreadsheets/d/1s15HnsE40hHl0QN2aX0hJ3atw9_LO19_mzhgM96rcbo/edit?usp=sharing >> > > > >> > > > - >> > > > Denis >> > > > >> > > > >> > > > On Wed, Jun 19, 2019 at 2:47 PM Dmitriy Pavlov >> > > wrote: >> > > > >> > > >> Pavel replied to me in private: encryption is available since 2.4 >> for >> > > .Net >> > > >> thin client. >> > > >> >> > > >> I've also modified source XML >> > > >> >> > > >> >> > > >> > >> https://github.com/apache/ignite/pull/6616/files#diff-1995c8a78832996cb48db91f7550479cR8 >> > > >> >> > > >> >> > > >> чт, 20 июн. 2019 г. в 00:10, Denis Magda : >> > > >> >> > > >> > Pavel, >> > > >> > >> > > >> > I still have no info related to starting version of .NET >> encryption >> > > >> > > support. So I supposed it was 1.5. >> > > >> > >> > > >> > >> > > >> > Could you please help with this last open item? >> > > >> > >> > > >> > Dmitry, thanks for the final summary. I'll contact ASF folks >> trying >> > to >> > > >> find >> > > >> > the ASF website dev instructions. >> > > >> > >> > > >> > >> > > >> > -- >> > > >> > Denis Magda >> > > >> > >> > > >> > >> > > >> > On Wed, Jun 19, 2019 at 11:35 AM Dmitriy Pavlov < >> dpav...@apache.org >> > > >> > > >> > wrote: >> > > >> > >> > > >> > > Hi Denis, >> > > >> > > >> > > >> > > I still have no info related to starting version of .NET >> > encryption >> > > >> > > support. So I supposed it was 1.5. >> > > >> > > >> > > >> > > I've started both XSTLs and added an example of both XLTs >> output >> > to >> > > >> > google >> > > >> > > doc tabs. One transformer is for email template generation >> > (requires >> > > >> > > project name), another is for the site table. >> > > >> > > >> > > >> > > Only one TODO now left in the PR version of the update. All >> other >> > > >> stuff >> > > >> > is >> > > >> > > ready for publishing: >> > > >> > > >> > > >> > > >> > > >> > >> > > >> >> > > >> > >> https://github.com/apache/ignite/pull/6616/files#diff-1995c8a78832996cb48db91f7550479cR8 >> > > >> > > >> > > >> > > Sincerely, >> > > >> > > Dmitriy Pavlov >> > > >> > > >> > > >> > > P.S. I'm not sure that dev. the list will keep formatting, but >> > > anyway >> > > >> > here >> > > >> > > is transformer output example as text. >> > > >> > > >> > > >> > > Apache Ignite Project >> > > >> > > Product Name Versions ECCN >> > > >> > > Controlled Source >> > > >> > > Apache Ignite development 5D002 >> > > >> > > ASF, Oracle, The OpenSSL Project, Microsoft, .NET Foundation, >> > > JCraft, >> > > >> > Inc., >> > > >> > > The Eclipse Foundation >> > > >> > > 2.5.0 - latest 5D002 >> > > >> > > ASF, Oracle, The OpenSSL Project, Microsoft, .NET Foundation, >> > > JCraft, >> > > >> > Inc., >> > > >>
Re: SpiUriDeploy TC job fails on Java 9+
Hello! I have just tried, looks like it is buildable with Java 12 (provided that -Dmaven.javadoc.skip=true is specified) Regards, -- Ilya Kasnacheev пн, 1 июл. 2019 г. в 22:04, Павлухин Иван : > Hi, > > SpiUriDeploy fails on TC when it is run with any Java 9+ version [1]. > The reason is very simple, it contains one preliminary build step > which is forced to run with Java 8. But for Java 9+ builds we pass > module-related arguments and consequently it leads to Java 8 failure > (unknown argument). I tried to run that step on JDK used for all other > steps but faced a compilation error. It was on Java 9 and it said that > target version 11 was not supported. Due to some reason we configure > 11 in parent pom for > java-9+ profile. > > In my mind simple solution here is to set target version to 9. But > perhaps there is a clever way to use maximum version supported by a > used JDK. > > Do you have an ideas? > > [1] > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv > > -- > Best regards, > Ivan Pavlukhin >
[jira] [Created] (IGNITE-11957) IdleVerify command should print end time of execution.
Andrey Kalinin created IGNITE-11957: --- Summary: IdleVerify command should print end time of execution. Key: IGNITE-11957 URL: https://issues.apache.org/jira/browse/IGNITE-11957 Project: Ignite Issue Type: Improvement Reporter: Andrey Kalinin Assignee: Andrey Kalinin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11956) Cache topology changes during test run on stable topology
Ilya Kasnacheev created IGNITE-11956: Summary: Cache topology changes during test run on stable topology Key: IGNITE-11956 URL: https://issues.apache.org/jira/browse/IGNITE-11956 Project: Ignite Issue Type: Bug Reporter: Ilya Kasnacheev I am fixing a test GridCachePartitionedTxMultiNodeSelfTest which starts 4 nodes with cache defined in node configuration, and proceeds running queries. Query fail with exception: "Server topology is changed during query execution inside a transaction. It's recommended to rollback and retry transaction." The following log message is generated: [2019-06-04 19:47:02,410][INFO ][exchange-worker-#712%near.GridCachePartitionedTxMultiNodeSelfTest0%][time] Started exchange init [topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], crd=true, evt=DISCOVERY_CUSTOM_EVT, evtNode=374107c7-953a-42b2-8595-9bc0, customEvt=CacheAffinityChangeMessage [id=e1d41732b61-5761dee7-7e89-498e-94b2-334d4b743b3c, topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0], exchId=null, partsMsg=null, exchangeNeeded=true], allowMerge=false] Note that test is currently broken so you just need to fix that one issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11955) Fix control.sh issues related to IGNITE-11876 and IGNITE-11913
Denis Chudov created IGNITE-11955: - Summary: Fix control.sh issues related to IGNITE-11876 and IGNITE-11913 Key: IGNITE-11955 URL: https://issues.apache.org/jira/browse/IGNITE-11955 Project: Ignite Issue Type: Bug Reporter: Denis Chudov Assignee: Denis Chudov Umbrella ticket for control.sh issues related to IGNITE-11876 and IGNITE-11913 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Performance drop with New Monitoring.
Guys. I've prepared PR to fix this issue. Who want to review it? https://github.com/apache/ignite/pull/6656 В Пн, 01/07/2019 в 15:17 +0300, Nikolay Izhikov пишет: > Hello, Igniter. > > I think we should fix the issue with slight changes in internal API (was not > released yet). > > Changes in API was independently proposed by me and Alexey Plekhanov [1]: > > 1. We should introduce `MetricGroup` - collection of metric of one specific > Ignite entity(io subsystem, data region, cache, etc.). > > 2. We can remove entire `MetricGroup` (on cache or cache group destroy) with > complexity of O(1). > > 3. We can remove metric from `MetricGroup` with complexity of O(1). > > [1] > https://issues.apache.org/jira/browse/IGNITE-11920?jql=labels%20%3D%20IEP-35%20ORDER%20BY%20status%20ASC > > В Пт, 28/06/2019 в 19:10 +0300, Nikolay Izhikov пишет: > > Hello, Maksim. > > > > I will take a look shortly. > > > > В Пт, 28/06/2019 в 19:02 +0300, Maksim Stepachev пишет: > > > Hello, Igniters. > > > > > > I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" breaks > > > cache stop performance. It affects next tests: testParallelStartAndStop, > > > testStartManyCaches > > > > > > The spent time was increased 6 times:( > > > > > > Look at: > > > https://ci.ignite.apache.org/project.html?tab=testDetails_IgniteTests24Java8=%3Cdefault%3E=IgniteTests24Java8=-145777872614811891=4 signature.asc Description: This is a digitally signed message part
Re: Hello
Hi Vladimir, I've added this user to the Contributors role, now you can assign an issue to yourself. Sincerely, Dmitriy Pavlov вт, 2 июл. 2019 г. в 13:22, Vladimir Malinovskiy : > Hi! > I want to start working on IGNITE-11954 > Please and me to the contributor list > My jira username is vmalinovskiy > > On Tue, May 21, 2019 at 9:32 PM Denis Magda wrote: > > > > Hello Vladimir and welcome aboard! > > > > Please get to know the process and share your JIRA id once you're ready > to > > take on a task: > > https://ignite.apache.org/community/contribute.html#contribute > > > > - > > Denis > > > > > > On Tue, May 21, 2019 at 8:46 AM Vladimir Malinovskiy < > > vmalinovs...@gridgain.com> wrote: > > > > > Hello! > > > My name is Vladimir Malinovskiy. > > > Please register me as Ignite developer. > > > > > > -- > > > Vladimir Malinovskiy > > > Software Engineer, Moscow > > > +7-753-767-36-24 > > > https://www.gridgain.com > > > Powered by Apache® Ignite™ > > > > > > > -- > Vladimir Malinovskiy > Software Engineer, Moscow > +7-753-767-36-24 > https://www.gridgain.com > Powered by Apache® Ignite™ >
Re: Hello
Hi! I want to start working on IGNITE-11954 Please and me to the contributor list My jira username is vmalinovskiy On Tue, May 21, 2019 at 9:32 PM Denis Magda wrote: > > Hello Vladimir and welcome aboard! > > Please get to know the process and share your JIRA id once you're ready to > take on a task: > https://ignite.apache.org/community/contribute.html#contribute > > - > Denis > > > On Tue, May 21, 2019 at 8:46 AM Vladimir Malinovskiy < > vmalinovs...@gridgain.com> wrote: > > > Hello! > > My name is Vladimir Malinovskiy. > > Please register me as Ignite developer. > > > > -- > > Vladimir Malinovskiy > > Software Engineer, Moscow > > +7-753-767-36-24 > > https://www.gridgain.com > > Powered by Apache® Ignite™ > > -- Vladimir Malinovskiy Software Engineer, Moscow +7-753-767-36-24 https://www.gridgain.com Powered by Apache® Ignite™
[jira] [Created] (IGNITE-11954) control.sh should log actions performed
Vladimir Malinovskiy created IGNITE-11954: - Summary: control.sh should log actions performed Key: IGNITE-11954 URL: https://issues.apache.org/jira/browse/IGNITE-11954 Project: Ignite Issue Type: Bug Reporter: Vladimir Malinovskiy control.sh must log all actions performed to work/log/control-utility.log The fields logged should be as follows: * date and time of action start and finish * version of utility * command name and arguments * user issued command * session id * log level * action error code and/or status message All the same fields but for log level and and session should be also logged to console. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11953) BTree corruption caused by byte array values
Dmitriy Govorukhin created IGNITE-11953:
---
Summary: BTree corruption caused by byte array values
Key: IGNITE-11953
URL: https://issues.apache.org/jira/browse/IGNITE-11953
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Govorukhin
In some cases for caches with cache group, we can get BTree corruption
exception.
{code}
09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected. Will
be handled accordingly to configured handler [hnd=CustomFailureHandler
[ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR,
err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing a
transaction has produced runtime exception]]class
org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
Committing a transaction has produced runtime exception
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
Caused by: class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427,
val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770,
cacheId=-420893003]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1811)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1620)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1603)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:2131)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:442)
at
Re: Ignite Modularization
Denis, > I think this should be optional. Do you think we need to do it in the first > instance In my opinion we should at least have a solid understanding of the subject. I think it worth having a separate discussion regarding Java 9 modules. Today java modular subsystem seems to be not widely adopted yet. And many Java library developers are satisfied delivering their jars to be used as automatic modules. I think that today Java 8 is the most widely used version. But the situation can change soon and we should keep our eyes peeled. вт, 2 июл. 2019 г. в 00:39, Denis Magda : > > Hi Ivan, > > Thanks for looking into this. > > 1. I did not get from IEP whether Thin Clients have a separate > > repository and a release lifecycle or not. > > > Sorry for the confusion. Yes, such clients have to be in separate repos and > might have their own lifecycles. Updated the wiki. > > > > 2. Are we going to exclude tests for unsupported modules from Ignite > > TeamCity? > > > Yes, that's my thinking, an unsupported integration won't be part of Ignite > modular ecosystem and won't be tested by the community. Any objections? > > > > 3. Will we adress implementing Java 9+ modules during that process? > > > I think this should be optional. Do you think we need to do it in the > first instance? > > - > Denis > > > On Sun, Jun 30, 2019 at 10:45 PM Павлухин Иван wrote: > > > Hi Denis, > > > > I fully support the idea. Could you please clarify on following points: > > 1. I did not get from IEP whether Thin Clients have a separate > > repository and a release lifecycle or not. > > 2. Are we going to exclude tests for unsupported modules from Ignite > > TeamCity? > > 3. Will we adress implementing Java 9+ modules during that process? > > > > чт, 27 июн. 2019 г. в 18:11, Denis Magda : > > > > > > Ignite developers and users, > > > > > > I'd like us to consider Ignite modularization as part of Ignite 3.0 > > > timeframe. Presently, Ignite codebase mixes both core capabilities with > > 3rd > > > party integrations. It leads to the following: > > > > > >- Cumbersome and continuously growing codebase with many 3rd-party > > >dependencies. > > >- Some of the integrations are questionable and should no longer be > > >supported by the community at all. > > >- Integrations evolution is bound to Ignite release cycles even though > > >no changes are needed in the core. > > >- Ignite community has to support everything (test, release, fix, > > >continue development) which requires to have particular integration > > experts > > >on a permanent basis - doesn't work. > > > > > > Here is an IEP: > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization > > > > > > Please review it, share feedback. Pay attention to the list of > > integrations > > > that should no longer be supported by the community. > > > > > > > > > - > > > Denis > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > -- Best regards, Ivan Pavlukhin
[jira] [Created] (IGNITE-11952) Bug fixes and improvements in console utilities & test fixes
Sergey Chugunov created IGNITE-11952: Summary: Bug fixes and improvements in console utilities & test fixes Key: IGNITE-11952 URL: https://issues.apache.org/jira/browse/IGNITE-11952 Project: Ignite Issue Type: Bug Reporter: Sergey Chugunov Assignee: Sergey Chugunov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [PROBLEM] Is TC down?
Sorry for that. Now everything works completely fine for me. Seems to be some surprise from my ISP. вт, 2 июл. 2019 г. в 09:18, Павлухин Иван : > > Igniters, > > Currently TC web UI is not loaded in my environment and reports > ERR_CONNECTION_TIMED_OUT. Is the problem on my side or is TC down? > > -- > Best regards, > Ivan Pavlukhin -- Best regards, Ivan Pavlukhin
[PROBLEM] Is TC down?
Igniters, Currently TC web UI is not loaded in my environment and reports ERR_CONNECTION_TIMED_OUT. Is the problem on my side or is TC down? -- Best regards, Ivan Pavlukhin
