[jira] [Created] (IGNITE-12164) Ignite Node stopped by ttl-cleanup-worker
Shariar Imtiaz created IGNITE-12164: --- Summary: Ignite Node stopped by ttl-cleanup-worker Key: IGNITE-12164 URL: https://issues.apache.org/jira/browse/IGNITE-12164 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7 Reporter: Shariar Imtiaz Fix For: None Attachments: Ignite Error.txt I have Ignite 2.7 and 5 node cluster. Over 40Mil data is generating and stored in ignite cache. I have set 3 days expiry for a paticular cache. It stopped by ttl-cleanup-worker. -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: Nabble message wrapping
Thanks for sharing details. 2. Change the ezmlm configuration to match the one of the users list. We > need to find a person who has access to the Apache infra in order to do this We can open a ticket for ASF INFRA. Could you please do that and see what they say? - Denis On Wed, Sep 11, 2019 at 1:36 AM Denis Mekhanikov wrote: > Denis, > > I did some investigation on this and started a Nabble support thread: > http://support.nabble.com/Line-wrapping-in-quotes-td7604136.html > It turned out, that Nabble has a little to do with it. It’s the mail list > itself. > > When you send a plain text message to the dev list either from Nabble or > in any other way, it’s getting wrapped to be 80 characters wide. > HTML messages don’t have this issue. Nabble uses plain text by default. > User list doesn’t wrap quotes though, even if you use plain text format. > You can see that my reply in the following thread is wrapped, but not the > quote: > http://apache-ignite-users.70518.x6.nabble.com/Ignition-Start-Timeout-if-connection-is-unsuccessful-td29289.html > > I see two possibilities of solving this issue: > > 1. Make Nabble always send messages in HTML format somehow. The issue will > still occur for other mail clients though. > 2. Change the ezmlm configuration to match the one of the users list. We > need to find a person who has access to the Apache infra in order to do > this. > > > Denis > On 11 Sep 2019, 00:53 +0300, Denis Magda , wrote: > > Denis, could you set up the dev list the way needed? > > > > - > > Denis > > > > > > On Thu, Aug 29, 2019 at 1:18 PM Denis Magda wrote: > > > > > Denis, > > > > > > I granted your account the admin access. Please do all the required > > > changes and let me know once done. > > > > > > - > > > Denis > > > > > > > > > On Thu, Aug 29, 2019 at 2:00 AM Denis Mekhanikov < > dmekhani...@gmail.com> > > > wrote: > > > > > > > Guys, > > > > > > > > Any update? Who has a Nabble admin account for the developers list? > > > > > > > > Denis > > > > On 27 Aug 2019, 14:55 +0300, Dmitriy Pavlov , > wrote: > > > > > Hi Denis, > > > > > > > > > > AFAIK, nabble forums are service, which resides outside of ASF > infra. > > > > They > > > > > have their separate support/feedback form. > > > > > > > > > > Maybe some PMC members could have some credentials for this > service. If > > > > so, > > > > > please share login info in SVN/private/credentials. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > >
Re: Start contributing Ignite
Lev, Let me loop in @Igor Sapego who is our main maintainer of the ODBC driver. Igor would you mind stepping in? https://issues.apache.org/jira/browse/IGNITE-12032 - Denis On Wed, Sep 11, 2019 at 2:59 AM Lev Agafonov wrote: > Hello, > Denis, thank you for support, happy to became part of your community! > > I don't have any Ignite experience, but I have bigdata-related experience: > working on several projects with Hadoop, Spark, Kafka, etc. I'm excited > with Ignite project, and hope I will use it in future projects, that is why > i decided to contribute it)) > > I started to work on IGNITE-12032. I investigated it and wrote a comment > with investigation results. I'd like to continue working on it, could you > please assign it on me (or may be it's OK to assign it to me by myself)? > > > Best Regards, > > Lev Agafonov > > > From: Denis Magda > Sent: Wednesday, September 11, 2019 1:21 AM > To: dev > Subject: Re: Start contributing Ignite > > Hello Lev! > > Welcome, it's nice to see you as part of the community. I've just added you > to the contributors'rs list in JIRA. Please go ahead and select a task > you'd like to work on. > > Btw, do you already have any Ignite-related experience? > > > - > Denis > > > On Mon, Sep 9, 2019 at 6:36 AM Lev Agafonov > wrote: > > > Hello, team! > > My name is Lev, I'm Java developer from Russia, Nizhny Novgorod. > > I'd be kindly glad to join your community and start contributing Ignite. > > Could you please grant to my Jira account 'levagafonov' contributor > > permissions? > > > > > > Best Regards, > > > > Lev Agafonov > > >
Re: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Ivan, thank you! Will update release notes and start the build shortly. ср, 11 сент. 2019 г. в 20:41, Ivan Rakov : > Alexey, > > I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master > and 2.7.6. > > Best Regards, > Ivan Rakov > > On 11.09.2019 18:13, Alexey Goncharuk wrote: > > Good, > > > > Please let me know when this is done, I will re-upload the release > > artifacts. > > > > ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin : > > > >> Alexey, > >> > >> The changes already have been tested, so no TC problems expected. > >> If this is true, then we need just a few hours to merge them. > >> > >> From: Alexey Goncharuk > >> Sent: Wednesday, September 11, 2019 6:03 PM > >> To: dev > >> Cc: Dmitriy Govorukhin; Anton Kalashnikov > >> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release > manager) > >> > >> Alexandr, > >> > >> I almost sent the vote email :) When do you expect the fix to be in > master > >> and 2.7.6? > >> > >> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin : > >> > >>> Folks, > >>> > >>> A critical bug was detected in .NET [1]. > >>> > >>> I understand that it’s a little bit late, but I propose to include this > >>> issue into the release scope. > >>> > >>> PR is ready, currently waiting for a TC visa. > >>> > >>> Thoughts? > >>> > >>> [1] - https://issues.apache.org/jira/browse/IGNITE-12163 > >>> > >>> > >>> From: Alexey Goncharuk > >>> Sent: Monday, September 9, 2019 5:11 PM > >>> To: dev > >>> Cc: Dmitriy Govorukhin; Anton Kalashnikov > >>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release > >> manager) > >>> Igniters, > >>> > >>> I just pushed the last ticket to ignite-2.7.6 branch; looks like we are > >>> ready for the next iteration. > >>> > >>> Given that Dmitriy Pavlov will be unavailable till the end of this > week, > >> I > >>> will take over the release. TC re-run is started. > >>> > >>> чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < > >>> dmitriy.govoruk...@gmail.com>: > >>> > Hi Igniters, > > I finished work on https://issues.apache.org/jira/browse/IGNITE-12127 > , > >>> fix > already in master and ignite-2.7.6 > > On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi Alexey, > > > > I think that I will finish work on the fix tomorrow. Fix already > completed > > but I need to get VISA from TC bot. > > > > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < > > alexey.goncha...@gmail.com> wrote: > > > >> Folks, it looks like I was overly optimistic with the estimates for > >>> the > >> mentioned two tickets. > >> > >> Dmitriy, Anton, > >> Can you share your vision when the issues will be fixed? Perhaps, it > makes > >> sense to release 2.7.6 with the already fixed issues and schedule > >>> 2.7.7? > >> Neither of them is a regression, so it's ok to release 2.7.6 as it > >> is > now. > >> Thoughts? > >> > >> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < > alexey.goncha...@gmail.com > >>> : > >>> Yes, my bad, forgot to include the link. That's the one. > >>> > >>> пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov >>> : > Alexey, > > Does the issue [1] is related to this [2] discussion on the > user-list? > If yes, I think it is very important to include these fixes to > >>> 2.7.6. > [1] https://issues.apache.org/jira/browse/IGNITE-12127 > [2] > > >> > http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html > On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov > wrote: > > Alexey, > > > > Looks like important fixes, better to include them. > > > > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < > alexey.goncha...@gmail.com>: > >> Igniters, > >> > >> Given that the RC1 vote did not succeed and we are still > >>> waiting > >> for > a few > >> minor fixes, may I suggest including these two tickest to the > 2.7.6 > scope? > >> https://issues.apache.org/jira/browse/IGNITE-12127 > >> https://issues.apache.org/jira/browse/IGNITE-12128 > >> > >> The first one has been already reported on the dev-list [1], > >>> the > second one > >> may cause a state when an Ignite node cannot start on > >> existing > persisted > >> data. Looking at the tickets, the fixes should be reasonably > easy, > >> so > it > >> should not shift 2.7.6 release timeline much. > >> > >> Thoughts? > >> > >> ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < > nizhi...@apache.org > >>> : > >>> Separate repos for different Spark version is a good idea > >> for > me. > >>> Anyway, can you
Re: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Alexey, I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master and 2.7.6. Best Regards, Ivan Rakov On 11.09.2019 18:13, Alexey Goncharuk wrote: Good, Please let me know when this is done, I will re-upload the release artifacts. ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin : Alexey, The changes already have been tested, so no TC problems expected. If this is true, then we need just a few hours to merge them. From: Alexey Goncharuk Sent: Wednesday, September 11, 2019 6:03 PM To: dev Cc: Dmitriy Govorukhin; Anton Kalashnikov Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) Alexandr, I almost sent the vote email :) When do you expect the fix to be in master and 2.7.6? ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin : Folks, A critical bug was detected in .NET [1]. I understand that it’s a little bit late, but I propose to include this issue into the release scope. PR is ready, currently waiting for a TC visa. Thoughts? [1] - https://issues.apache.org/jira/browse/IGNITE-12163 From: Alexey Goncharuk Sent: Monday, September 9, 2019 5:11 PM To: dev Cc: Dmitriy Govorukhin; Anton Kalashnikov Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) Igniters, I just pushed the last ticket to ignite-2.7.6 branch; looks like we are ready for the next iteration. Given that Dmitriy Pavlov will be unavailable till the end of this week, I will take over the release. TC re-run is started. чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: Hi Igniters, I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, fix already in master and ignite-2.7.6 On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: Hi Alexey, I think that I will finish work on the fix tomorrow. Fix already completed but I need to get VISA from TC bot. On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: Folks, it looks like I was overly optimistic with the estimates for the mentioned two tickets. Dmitriy, Anton, Can you share your vision when the issues will be fixed? Perhaps, it makes sense to release 2.7.6 with the already fixed issues and schedule 2.7.7? Neither of them is a regression, so it's ok to release 2.7.6 as it is now. Thoughts? сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < alexey.goncha...@gmail.com : Yes, my bad, forgot to include the link. That's the one. пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov : Alexey, Does the issue [1] is related to this [2] discussion on the user-list? If yes, I think it is very important to include these fixes to 2.7.6. [1] https://issues.apache.org/jira/browse/IGNITE-12127 [2] http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov wrote: Alexey, Looks like important fixes, better to include them. пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < alexey.goncha...@gmail.com>: Igniters, Given that the RC1 vote did not succeed and we are still waiting for a few minor fixes, may I suggest including these two tickest to the 2.7.6 scope? https://issues.apache.org/jira/browse/IGNITE-12127 https://issues.apache.org/jira/browse/IGNITE-12128 The first one has been already reported on the dev-list [1], the second one may cause a state when an Ignite node cannot start on existing persisted data. Looking at the tickets, the fixes should be reasonably easy, so it should not shift 2.7.6 release timeline much. Thoughts? ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < nizhi...@apache.org : Separate repos for different Spark version is a good idea for me. Anyway, can you help with Spark version migration, for now? В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет: Maybe the best solution today add for each new version of Spark the sub-module (Spark-2.3, Spark-2.4) or the separate repository with modules for each version or another way with separate repository and different branches like in https://github.com/datastax/spark-cassandra-connector 3 ways to support different versions with the different costs of support In the case of separate repository I could help, for example ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov < nizhi...@apache.org : Hello, Alexey. But the compatibility with Spark 2.3 will be broken, isn't it? Yes. Do you have any plans to support the different version of Spark without loosing your unique expertise in Spark-Ignite integration? What do you mean by "my unique expertise"? :) How do you see support of several Spark version? В Ср, 28/08/2019 в 14:29 +0300, Alexey Zinoviev пишет: Dear Nikolay Izhikov Are you going to update the Ignite-Spark integration for Spark 2.4. But the compatibility with Spark 2.3 will be broken, isn't it? Do you have any plans to support the different
Re: help on IGNITE-11894
Thanks, Nikolay. Some questions I have - 1. Looking at the Ignite core module I see following classes that are jdbc stores CacheJdbcBlobStore and CacheJdbcPojoStore. Are these the only ones or am I missing more? 2. I see the fetchSize is part of JdbcDialect. Which implementation of the JdbcDilect is used to access CacheStores? 3. Are there any examples of UT or docs which shows how the cachestores are being used so it helps me understand the full end to end workings on the CacheStores. Thanks, Amit On Mon, Sep 9, 2019 at 2:50 PM Nikolay Izhikov wrote: > Hell, Amit. > > You can write you question here, on the dev-list or in the ticket. > I think, Ignite community will help you with this and ongoing contribution. > > Welcome! > > В Пн, 09/09/2019 в 11:14 -0700, Amit Chavan пишет: > > Hello, > > > > I need some help on the ticket > > https://issues.apache.org/jira/browse/IGNITE-11894 since this is my time > > working on ignite code base. I am not able to move the ticket in progress > > and would like to chat with a developer on what is expected for the > ticket. > > Is there a slack channel or message client the team uses to communicate? > > > > Thanks, > > Amit >
Re: [IEP-35] Monitoring & Profiling. Phase 2
Hello, Andrey. Thanks, for joining the review. Basic interface for objects list is `MonitoringList`. It provides the following features: * name. * description. * row class. * size. * iterator for the list content. * attribute walker (described below). `MonitoringRow` is a marker interface for classes that can be used as a monitoring list content. Internally, there is only one implementation of `MonitoringList`, for now, `MonitoringListAdapter`. It adapts the content of some `ConcurrentMap` which uses widely in Ignite internals. I think, will be another implementation in the follow-up PRs. Public API changes: * New registry created `ReadOnlyMonitoringListRegistry` It provides access: * To all lists that exist in the Ignite. * Ability to subscribe to the list creation/removal events. * `MetricExporterSpi` changes: * `setMonitoringListRegistry` method added * `setMonitoringListExportFilter` method added. `MonitoringRowAttributeWalker` is a helper class for exporter implementations. Usually, exporter SPI iterates on `MonitoringRow` attributes. `SqlViewExporterSpi`, `JmxMetricExporterSpi` can be taken as an example. It can be implemented with Java reflection API, but I use more quick approach. `MonitoringRowAttributeWalker` can visit each attribute of the MonitoringRow implementation. It's also, preserves, the order provided by the MonitoringRow implementation author. It provides 2 main methods: * `visitAll(AttributeVisitor visitor);` - visits each attribute of the some monitoring row class. Provides index, name and class of attribute to the consumer. * `visitAll(R row, AttributeWithValueVisitor visitor)` - visits each attribute of some monitoring row instance. Provides index, name, class, value of attribute to the consumer. В Ср, 11/09/2019 в 16:30 +0300, Andrey Gura пишет: > Nikolai, > > I'm trying to review this PR but it is too large. > > Could you please describe problem and design of implemented solution? > Also javadocs for base interfaces aren't clear, too brief and doesn't > give any imagine about whole picture. > > At present it is very hard to understand the purposes of new > interfaces and walker generator, and design itself. > > On Fri, Sep 6, 2019 at 3:16 PM Nikolay Izhikov wrote: > > > > Hello, Igniters. > > > > IEP-35. Monitoring Phase2 is ready [1] > > Please, join to the review! > > > > I've implemented: > > > > * Monitoring list engine. > > * Following list implemented: > > * Cache list > > * Cache group list > > * Compute task list > > * Service list. > > > > Engine details: > > > > * `MonitoringList` added to store list data. > > * Base interface `MonitoringRow` for list data created. > > * Corresponding method added to `MetricExporterSpi` > > * `JmxMetricExporterSpi`, `SqlViewExporterSpi`, `LogExporterSpi` updated to > > support list export. > > * JMX, SQL and other column-oriented SPI uses > > `MonitoringRowAttributeWalker` to quickly traverse all list row attributes. > > * Implementation of `MonitoringRowAttributeWalkerfor specificMonitoringRow` > > can be generated with `MonitoringRowAttributeWalkerGenerator` > > > > I prepare follow-up PR [2], also. > > Following lists implemented: > > > > * SQL tables > > * SQL indexes > > * SQL schemas > > * SQL queries > > * Continuous queries > > * Text queries > > * Transactions > > * Cluster nodes > > * Client connections(JDBC, ODBC, Thin) > > > > [1] https://github.com/apache/ignite/pull/6845 > > [2] https://github.com/apache/ignite/pull/6790 > > > > > > > > пн, 10 июн. 2019 г. в 13:49, Nikolay Izhikov : > > > > > Hello, Igniters. > > > > > > Since Phase 1 will be merged in master soon I've created the ticket [1] > > > for Phase 2. > > > > > > Scope of Phase 2(copy-paste from the ticket) > > > > > > Ability to collect lists of some internal object Ignite manage. > > > Examples of such objects: > > > > > > * Caches > > > * Queries (including continuous queries) > > > * Services > > > * Compute tasks > > > * Distributed Data Structures > > > * etc... > > > > > > > > > 1. Fields for each list(that doesn't currently exists in Ignite) will be > > > discussed in separate tickets > > > 2. Metric Exporters (optionally) can support list export. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11905 > > > > > > > > > В Вт, 14/05/2019 в 16:42 +0300, Nikolay Izhikov пишет: > > > > Ticket for IEP.Phase1 created - > > > > > > https://issues.apache.org/jira/browse/IGNITE-11848 > > > > > > > > > > > > В Пн, 13/05/2019 в 18:06 +0300, Nikolay Izhikov пишет: > > > > > Hello, Igniters. > > > > > > > > > > We have discussed this IEP [1] with Alexey Goncharyuk, Anton > > > > > > Vinogradov, Andrey Gura, Alexey Scherbakov and Pavel Kovalenko. > > > > > > > > > > Issues to address: > > > > > > > > > > 1. Study experience of following libs, tools: > > > > > * OpenTracing > > > >
Re: Start contributing Ignite
Hello! You can assign it to yourself if nobody is actively working on it right now. Regards, -- Ilya Kasnacheev ср, 11 сент. 2019 г. в 12:59, Lev Agafonov : > Hello, > Denis, thank you for support, happy to became part of your community! > > I don't have any Ignite experience, but I have bigdata-related experience: > working on several projects with Hadoop, Spark, Kafka, etc. I'm excited > with Ignite project, and hope I will use it in future projects, that is why > i decided to contribute it)) > > I started to work on IGNITE-12032. I investigated it and wrote a comment > with investigation results. I'd like to continue working on it, could you > please assign it on me (or may be it's OK to assign it to me by myself)? > > > Best Regards, > > Lev Agafonov > > > From: Denis Magda > Sent: Wednesday, September 11, 2019 1:21 AM > To: dev > Subject: Re: Start contributing Ignite > > Hello Lev! > > Welcome, it's nice to see you as part of the community. I've just added you > to the contributors'rs list in JIRA. Please go ahead and select a task > you'd like to work on. > > Btw, do you already have any Ignite-related experience? > > > - > Denis > > > On Mon, Sep 9, 2019 at 6:36 AM Lev Agafonov > wrote: > > > Hello, team! > > My name is Lev, I'm Java developer from Russia, Nizhny Novgorod. > > I'd be kindly glad to join your community and start contributing Ignite. > > Could you please grant to my Jira account 'levagafonov' contributor > > permissions? > > > > > > Best Regards, > > > > Lev Agafonov > > >
Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Good, Please let me know when this is done, I will re-upload the release artifacts. ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin : > Alexey, > > The changes already have been tested, so no TC problems expected. > If this is true, then we need just a few hours to merge them. > > From: Alexey Goncharuk > Sent: Wednesday, September 11, 2019 6:03 PM > To: dev > Cc: Dmitriy Govorukhin; Anton Kalashnikov > Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) > > Alexandr, > > I almost sent the vote email :) When do you expect the fix to be in master > and 2.7.6? > > ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin : > > > Folks, > > > > A critical bug was detected in .NET [1]. > > > > I understand that it’s a little bit late, but I propose to include this > > issue into the release scope. > > > > PR is ready, currently waiting for a TC visa. > > > > Thoughts? > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-12163 > > > > > > From: Alexey Goncharuk > > Sent: Monday, September 9, 2019 5:11 PM > > To: dev > > Cc: Dmitriy Govorukhin; Anton Kalashnikov > > Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release > manager) > > > > Igniters, > > > > I just pushed the last ticket to ignite-2.7.6 branch; looks like we are > > ready for the next iteration. > > > > Given that Dmitriy Pavlov will be unavailable till the end of this week, > I > > will take over the release. TC re-run is started. > > > > чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < > > dmitriy.govoruk...@gmail.com>: > > > > > Hi Igniters, > > > > > > I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, > > fix > > > already in master and ignite-2.7.6 > > > > > > On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < > > > dmitriy.govoruk...@gmail.com> wrote: > > > > > > > Hi Alexey, > > > > > > > > I think that I will finish work on the fix tomorrow. Fix already > > > completed > > > > but I need to get VISA from TC bot. > > > > > > > > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < > > > > alexey.goncha...@gmail.com> wrote: > > > > > > > >> Folks, it looks like I was overly optimistic with the estimates for > > the > > > >> mentioned two tickets. > > > >> > > > >> Dmitriy, Anton, > > > >> Can you share your vision when the issues will be fixed? Perhaps, it > > > makes > > > >> sense to release 2.7.6 with the already fixed issues and schedule > > 2.7.7? > > > >> Neither of them is a regression, so it's ok to release 2.7.6 as it > is > > > now. > > > >> > > > >> Thoughts? > > > >> > > > >> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < > > > alexey.goncha...@gmail.com > > > >> >: > > > >> > > > >> > Yes, my bad, forgot to include the link. That's the one. > > > >> > > > > >> > пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov >: > > > >> > > > > >> >> Alexey, > > > >> >> > > > >> >> Does the issue [1] is related to this [2] discussion on the > > > user-list? > > > >> >> If yes, I think it is very important to include these fixes to > > 2.7.6. > > > >> >> > > > >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12127 > > > >> >> [2] > > > >> >> > > > >> > > > > > > http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html > > > >> >> > > > >> >> On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov > > > >> >> wrote: > > > >> >> > > > > >> >> > Alexey, > > > >> >> > > > > >> >> > Looks like important fixes, better to include them. > > > >> >> > > > > >> >> > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < > > > >> >> alexey.goncha...@gmail.com>: > > > >> >> > > > > >> >> > > Igniters, > > > >> >> > > > > > >> >> > > Given that the RC1 vote did not succeed and we are still > > waiting > > > >> for > > > >> >> a few > > > >> >> > > minor fixes, may I suggest including these two tickest to the > > > 2.7.6 > > > >> >> scope? > > > >> >> > > > > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12127 > > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12128 > > > >> >> > > > > > >> >> > > The first one has been already reported on the dev-list [1], > > the > > > >> >> second one > > > >> >> > > may cause a state when an Ignite node cannot start on > existing > > > >> >> persisted > > > >> >> > > data. Looking at the tickets, the fixes should be reasonably > > > easy, > > > >> so > > > >> >> it > > > >> >> > > should not shift 2.7.6 release timeline much. > > > >> >> > > > > > >> >> > > Thoughts? > > > >> >> > > > > > >> >> > > ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < > > > nizhi...@apache.org > > > >> >: > > > >> >> > > > > > >> >> > > > Separate repos for different Spark version is a good idea > for > > > me. > > > >> >> > > > Anyway, can you help with Spark version migration, for > now? > > > >> >> > > > > > > >> >> > > > В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет: > > > >> >> > > > > Maybe the best solution today add for each new version of > > > Spark > > > >> >> the > > > >> >> > > > > sub-module
RE: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Alexey, The changes already have been tested, so no TC problems expected. If this is true, then we need just a few hours to merge them. From: Alexey Goncharuk Sent: Wednesday, September 11, 2019 6:03 PM To: dev Cc: Dmitriy Govorukhin; Anton Kalashnikov Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) Alexandr, I almost sent the vote email :) When do you expect the fix to be in master and 2.7.6? ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin : > Folks, > > A critical bug was detected in .NET [1]. > > I understand that it’s a little bit late, but I propose to include this > issue into the release scope. > > PR is ready, currently waiting for a TC visa. > > Thoughts? > > [1] - https://issues.apache.org/jira/browse/IGNITE-12163 > > > From: Alexey Goncharuk > Sent: Monday, September 9, 2019 5:11 PM > To: dev > Cc: Dmitriy Govorukhin; Anton Kalashnikov > Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) > > Igniters, > > I just pushed the last ticket to ignite-2.7.6 branch; looks like we are > ready for the next iteration. > > Given that Dmitriy Pavlov will be unavailable till the end of this week, I > will take over the release. TC re-run is started. > > чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com>: > > > Hi Igniters, > > > > I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, > fix > > already in master and ignite-2.7.6 > > > > On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < > > dmitriy.govoruk...@gmail.com> wrote: > > > > > Hi Alexey, > > > > > > I think that I will finish work on the fix tomorrow. Fix already > > completed > > > but I need to get VISA from TC bot. > > > > > > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < > > > alexey.goncha...@gmail.com> wrote: > > > > > >> Folks, it looks like I was overly optimistic with the estimates for > the > > >> mentioned two tickets. > > >> > > >> Dmitriy, Anton, > > >> Can you share your vision when the issues will be fixed? Perhaps, it > > makes > > >> sense to release 2.7.6 with the already fixed issues and schedule > 2.7.7? > > >> Neither of them is a regression, so it's ok to release 2.7.6 as it is > > now. > > >> > > >> Thoughts? > > >> > > >> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < > > alexey.goncha...@gmail.com > > >> >: > > >> > > >> > Yes, my bad, forgot to include the link. That's the one. > > >> > > > >> > пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov : > > >> > > > >> >> Alexey, > > >> >> > > >> >> Does the issue [1] is related to this [2] discussion on the > > user-list? > > >> >> If yes, I think it is very important to include these fixes to > 2.7.6. > > >> >> > > >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12127 > > >> >> [2] > > >> >> > > >> > > > http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html > > >> >> > > >> >> On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov > > >> >> wrote: > > >> >> > > > >> >> > Alexey, > > >> >> > > > >> >> > Looks like important fixes, better to include them. > > >> >> > > > >> >> > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < > > >> >> alexey.goncha...@gmail.com>: > > >> >> > > > >> >> > > Igniters, > > >> >> > > > > >> >> > > Given that the RC1 vote did not succeed and we are still > waiting > > >> for > > >> >> a few > > >> >> > > minor fixes, may I suggest including these two tickest to the > > 2.7.6 > > >> >> scope? > > >> >> > > > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12127 > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12128 > > >> >> > > > > >> >> > > The first one has been already reported on the dev-list [1], > the > > >> >> second one > > >> >> > > may cause a state when an Ignite node cannot start on existing > > >> >> persisted > > >> >> > > data. Looking at the tickets, the fixes should be reasonably > > easy, > > >> so > > >> >> it > > >> >> > > should not shift 2.7.6 release timeline much. > > >> >> > > > > >> >> > > Thoughts? > > >> >> > > > > >> >> > > ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < > > nizhi...@apache.org > > >> >: > > >> >> > > > > >> >> > > > Separate repos for different Spark version is a good idea for > > me. > > >> >> > > > Anyway, can you help with Spark version migration, for now? > > >> >> > > > > > >> >> > > > В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет: > > >> >> > > > > Maybe the best solution today add for each new version of > > Spark > > >> >> the > > >> >> > > > > sub-module (Spark-2.3, Spark-2.4) or the separate > repository > > >> with > > >> >> > > modules > > >> >> > > > > for each version or another way with separate repository > and > > >> >> different > > >> >> > > > > branches like in > > >> >> > > https://github.com/datastax/spark-cassandra-connector > > >> >> > > > > > > >> >> > > > > 3 ways to support different versions with the different > costs > > >> of > > >> >> > > support > > >> >> > > > > > > >> >> > > > >
Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Alexandr, I almost sent the vote email :) When do you expect the fix to be in master and 2.7.6? ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin : > Folks, > > A critical bug was detected in .NET [1]. > > I understand that it’s a little bit late, but I propose to include this > issue into the release scope. > > PR is ready, currently waiting for a TC visa. > > Thoughts? > > [1] - https://issues.apache.org/jira/browse/IGNITE-12163 > > > From: Alexey Goncharuk > Sent: Monday, September 9, 2019 5:11 PM > To: dev > Cc: Dmitriy Govorukhin; Anton Kalashnikov > Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) > > Igniters, > > I just pushed the last ticket to ignite-2.7.6 branch; looks like we are > ready for the next iteration. > > Given that Dmitriy Pavlov will be unavailable till the end of this week, I > will take over the release. TC re-run is started. > > чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com>: > > > Hi Igniters, > > > > I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, > fix > > already in master and ignite-2.7.6 > > > > On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < > > dmitriy.govoruk...@gmail.com> wrote: > > > > > Hi Alexey, > > > > > > I think that I will finish work on the fix tomorrow. Fix already > > completed > > > but I need to get VISA from TC bot. > > > > > > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < > > > alexey.goncha...@gmail.com> wrote: > > > > > >> Folks, it looks like I was overly optimistic with the estimates for > the > > >> mentioned two tickets. > > >> > > >> Dmitriy, Anton, > > >> Can you share your vision when the issues will be fixed? Perhaps, it > > makes > > >> sense to release 2.7.6 with the already fixed issues and schedule > 2.7.7? > > >> Neither of them is a regression, so it's ok to release 2.7.6 as it is > > now. > > >> > > >> Thoughts? > > >> > > >> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < > > alexey.goncha...@gmail.com > > >> >: > > >> > > >> > Yes, my bad, forgot to include the link. That's the one. > > >> > > > >> > пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov : > > >> > > > >> >> Alexey, > > >> >> > > >> >> Does the issue [1] is related to this [2] discussion on the > > user-list? > > >> >> If yes, I think it is very important to include these fixes to > 2.7.6. > > >> >> > > >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12127 > > >> >> [2] > > >> >> > > >> > > > http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html > > >> >> > > >> >> On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov > > >> >> wrote: > > >> >> > > > >> >> > Alexey, > > >> >> > > > >> >> > Looks like important fixes, better to include them. > > >> >> > > > >> >> > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < > > >> >> alexey.goncha...@gmail.com>: > > >> >> > > > >> >> > > Igniters, > > >> >> > > > > >> >> > > Given that the RC1 vote did not succeed and we are still > waiting > > >> for > > >> >> a few > > >> >> > > minor fixes, may I suggest including these two tickest to the > > 2.7.6 > > >> >> scope? > > >> >> > > > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12127 > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12128 > > >> >> > > > > >> >> > > The first one has been already reported on the dev-list [1], > the > > >> >> second one > > >> >> > > may cause a state when an Ignite node cannot start on existing > > >> >> persisted > > >> >> > > data. Looking at the tickets, the fixes should be reasonably > > easy, > > >> so > > >> >> it > > >> >> > > should not shift 2.7.6 release timeline much. > > >> >> > > > > >> >> > > Thoughts? > > >> >> > > > > >> >> > > ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < > > nizhi...@apache.org > > >> >: > > >> >> > > > > >> >> > > > Separate repos for different Spark version is a good idea for > > me. > > >> >> > > > Anyway, can you help with Spark version migration, for now? > > >> >> > > > > > >> >> > > > В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет: > > >> >> > > > > Maybe the best solution today add for each new version of > > Spark > > >> >> the > > >> >> > > > > sub-module (Spark-2.3, Spark-2.4) or the separate > repository > > >> with > > >> >> > > modules > > >> >> > > > > for each version or another way with separate repository > and > > >> >> different > > >> >> > > > > branches like in > > >> >> > > https://github.com/datastax/spark-cassandra-connector > > >> >> > > > > > > >> >> > > > > 3 ways to support different versions with the different > costs > > >> of > > >> >> > > support > > >> >> > > > > > > >> >> > > > > In the case of separate repository I could help, for > example > > >> >> > > > > > > >> >> > > > > ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov < > > >> nizhi...@apache.org > > >> >> >: > > >> >> > > > > > > >> >> > > > > > Hello, Alexey. > > >> >> > > > > > > > >> >> > > > > > > But the > > >> >> > > > > > > compatibility with
RE: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Folks, A critical bug was detected in .NET [1]. I understand that it’s a little bit late, but I propose to include this issue into the release scope. PR is ready, currently waiting for a TC visa. Thoughts? [1] - https://issues.apache.org/jira/browse/IGNITE-12163 From: Alexey Goncharuk Sent: Monday, September 9, 2019 5:11 PM To: dev Cc: Dmitriy Govorukhin; Anton Kalashnikov Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager) Igniters, I just pushed the last ticket to ignite-2.7.6 branch; looks like we are ready for the next iteration. Given that Dmitriy Pavlov will be unavailable till the end of this week, I will take over the release. TC re-run is started. чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: > Hi Igniters, > > I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, fix > already in master and ignite-2.7.6 > > On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi Alexey, > > > > I think that I will finish work on the fix tomorrow. Fix already > completed > > but I need to get VISA from TC bot. > > > > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < > > alexey.goncha...@gmail.com> wrote: > > > >> Folks, it looks like I was overly optimistic with the estimates for the > >> mentioned two tickets. > >> > >> Dmitriy, Anton, > >> Can you share your vision when the issues will be fixed? Perhaps, it > makes > >> sense to release 2.7.6 with the already fixed issues and schedule 2.7.7? > >> Neither of them is a regression, so it's ok to release 2.7.6 as it is > now. > >> > >> Thoughts? > >> > >> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < > alexey.goncha...@gmail.com > >> >: > >> > >> > Yes, my bad, forgot to include the link. That's the one. > >> > > >> > пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov : > >> > > >> >> Alexey, > >> >> > >> >> Does the issue [1] is related to this [2] discussion on the > user-list? > >> >> If yes, I think it is very important to include these fixes to 2.7.6. > >> >> > >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12127 > >> >> [2] > >> >> > >> > http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html > >> >> > >> >> On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov > >> >> wrote: > >> >> > > >> >> > Alexey, > >> >> > > >> >> > Looks like important fixes, better to include them. > >> >> > > >> >> > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < > >> >> alexey.goncha...@gmail.com>: > >> >> > > >> >> > > Igniters, > >> >> > > > >> >> > > Given that the RC1 vote did not succeed and we are still waiting > >> for > >> >> a few > >> >> > > minor fixes, may I suggest including these two tickest to the > 2.7.6 > >> >> scope? > >> >> > > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12127 > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12128 > >> >> > > > >> >> > > The first one has been already reported on the dev-list [1], the > >> >> second one > >> >> > > may cause a state when an Ignite node cannot start on existing > >> >> persisted > >> >> > > data. Looking at the tickets, the fixes should be reasonably > easy, > >> so > >> >> it > >> >> > > should not shift 2.7.6 release timeline much. > >> >> > > > >> >> > > Thoughts? > >> >> > > > >> >> > > ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < > nizhi...@apache.org > >> >: > >> >> > > > >> >> > > > Separate repos for different Spark version is a good idea for > me. > >> >> > > > Anyway, can you help with Spark version migration, for now? > >> >> > > > > >> >> > > > В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет: > >> >> > > > > Maybe the best solution today add for each new version of > Spark > >> >> the > >> >> > > > > sub-module (Spark-2.3, Spark-2.4) or the separate repository > >> with > >> >> > > modules > >> >> > > > > for each version or another way with separate repository and > >> >> different > >> >> > > > > branches like in > >> >> > > https://github.com/datastax/spark-cassandra-connector > >> >> > > > > > >> >> > > > > 3 ways to support different versions with the different costs > >> of > >> >> > > support > >> >> > > > > > >> >> > > > > In the case of separate repository I could help, for example > >> >> > > > > > >> >> > > > > ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov < > >> nizhi...@apache.org > >> >> >: > >> >> > > > > > >> >> > > > > > Hello, Alexey. > >> >> > > > > > > >> >> > > > > > > But the > >> >> > > > > > > compatibility with Spark 2.3 will be broken, isn't it? > >> >> > > > > > > >> >> > > > > > Yes. > >> >> > > > > > > >> >> > > > > > > Do you have any > >> >> > > > > > > plans to support the different version of Spark without > >> >> loosing > >> >> > > your > >> >> > > > > > > >> >> > > > > > unique > >> >> > > > > > > expertise in Spark-Ignite integration? > >> >> > > > > > > >> >> > > > > > What do you mean by "my unique expertise"? :) > >> >> > > > > > > >> >> > >
[DISCUSSION] REST requests explicit authorization.
Igniters, I would like to suggest expanding the IgniteSecurity interface with a method for REST requests explicit authorization (e.g. public void authorize(GridRestRequest req) throws SecurityException;). Currently, REST request authorization starts in GridRestProcessor#authorize(GridRestRequest) where GridRestCommand is converted to SecurityPermission and then passed to IgniteSecurity#authorize(String, SecurityPermission) for final authorization. I propose to allow GridSecurityProcessor to make an authorization decision on its own by giving it GridRestRequest. This approach can help to avoid tough mapping GridRestCommand -> SecurityPermission and achieve much more flexibility in tweaking REST request authorization. I will appreciate your feedback on this proposal.
Re: Update Apache Zookeeper dependency
Pavel, I described changes in the ticket. ср, 11 сент. 2019 г., 15:10 Dmitrii Ryabov : > Ok, I'll do it. > > ср, 11 сент. 2019 г., 14:23 Pavel Kovalenko : > >> Hi Dmitrii, >> >> Thank you for contribution. I'll take a look at it. Could you please >> describe in the ticket what changes have you done besides version update >> and why they are needed? >> >> ср, 11 сент. 2019 г. в 14:06, Dmitrii Ryabov : >> >> > Hello, Igniters! >> > >> > I want to update Apachee Zookeeper version from 3.4.13 to 3.5.5 and >> Apache >> > Curator from 2.9.1 to 4.2.0 as part of IGNITE-11094 [1]. Any objections? >> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-11094 >> > >> >
[jira] [Created] (IGNITE-12163) CacheEntryEventType.Removed is not being rised
Alexandr Shapkin created IGNITE-12163: - Summary: CacheEntryEventType.Removed is not being rised Key: IGNITE-12163 URL: https://issues.apache.org/jira/browse/IGNITE-12163 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 2.7.5 Reporter: Alexandr Shapkin Assignee: Alexandr Shapkin Steps to reproduce: * Create a cache with user-defined type * Add an ICacheEntryEventListener in order to be notified of CacheEntryEventType.Removed events * Put a value in the cache * Remove that value Expected: CacheEntryEventType.Removed event get captured Actual: CacheEntryEventType.Updated event get captured Update: After these changes https://issues.apache.org/jira/browse/IGNITE-8714 New logic of detecting events (ContinuousQueryUtils.cs) now relies on the Object.Equals method which is not intuitive at all. -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: [IEP-35] Monitoring & Profiling. Phase 2
Nikolai, I'm trying to review this PR but it is too large. Could you please describe problem and design of implemented solution? Also javadocs for base interfaces aren't clear, too brief and doesn't give any imagine about whole picture. At present it is very hard to understand the purposes of new interfaces and walker generator, and design itself. On Fri, Sep 6, 2019 at 3:16 PM Nikolay Izhikov wrote: > > Hello, Igniters. > > IEP-35. Monitoring Phase2 is ready [1] > Please, join to the review! > > I've implemented: > > * Monitoring list engine. > * Following list implemented: > * Cache list > * Cache group list > * Compute task list > * Service list. > > Engine details: > > * `MonitoringList` added to store list data. > * Base interface `MonitoringRow` for list data created. > * Corresponding method added to `MetricExporterSpi` > * `JmxMetricExporterSpi`, `SqlViewExporterSpi`, `LogExporterSpi` updated to > support list export. > * JMX, SQL and other column-oriented SPI uses > `MonitoringRowAttributeWalker` to quickly traverse all list row attributes. > * Implementation of `MonitoringRowAttributeWalkerfor specificMonitoringRow` > can be generated with `MonitoringRowAttributeWalkerGenerator` > > I prepare follow-up PR [2], also. > Following lists implemented: > > * SQL tables > * SQL indexes > * SQL schemas > * SQL queries > * Continuous queries > * Text queries > * Transactions > * Cluster nodes > * Client connections(JDBC, ODBC, Thin) > > [1] https://github.com/apache/ignite/pull/6845 > [2] https://github.com/apache/ignite/pull/6790 > > > > пн, 10 июн. 2019 г. в 13:49, Nikolay Izhikov : > > > Hello, Igniters. > > > > Since Phase 1 will be merged in master soon I've created the ticket [1] > > for Phase 2. > > > > Scope of Phase 2(copy-paste from the ticket) > > > > Ability to collect lists of some internal object Ignite manage. > > Examples of such objects: > > > > * Caches > > * Queries (including continuous queries) > > * Services > > * Compute tasks > > * Distributed Data Structures > > * etc... > > > > > > 1. Fields for each list(that doesn't currently exists in Ignite) will be > > discussed in separate tickets > > 2. Metric Exporters (optionally) can support list export. > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11905 > > > > > > В Вт, 14/05/2019 в 16:42 +0300, Nikolay Izhikov пишет: > > > Ticket for IEP.Phase1 created - > > https://issues.apache.org/jira/browse/IGNITE-11848 > > > > > > > > > В Пн, 13/05/2019 в 18:06 +0300, Nikolay Izhikov пишет: > > > > Hello, Igniters. > > > > > > > > We have discussed this IEP [1] with Alexey Goncharyuk, Anton > > Vinogradov, Andrey Gura, Alexey Scherbakov and Pavel Kovalenko. > > > > > > > > Issues to address: > > > > > > > > 1. Study experience of following libs, tools: > > > > * OpenTracing > > > > * OpenSensus > > > > * DropWizard > > > > > > > > 2. Support histogram sensor: Sensor that collects values that gets > > into predefined segments > > > > > > > > 3. Use more widely used naming(like in OpenSensus?) > > > > > > > > 4. Consider the usage of OpenSensus as a default implementation for > > local metric storage. > > > > > > > > 5. To measure the performance penalty for metrics for 5_000 caches. > > > > > > > > 6. Some metrics should be part of public API and others are not(may be > > changed/removed in release without warnings). > > > > > > > > My plan for Phase #1 is the following: > > > > > > > > 1. Address the issues. > > > > 2. Prepare public API > > > > 3. Prepare PR for monitoring subsystem + existing metrics rewritten > > with it. > > > > 4. Prepare a PR with lists of each user API. > > > > 5. Collect feedback for a #4. > > > > 6. Design a log exposer. Consider the usage of JFR format or some > > other widely used, tool compatible format. > > > > > > > > [1] > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392 > > > > > > > > В Чт, 02/05/2019 в 14:02 +0300, Nikolay Izhikov пишет: > > > > > Hello, Maxim. > > > > > > > > > > > How will be recorded throughput sensor values which will require > > an interval for the rate calculations? > > > > > > > > > > I answered to this question in IEP "Design principles": > > > > > > > > > > ``` > > > > > Sensors should contain only raw values. No aggregation of numeric > > metrics on Ignite side. > > > > > Min, max, avg and other functions are the matter of an external > > monitoring system. > > > > > ``` > > > > > > > > > > Throughput is a function `(S(t2) - S(t1))/(t2-t1)` > > > > > where S(t) is the sensor value in some point of time t. > > > > > > > > > > Seems, throughput calculation is a responsibility of an external > > system. > > > > > > > > > > What do you think? > > > > > > > > > > > It seems to me that we can add an additional parameter of > > `sensitivityLevel` to provide for the user a flexible sensor control (e.g., > > INFO, WARN, NOTICE, DEBUG). > > > > > > > > > > For now, I think that all sensors and lists will be
[jira] [Created] (IGNITE-12162) Add the cluster name to the promt message "--deactivate" the control.sh
Kirill Tkalenko created IGNITE-12162: Summary: Add the cluster name to the promt message "--deactivate" the control.sh Key: IGNITE-12162 URL: https://issues.apache.org/jira/browse/IGNITE-12162 Project: Ignite Issue Type: Improvement Reporter: Kirill Tkalenko Assignee: Kirill Tkalenko Fix For: 2.8 Add the cluster name to the promt message "--deactivate" the control.sh -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12161) [ML] Add support of different classloaders for client code
Alexey Platonov created IGNITE-12161: Summary: [ML] Add support of different classloaders for client code Key: IGNITE-12161 URL: https://issues.apache.org/jira/browse/IGNITE-12161 Project: Ignite Issue Type: Improvement Components: ml Reporter: Alexey Platonov Assignee: Alexey Platonov Currently we support just one classloader for unknown classes on server side. Potentially client can handle several classloaders and we should support this situation. -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: Update Apache Zookeeper dependency
Ok, I'll do it. ср, 11 сент. 2019 г., 14:23 Pavel Kovalenko : > Hi Dmitrii, > > Thank you for contribution. I'll take a look at it. Could you please > describe in the ticket what changes have you done besides version update > and why they are needed? > > ср, 11 сент. 2019 г. в 14:06, Dmitrii Ryabov : > > > Hello, Igniters! > > > > I want to update Apachee Zookeeper version from 3.4.13 to 3.5.5 and > Apache > > Curator from 2.9.1 to 4.2.0 as part of IGNITE-11094 [1]. Any objections? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-11094 > > >
Re: Update Apache Zookeeper dependency
Hi Dmitrii, Thank you for contribution. I'll take a look at it. Could you please describe in the ticket what changes have you done besides version update and why they are needed? ср, 11 сент. 2019 г. в 14:06, Dmitrii Ryabov : > Hello, Igniters! > > I want to update Apachee Zookeeper version from 3.4.13 to 3.5.5 and Apache > Curator from 2.9.1 to 4.2.0 as part of IGNITE-11094 [1]. Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-11094 >
[jira] [Created] (IGNITE-12160) Fix RPM packages build
Peter Ivanov created IGNITE-12160:
-
Summary: Fix RPM packages build
Key: IGNITE-12160
URL: https://issues.apache.org/jira/browse/IGNITE-12160
Project: Ignite
Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov
{{Tue 10 Sep 2019 Peter Ivanov - 2.7.6-1}} date is in
invalid format and should be fixed.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
Update Apache Zookeeper dependency
Hello, Igniters! I want to update Apachee Zookeeper version from 3.4.13 to 3.5.5 and Apache Curator from 2.9.1 to 4.2.0 as part of IGNITE-11094 [1]. Any objections? [1] https://issues.apache.org/jira/browse/IGNITE-11094
Re: Start contributing Ignite
Hello, Denis, thank you for support, happy to became part of your community! I don't have any Ignite experience, but I have bigdata-related experience: working on several projects with Hadoop, Spark, Kafka, etc. I'm excited with Ignite project, and hope I will use it in future projects, that is why i decided to contribute it)) I started to work on IGNITE-12032. I investigated it and wrote a comment with investigation results. I'd like to continue working on it, could you please assign it on me (or may be it's OK to assign it to me by myself)? Best Regards, Lev Agafonov From: Denis Magda Sent: Wednesday, September 11, 2019 1:21 AM To: dev Subject: Re: Start contributing Ignite Hello Lev! Welcome, it's nice to see you as part of the community. I've just added you to the contributors'rs list in JIRA. Please go ahead and select a task you'd like to work on. Btw, do you already have any Ignite-related experience? - Denis On Mon, Sep 9, 2019 at 6:36 AM Lev Agafonov wrote: > Hello, team! > My name is Lev, I'm Java developer from Russia, Nizhny Novgorod. > I'd be kindly glad to join your community and start contributing Ignite. > Could you please grant to my Jira account 'levagafonov' contributor > permissions? > > > Best Regards, > > Lev Agafonov >
Re: Nabble message wrapping
Denis, I did some investigation on this and started a Nabble support thread: http://support.nabble.com/Line-wrapping-in-quotes-td7604136.html It turned out, that Nabble has a little to do with it. It’s the mail list itself. When you send a plain text message to the dev list either from Nabble or in any other way, it’s getting wrapped to be 80 characters wide. HTML messages don’t have this issue. Nabble uses plain text by default. User list doesn’t wrap quotes though, even if you use plain text format. You can see that my reply in the following thread is wrapped, but not the quote: http://apache-ignite-users.70518.x6.nabble.com/Ignition-Start-Timeout-if-connection-is-unsuccessful-td29289.html I see two possibilities of solving this issue: 1. Make Nabble always send messages in HTML format somehow. The issue will still occur for other mail clients though. 2. Change the ezmlm configuration to match the one of the users list. We need to find a person who has access to the Apache infra in order to do this. Denis On 11 Sep 2019, 00:53 +0300, Denis Magda , wrote: > Denis, could you set up the dev list the way needed? > > - > Denis > > > On Thu, Aug 29, 2019 at 1:18 PM Denis Magda wrote: > > > Denis, > > > > I granted your account the admin access. Please do all the required > > changes and let me know once done. > > > > - > > Denis > > > > > > On Thu, Aug 29, 2019 at 2:00 AM Denis Mekhanikov > > wrote: > > > > > Guys, > > > > > > Any update? Who has a Nabble admin account for the developers list? > > > > > > Denis > > > On 27 Aug 2019, 14:55 +0300, Dmitriy Pavlov , wrote: > > > > Hi Denis, > > > > > > > > AFAIK, nabble forums are service, which resides outside of ASF infra. > > > They > > > > have their separate support/feedback form. > > > > > > > > Maybe some PMC members could have some credentials for this service. If > > > so, > > > > please share login info in SVN/private/credentials. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > >
