Re: 2.9.1 release scope and dates
Yaroslav, there is another bug for 2.9.1 release https://issues.apache.org/jira/browse/IGNITE-13572 чт, 5 нояб. 2020 г., 19:23 Yaroslav Molochkov : > Ivan, hi! > Sure. > > UPD: i am the release manager and will be doing this with Maxim's help > (since i don't have some user permissions) > > On Thu, Nov 5, 2020 at 6:24 PM Ivan Daschinsky > wrote: > > > Hi. I'd suggest to add this issue. This is a usability improvement for zk > > discovery, and also this patch incorporates fixes for JMX metrics > > concurrency issues > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-13577 > > > > чт, 5 нояб. 2020 г., 16:20 Yaroslav Molochkov : > > > > > Igniters! > > > > > > I'd like to help with the 2.9.1 release. The scope of this release > > includes > > > following issues: > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13676?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1 > > > > > > Maxim Muzafarov agreed to help me with the process and he will be the > > > release manager. > > > > > > Scope freeze: Nov. 12th > > > Code freeze: Nov. 19th > > > Voting date: Nov. 26th > > > Release date: Nov. 31st > > > > > > Tickets that were added (or to be added) to the scope don't bring new > > > features but various bug fixes. > > > > > >
[DISCUSS] Use GridNioServer in Java thin client
Igniters, This is a continuation of "Use Netty for Java thin client" [1], I'm starting a new thread for better visibility. The problems with current Java thin client are: * Socket writes block user threads * Every connection uses a separate listener thread (with partition awareness there is a thread for every server node within a single IgniteClient) GridNioServer can work in client mode and solves both of these problems. It is the most practical choice as well at the moment - no extra dependencies required. A potential drawback is increased coupling between thin client and core code, which I'm going to mitigate by abstracting GridNioServer behind a simpler facade, so we can replace it with Netty or something else easier if we decide to split the code. Thoughts, objections? [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Use-Netty-for-Java-thin-client-td49732.html
[MTCGA]: new failures in builds [5722527] 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 Disk Page Compressions https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_DiskPageCompressions?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 20:37:40 08-11-2020
[MTCGA]: new failures in builds [5722596] 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 JCache TCK 1.1 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_JCacheTck11?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 23:37:39 08-11-2020
IGNITE-13648 Tests failing for extensions modules
Hi, I have raised a PR for the following jira issue. Jira : https://issues.apache.org/jira/browse/IGNITE-13648 PR : https://github.com/apache/ignite-extensions/pull/29 We are observing following exceptions in the test failures: Caused by: org.apache.ignite.IgniteCheckedException: Remote node has peer class loading enabled flag different from local [locId8=dfc9ddaf, locPeerClassLoading=true, rmtId8=fee013c8, rmtPeerClassLoading=false, rmtAddrs=[9dc3d9f4b167/127.0.0.1, /172.17.0.6], rmtNode=ClusterNode [id=fee013c8-d398-4cdc-92f5-c368c5fc663a, order=1, addr=[127.0.0.1, 172.17.0.6], daemon=false]] at org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest.beforeTestsStarted(IgniteSinkConnectorTest.java:136) Please review and share feedback. Regards, Saikat
IGNITE-12951 Update documents for migrated extensions
Hi, I have raised a PR for the following issue. Jira : https://issues.apache.org/jira/browse/IGNITE-12951 PR : https://github.com/apache/ignite-extensions/pull/30 This is an initial PR in Ignite Extensions repo. I will work on another PR in ignite repo for the remaining changes. Regards, Saikat
Re: IGNITE-12951 Update documents for migrated extensions
Hello, Saikat.
As far as I can see you changed artifactId of the extensions not only docs.
Do we have an agreement to name each extension as «{extension-name}-ext» like
«ignite-camel-ext» or similar?
We don’t have much extensions release, so maybe it will be better to have
naming like
groupId=org.apache.ignite.extensions
artifactId=ignite-camel
What do you think?
> 9 нояб. 2020 г., в 05:36, Saikat Maitra написал(а):
>
> Hi,
>
> I have raised a PR for the following issue.
>
> Jira : https://issues.apache.org/jira/browse/IGNITE-12951
> PR : https://github.com/apache/ignite-extensions/pull/30
>
> This is an initial PR in Ignite Extensions repo. I will work on another PR
> in ignite repo for the remaining changes.
>
> Regards,
> Saikat
