[jira] [Created] (IGNITE-14512) General purpose DirectMemoryRegion.
Andrey Mashenkov created IGNITE-14512: - Summary: General purpose DirectMemoryRegion. Key: IGNITE-14512 URL: https://issues.apache.org/jira/browse/IGNITE-14512 Project: Ignite Issue Type: Improvement Reporter: Andrey Mashenkov h3. Motivation. Now Ignite 2 have a number of place of direct Unsafe class usage. We already ported DirectBuffer for streams/connections and going to port a PageMemory to Ignite 3. Rewriting Unsafe to VarHandles looks impossible for most of the cases I've no idea why there is VarHandle wrapper e.g. for direct LongBuffer, but there is no way to get DirectBB with CAS operation in Java. h3. Description. Let's localize and restrict direct Unsafe class usage to few classes in a single module. * Design MemorySegment API with random offset access using Unsafe. * Multiple implementation for Big-Endian and Little-Endian cases. * Align-aware wrapper or implementation (non-volatile operations only). For systems that has limited non-aligned access. * Add CAS operations support (only aligned) * Add adapter to access memory segment slice() via ByteBuffer interface. Then replace DirectBuffer in network module. And port PageMemory regarding the new concept. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[MTCGA]: new failures in builds [5960628] 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 Control Utility https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility?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 13:10:19 10-04-2021
Re: Static hierarchy in jmx tree
Hello, everyone! Because there was no cons, I have started developing and I have pull request https://github.com/apache/ignite/pull/8972 now. Review it please. > Sent: Friday, December 18, 2020 at 4:58 PM > From: "¿ ¿" > To: dev@ignite.apache.org > Subject: Static hierarchy in jmx tree > > Hello, everyone! > > Ignite has a changeable jmx hierarchy now. It may lead a lot of problems for > product maintenance and monitoring: > - By default where would be classloader that change every time that node > has been restarted. It will lead to rediscover all metrics for node. > - It's hard to create a single template for different deployments. For > example we should have about 4 different templates for each combination of > classLoader and instanceName. > - It's hard for engineers to switch between different hierarchies. You > have to recreate anything you already have. > > I've created https://issues.apache.org/jira/browse/IGNITE-12920 to change > this behavior. I am going to: > > 1. Change IGNITE_MBEAN_APPEND_CLASS_LOADER_ID default value to false > 2. Use instanceName in any case. If this option is set, the value will be > used, otherwise use consistentId if it's null use nodeId > 3. Add option IGNITE_MBEAN_APPEND_INSTANCE_NAME for backward > compatibility. True by default > 4. Update documentation according to changes > > What do you think? > > Igor > >
