[MTCGA]: new failures in builds [6440982] 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 test failure in master IgniteConfigurationTest.TestDefaultSpi https://ci2.ignite.apache.org/test/2016195675123383739?currentProjectId=IgniteTests24Java8=%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:38:24 18-05-2022
[Ignite Summit] The Schedule for June 14th Virtual Event is Live
Hi Igniters! On June 14th speakers from industry-leading companies, including Finance, Travel, Software Development and IoT will share their experience and vision: The future of Apache Ignite: Bridging from Complexity to Simplicity, Scale, and Community - Nikita Ivanov, GridGain, Founder & CTO Lightning Fast Flight Searches on Expedia Using Apache Ignite - Rohit Goel, Expedia Group, Software Engineer and Bhanu Choudhary, Expedia Group, Principal Software Development Engineer Data Management in the IoT with Apache Ignite - Piotr Wykowski, Transition Technologies PSC, IoT Evangelist Apache Ignite 3: Improving the Beloved Platform - Val Kulichenko, Apache Ignite PMC member Exposing Legacy Mainframe Data with Apache Ignite - Timothy Anderson, M Bank Software Engineer And more! Check the complete schedule https://ignite-summit.org/2022-june/schedule/ (click on the sessions’ title to go to the page with description) Register to join sessions and meet Ignite developers and users from around the world: https://hopin.com/events/ignite-summit-june-14 Cheers, Kseniya
Re: [RESULT] [VOTE] Release Extensions Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1, Ignite Zookeeper IP Finder 1.0.0 RC1
Folks, I'm sorry for the mistake with the Spring Data Extension version in the thread title (copy-pasted from the wrong thread). Of course, the correct version which is being released - Ignite Spring Data Extension 2.0.0. See: https://dist.apache.org/repos/dist/release/ignite/ignite-extensions/ignite-spring-data-ext/2.0.0/ On Tue, 17 May 2022 at 15:44, Maxim Muzafarov wrote: > > Hello, Igniters! > > Th Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1, > Ignite Zookeeper IP Finder 1.0.0 RC1 extensions have been accepted. > > 3 - "+1" votes received. > > Here are the +1 votes received: > > - Anton Vinogradov (binding) > - Alexey Plehanov (binding) > - Nikolay Izhikov (binding) > > Here is the link to the voting thread - > https://lists.apache.org/thread/njqls47r3jn920546q63xknyr2y5yd5l > > Thank you!
[RESULT] [VOTE] Release Extensions Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1, Ignite Zookeeper IP Finder 1.0.0 RC1
Hello, Igniters! Th Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1, Ignite Zookeeper IP Finder 1.0.0 RC1 extensions have been accepted. 3 - "+1" votes received. Here are the +1 votes received: - Anton Vinogradov (binding) - Alexey Plehanov (binding) - Nikolay Izhikov (binding) Here is the link to the voting thread - https://lists.apache.org/thread/njqls47r3jn920546q63xknyr2y5yd5l Thank you!
Re: IEP-90 Ignite 3 Client Lifecycle
1. I've tried to clarify IDs part; 2. Maybe you are right, though in this case we'd need to use authentication in ConnectionRestoreReq. Which sounds reasonable to me. Best Regards, Igor On Tue, May 17, 2022 at 10:47 AM Pavel Tupitsyn wrote: > Igor, > > The proposal looks good to me. Very detailed! > > A couple comments: > > 1. There is a bit of a term mixup with "Connection ID", "Node ID", "Token" > - can you please review those? > > 2. > The Connection ID should be generated using a proper secure algorithm > (additional research is required here) to make sure an intruder can not > generate an existing Connection ID > Not sure about the reasoning here. I think randomUUID() should be enough: > - In the case of an unsecured cluster it does not matter, because anyone > can do anything. > - In the case of a secured cluster it does not matter, because > authentication/authorization keeps intruders out. > > > On Mon, May 16, 2022 at 11:07 PM Igor Sapego wrote: > > > Hi, Igniters > > > > I've prepared an IEP for Ignite 3 Client Lifecycle [1]. The main idea is > to > > define client lifecycle as well as core algorithms and mechanisms used by > > clients. This proposal can be used as a reference for implementation of a > > new client for Ignite when dealing with such problems as: > > > >- Resolving of user-provided addresses; > >- Initial connection to a cluster; > >- Maintaining cluster connection; > >- Connection recovery; > >- Connection break handling. > > > > So take a look and let me know what you think guys. > > > > [1] - > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-90+Client+Lifecycle > > > > Best Regards, > > Igor > > >
A new feedback has been added : 77
A new feedback has been added, go to bugyard.io to see all the details... https://bugyard.io A new feedback has been added "It seem that NoOpWarmUpConfiguration should be there." Â by shishkovilja View feedback https://app.bugyard.io/web/app/rycqZJDyY/f/62820a2c05925900149db68c
[MTCGA]: new failures in builds [6434033] 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 ClusterReadOnlyModeSelfTest.testIgniteUtilityCacheAvailableForUpdatesOnReadOnlyCluster https://ci2.ignite.apache.org/test/5843797864653296257?currentProjectId=IgniteTests24Java8=%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 06:53:21 17-05-2022
Re: IEP-90 Ignite 3 Client Lifecycle
Igor, The proposal looks good to me. Very detailed! A couple comments: 1. There is a bit of a term mixup with "Connection ID", "Node ID", "Token" - can you please review those? 2. > The Connection ID should be generated using a proper secure algorithm (additional research is required here) to make sure an intruder can not generate an existing Connection ID Not sure about the reasoning here. I think randomUUID() should be enough: - In the case of an unsecured cluster it does not matter, because anyone can do anything. - In the case of a secured cluster it does not matter, because authentication/authorization keeps intruders out. On Mon, May 16, 2022 at 11:07 PM Igor Sapego wrote: > Hi, Igniters > > I've prepared an IEP for Ignite 3 Client Lifecycle [1]. The main idea is to > define client lifecycle as well as core algorithms and mechanisms used by > clients. This proposal can be used as a reference for implementation of a > new client for Ignite when dealing with such problems as: > >- Resolving of user-provided addresses; >- Initial connection to a cluster; >- Maintaining cluster connection; >- Connection recovery; >- Connection break handling. > > So take a look and let me know what you think guys. > > [1] - > https://cwiki.apache.org/confluence/display/IGNITE/IEP-90+Client+Lifecycle > > Best Regards, > Igor >
