Re: [DISCUSSION] Moving tracing feature to GA
Hello, Valentin. I’m -1 to make Tracing API GA > the API is stabilized, and there are no known performance issues associated > with it. For now, API works with strings only and this leads to huge performance degradation when tracing enabled. Our measurement shows about 50% drop. Moreover, as we discussed earlier, there is a plan to merge internals of tracing and performance profiling To make it, we should enhance Tracing API and learn it to work with primitives in some king of lazy manner. So, I think we can’t stabilise Tracing API, for now. You can find more details in meetup talk (in Russian) [1] [1] https://www.youtube.com/watch?v=68QoOBD574g > 13 февр. 2021 г., в 04:23, Valentin Kulichenko > написал(а): > > Igniters, > > As far as I know, the tracing feature [1] is still marked as experimental. > However, It seems that we've had it for a while, it's being used, the API > is stabilized, and there are no known performance issues associated with it. > > That said, should we remove the "experimental" mark and move the feature to > the GA status? Please share your thoughts. > > [1] https://ignite.apache.org/docs/latest/monitoring-metrics/tracing > > -Val
Re: Adding metrics of using WAL archive
Hello, Kirill. > It is not possible for us to estimate how much space a user will need in the > archive so as not to overflow it under its load It still not clear for me why do we need those metrics. Can you please, write down specific scenario - how user will use these metrics to estimate required WAL volume? > 12 февр. 2021 г., в 19:35, ткаленко кирилл написал(а): > > Hi, Nikolay! > > It is not possible for us to estimate how much space a user will need in the > archive so as not to overflow it under its load. And the proposed metrics > will allow you to make a rough estimate. > > > 12.02.2021, 17:23, "Nikolay Izhikov" : >> Hello, Kirill. >> >> Can you, please, clarify - What question about WAL user have in mind? >> And what answers he(or she) gets with these new metrics? >> >>> 12 февр. 2021 г., в 14:26, ткаленко кирилл >>> написал(а): >>> >>> Hi everyone! >>> At the moment, I have not found an opportunity to estimate how many WAL >>> segments fall into the archive, say per day. >>> So I created a ticket https://issues.apache.org/jira/browse/IGNITE-14170 >>> to add a couple of new metrics.
[jira] [Created] (IGNITE-14172) Cool drawing ideas with pencil sketching
Cool drawing idea created IGNITE-14172: -- Summary: Cool drawing ideas with pencil sketching Key: IGNITE-14172 URL: https://issues.apache.org/jira/browse/IGNITE-14172 Project: Ignite Issue Type: Bug Environment: Cool drawing idea is one of the best channels for amazing cool drawing ideas! This channel is created to provide you with the most stunning and **[cool drawing ideas|https://cooldrawingidea.com/cool-drawing-ideas-with-pencil-sketching/]. We make videos on pencil sketch drawing, drawing nature and landscape, drawing tutorials for beginners, 3d drawing, drawing animals, drawing flowers, drawing birds, Drawing for kids, and Cartoon drawings. Reporter: Cool drawing idea **[Cool drawing idea|http://https://cooldrawingidea.com/] is one of the best channels for amazing cool drawing ideas! This channel is created to provide you with the most stunning and cool drawing ideas. We make videos on pencil sketch drawing, drawing nature and landscape, drawing tutorials for beginners, 3d drawing, drawing animals, drawing flowers, drawing birds, Drawing for kids, and Cartoon drawings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSSION] Moving tracing feature to GA
Igniters, As far as I know, the tracing feature [1] is still marked as experimental. However, It seems that we've had it for a while, it's being used, the API is stabilized, and there are no known performance issues associated with it. That said, should we remove the "experimental" mark and move the feature to the GA status? Please share your thoughts. [1] https://ignite.apache.org/docs/latest/monitoring-metrics/tracing -Val
[MTCGA]: new failures in builds [5869887] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master-nightly MVCC Cache 7 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E 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 03:14:48 13-02-2021
[MTCGA]: new failures in builds [5862082] 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 ZookeeperDiscoveryConcurrentStartAndStartStopTest.testConcurrentStart https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1582237967438206122=%3Cdefault%3E=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 22:44:49 12-02-2021
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Folks, I'm going to cherry-pick these issues to the release branch, any objections? Checkpointer thread holds write lock too long https://issues.apache.org/jira/browse/IGNITE-14140 Incorrect initialize checkpoint-runner-cpu thread pool https://issues.apache.org/jira/browse/IGNITE-14139 On Wed, 10 Feb 2021 at 21:59, Maxim Muzafarov wrote: > > Folks, > > Do we need any other critical issues from the master branch that need > to be cherry-picked picked from the master branch? I've marked the > latest select issues with patching version 2.10. > > - benchmarks completed (I'll do another one prior to preparing rc) > - the release notes merged > - cherry-picked issue (IGNITE-14073 Fixed transactions failover) > - most of the documentation pages also merged > > Hopefully, by Friday the 12th everything will be ready for the > preparation of a release candidate. > > On Tue, 9 Feb 2021 at 05:09, Никита Сафонов wrote: > > > > Hi everyone, > > > > Below are two lists of items representing all the remaining (and completed) > > documentation tasks for the Ignite 2.10 release. > > > > The "*Improvements*" part includes PRs on reworked documentation. > > The "*Finished*" part includes PRs on newly added documentation. > > > > *Improvements:* > > > > Documentation for .NET thin client service invocation > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > [2] https://github.com/apache/ignite/pull/8756 > > > > Documentation for cache warm-up strategy > > [1] https://issues.apache.org/jira/browse/IGNITE-13385 > > [2] https://github.com/apache/ignite/pull/8703 > > > > *Finished:* > > > > Document control.(sh|bin) command to get an arbitrary SystemView > > [1] https://issues.apache.org/jira/browse/IGNITE-14142 > > [2] https://github.com/apache/ignite/pull/8775 > > > > Document metric for processed keys when rebuilding indexes > > [1] https://issues.apache.org/jira/browse/IGNITE-14143 > > [2] https://github.com/apache/ignite/pull/8776 > > > > Document C++ thin client transactions > > [1] https://issues.apache.org/jira/browse/IGNITE-14144 > > [2] https://github.com/apache/ignite/pull/8777 > > > > Please don't hesitate to ask me if you have any questions or concerns. > > > > With best regards, > > Nikita > > > > сб, 6 февр. 2021 г. в 02:14, Никита Сафонов : > > > > > Maxim, > > > > > > Thank you for being ready to help! > > > > > > As I mentioned before, I'm sharing the completed doc items today. > > > Below is the list of tickets with the prepared PR's: > > > > > > *- Documentation: SQL tracing.* > > > [1] https://issues.apache.org/jira/browse/IGNITE-13981 > > > [2] https://github.com/apache/ignite/pull/8762 > > > > > > *- Documentation for async API (Thin client Java API)* > > > [1] https://issues.apache.org/jira/browse/IGNITE-14128 > > > [2] https://github.com/apache/ignite/pull/8753 > > > > > > *- Documentation for .NET: Thin Client: Service invocation* > > > [1] https://issues.apache.org/jira/browse/IGNITE-14129 > > > [2] https://github.com/apache/ignite/pull/8756 > > > > > > *- Document cluster API implementation for CPP* > > > [1] https://issues.apache.org/jira/browse/IGNITE-14133 > > > [2] https://github.com/apache/ignite/pull/8761 > > > > > > > > > I still have some docs to finish/improve. > > > I do believe that I'll provide the rest of the remaining documentation by > > > the end of Monday. > > > > > > Regards, > > > Nikita > > > > > > чт, 4 февр. 2021 г. в 21:45, Maxim Muzafarov : > > > > > >> Nikita, > > >> > > >> Thank you, I will be waiting for the review. > > >> > > >> > I'll give the precise estimate tomorrow as I'm still waiting for some > > >> info > > >> from the dev side. > > >> Let me know if you need any kind of help. > > >> > > >> On Thu, 4 Feb 2021 at 20:07, Никита Сафонов > > >> wrote: > > >> > > > >> > Hi Maxim, > > >> > > > >> > I can take a look! > > >> > > > >> > Moreover, I'm finishing the work on the remaining documentation > > >> > tickets. > > >> > I do believe that I'll be able to provide several PR's tomorrow and > > >> > complete the rest in a couple of days. > > >> > I'll give the precise estimate tomorrow as I'm still waiting for some > > >> info > > >> > from the dev side. > > >> > > > >> > Regards, > > >> > Nikita > > >> > > > >> > ср, 3 февр. 2021 г. в 22:40, Maxim Muzafarov : > > >> > > > >> > > Folks, > > >> > > > > >> > > > > >> > > I've prepared the RELEASE_NOTES. > > >> > > Would anyone take a look at the PR [2] [1]? > > >> > > > > >> > > > > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-14069 > > >> > > [2] https://github.com/apache/ignite/pull/8748/files > > >> > > > > >> > > On Tue, 2 Feb 2021 at 22:13, Maxim Muzafarov > > >> wrote: > > >> > > > > > >> > > > Folks, > > >> > > > > > >> > > > I've prepared first benchmarks comparing 2.9.1 vs 2.10 [1]. > > >> > > > Everything looks good at the first glance. > > >> > > > > > >> > > > > > >> > > > > >>
Re: Adding metrics of using WAL archive
Hi, Nikolay! It is not possible for us to estimate how much space a user will need in the archive so as not to overflow it under its load. And the proposed metrics will allow you to make a rough estimate. 12.02.2021, 17:23, "Nikolay Izhikov" : > Hello, Kirill. > > Can you, please, clarify - What question about WAL user have in mind? > And what answers he(or she) gets with these new metrics? > >> 12 февр. 2021 г., в 14:26, ткаленко кирилл >> написал(а): >> >> Hi everyone! >> At the moment, I have not found an opportunity to estimate how many WAL >> segments fall into the archive, say per day. >> So I created a ticket https://issues.apache.org/jira/browse/IGNITE-14170 to >> add a couple of new metrics.
.NET naming convention + RegisterSameJavaType mode
Hello, Igniters. Currently, BasicBinaryNameMapper[isSimpleName=false] assumes that type names equals both in Java and .Net. • Java type - ru.company.Model • .Net type - ‘ru.company.Model` However, .net naming conventions [1] differs from java [2] So, if a user follows both conventions then names will be • Java type - ru.company.Model • .Net type - 'Ru.Company.Model` User can implement this behaviour in custom name mapper, but custom name mapper will disable RegisterSameJavaType mode. To solve this issue I prepared a PR[3] and ticked [4]. PR introduces new BasicBinaryNameMapper#ForceJavaNamingConventions flag that enables mapping from .Net style to the java naming style. WDYT? [1] https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces [2] https://www.oracle.com/java/technologies/javase/codeconventions-namingconventions.html [3] https://github.com/apache/ignite/pull/8795 [4] https://issues.apache.org/jira/browse/IGNITE-14169
[jira] [Created] (IGNITE-14171) Flaky IgniteSpringBeanSpringResourceInjectionTest.testSpringResourceInjectedInService
Aleksey Plekhanov created IGNITE-14171:
--
Summary: Flaky
IgniteSpringBeanSpringResourceInjectionTest.testSpringResourceInjectedInService
Key: IGNITE-14171
URL: https://issues.apache.org/jira/browse/IGNITE-14171
Project: Ignite
Issue Type: Bug
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov
Test failing with exception:
{noformat}
Caused by: java.lang.NullPointerException
at
org.apache.ignite.spring.injection.IgniteSpringBeanSpringResourceInjectionTest$2.getInjectedBean(IgniteSpringBeanSpringResourceInjectionTest.java:216)
at
org.apache.ignite.spring.injection.IgniteSpringBeanSpringResourceInjectionTest$TestSpringResourceInjectedRunnable.run(IgniteSpringBeanSpringResourceInjectionTest.java:159){noformat}
Reason: after IGNITE-14112 Ignite node start faster and async service
initialization sometimes can't be finished before user code start to use Ignite.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Adding metrics of using WAL archive
Hello, Kirill. Can you, please, clarify - What question about WAL user have in mind? And what answers he(or she) gets with these new metrics? > 12 февр. 2021 г., в 14:26, ткаленко кирилл написал(а): > > Hi everyone! > At the moment, I have not found an opportunity to estimate how many WAL > segments fall into the archive, say per day. > So I created a ticket https://issues.apache.org/jira/browse/IGNITE-14170 to > add a couple of new metrics.
Adding metrics of using WAL archive
Hi everyone! At the moment, I have not found an opportunity to estimate how many WAL segments fall into the archive, say per day. So I created a ticket https://issues.apache.org/jira/browse/IGNITE-14170 to add a couple of new metrics.
[jira] [Created] (IGNITE-14170) Adding metrics of using WAL archive
Kirill Tkalenko created IGNITE-14170: Summary: Adding metrics of using WAL archive Key: IGNITE-14170 URL: https://issues.apache.org/jira/browse/IGNITE-14170 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.11 At the moment there is no way to estimate how many segments in the archive we may need, for example, per day. It is proposed to add the following metrics: * org.apache.ignite.mxbean.DataStorageMetricsMXBean#getLastArchivedSegmentIndex - Get the index of the last archived segment. * org.apache.ignite.mxbean.DataStorageMetricsMXBean#getMaxSizeComressedArchivedSegment - Getting the size of the maximum compressed segment in the archive. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14169) .NET support standart java, .net naming conventions
Nikolay Izhikov created IGNITE-14169:
Summary: .NET support standart java, .net naming conventions
Key: IGNITE-14169
URL: https://issues.apache.org/jira/browse/IGNITE-14169
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.9.1
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
Fix For: 2.11
Currently, {BasicBinaryNameMapper[isSimpleName=false]} assumes that type names
equals both in Java and .Net.
Java type - `ru.company.Model`
.Net type - 'ru.company.Model`
However, .net naming conventions [1] differs from java [2]
So, if a user follows both conventions then names will be
Java type - `ru.company.Model`
.Net type - 'Ru.Company.Model`
We should support standard naming conventions for both platforms in
{BasicBinaryNameMapper[isSimpleName=false]}.
[1]
https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces
[2]
https://www.oracle.com/java/technologies/javase/codeconventions-namingconventions.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
