Re: [DISCUSS] Remove TC badge from README.md

Folks, I created a ticket [1] and prepared PR with magic number =). Please review. [1] https://issues.apache.org/jira/browse/IGNITE-12987 Best regards, Ivan Pavlukhin пн, 4 мая 2020 г. в 10:01, Ivan Pavlukhin : > > Hi Igniters, > > Inspired by a neighbor thread about PR checks [1]. It brought

[jira] [Created] (IGNITE-12987) Remove TC badge from README.md

Ivan Pavlukhin created IGNITE-12987: --- Summary: Remove TC badge from README.md Key: IGNITE-12987 URL: https://issues.apache.org/jira/browse/IGNITE-12987 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-12986) Redis mget command is broken

Vishnu Bharathi created IGNITE-12986: Summary: Redis mget command is broken Key: IGNITE-12986 URL: https://issues.apache.org/jira/browse/IGNITE-12986 Project: Ignite Issue Type: Bug

[MTCGA]: new failures in builds [5278999] 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 GridCachePartitionedNodeRestartTest.testRestartWithTxFourNodesNoBackups https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tes

Re: IEP-44 Thin Client Discovery

Pavel, Since we have a notification mechanism for thin clients now, we can implement a subscription to some types of events and this can be used to inform a client about topology change as well. I think it's a more appropriate way to detect topology changes than ping requests. But approach with pi

Re: Using GraalVM instead of standard JVM

I just switched out OpenJDK and used GraalVM instead. Everything seemed to work but I wasn’t looking terribly hard. We’d need to do some more QA but I think chances are good that it’ll work just fine. Regards, Stephen >> On 6 May 2020, at 20:31, Denis Magda wrote: > Stephen, that's terrific!

Re: Using GraalVM instead of standard JVM

Stephen, that's terrific! To Ivan's first question, did you just swap HotSpot with GraalVM and got the thing working? Or did it require some extra work? - Denis On Wed, May 6, 2020 at 10:10 AM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > I’ve been playing around with it. I’ve

Re: [DISCUSSION] Ignite WebConsole Deprecation

Folks, Personally, I like the idea of Apache Attic [1] suggested by Saikat. We are not discontinuing Ignite WebConsole because it became useless like it was with Hadoop Accelerator. The tool has good capabilities such as the configuration wizard, and the only problem is that we no longer want to s

Re: Using GraalVM instead of standard JVM

Hi, My thoughts: * Does anyone has an idea what prevents us to run Ignite on GraalVM? * Regarding Python. I suppose every JVM can leverage jython [1]. Also I think we should support all significant features on HotSpot as well. [1] https://www.jython.org/ Best regards, Ivan Pavlukhin ср, 6 мая 2

Re: Extended logging for rebalance performance analysis

Hello. Let's look at existing rebalancing log for a single group: [2020-05-06 20:56:36,999][INFO ][...] Rebalancing scheduled [order=[ignite-sys-cache, cache1, cache2, default], top=AffinityTopologyVersion [topVer=3, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT, node=9d9edb7b-eb01-47a1-8ff9-fef715d00

Re: Extended logging for rebalance performance analysis

Kirill, Thank you for raising this topic. It's true that the rebalance process still requires additional information for analyzing issues. Please, don't think that I'm against your changes :-) * My short answer. * We won't do performance analysis on the production environment. Each time we need

Re: Using GraalVM instead of standard JVM

I’ve been playing around with it. I’ve was really impressed that I could run JavaScript on Ignite with comparatively little code: https://github.com/sdarlington/ignite-graalvm I’ve not been looking at performance, though. Regards, Stephen > On 6

Re: [DISCUSS] Data loss handling improvements

ср, 6 мая 2020 г. в 12:54, Anton Vinogradov : > Alexei, > > 1,2,4,5 - looks good to me, no objections here. > > >> 3. Lost state is impossible to reset if a topology doesn't have at least > >> one owner for each lost partition. > > Do you mean that, according to your example, where > >> a node2 ha

Re: Using GraalVM instead of standard JVM

I'll leave this reference here so that we have a better understanding of why it's worthwhile to support GraalVM: https://blogs.oracle.com/graalvm/apache-spark —lightning-fast-on-graalvm-enterprise Spark benefits from running on GraalVM, so should we. Apart from memory usage and performance advanta

Re: Extended logging for rebalance performance analysis

Hi, IGNITE_WRITE_REBALANCE_PARTITION_DISTRIBUTION_THRESHOLD - threshold > duration rebalance of cache group after which partitions distribution is > output, set in milliseconds, default value is 10 minutes. Does it mean that if the rebalancing process took less than 10 minutes, only a short vers

Re: IEP-44 Thin Client Discovery

Igniters, let's discuss the following issue: For partition awareness, and now for cluster discovery, we use a response flag to detect topology changes. The problem is - if the client does not do anything (user code does not perform operations), then we'll never know about topology changes and may

Re: [DISCUSSION] Ignite WebConsole Deprecation

Hello, +1 to remove this component or move it to a separate repository if someone wants to maintain it. In case the web console provides useful features, we should consider how to add them to our command-line utilities, if possible. Thanks, Slava. ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov : >

[jira] [Created] (IGNITE-12985) Fix unguarded log.info/log.debug/log.trace usages

Sergey Antonov created IGNITE-12985: --- Summary: Fix unguarded log.info/log.debug/log.trace usages Key: IGNITE-12985 URL: https://issues.apache.org/jira/browse/IGNITE-12985 Project: Ignite Is

Re: [DISCUSSION] Ignite WebConsole Deprecation

Hello. +1 to remove any graphical utilities from the Ignite core. I think we should maintain and support only cmd, JMX, and other «core» tools. We shouldn't waste our resources on supporting pretty looking UI tools. > 2 мая 2020 г., в 04:05, Saikat Maitra написал(а): > > Hello Denis, > > I a

Re: Discovery-based services deployment guarantees question

Hello, Igniters. I am working on IGNITE-12894 - [1]. It seems that it has the root cause which is similar to the problem described in this thread. To solve these problems, I propose to change the behavior of the IgniteServiceProcessor#serviceTopology if the timeout argument is 0. At the momen

Crash recovery speed-up #3, Cellular Switch

Igniters, PME-free switch [1] (since 2.8) skips PME on node left when possible (baseline + fully rebalanced cluster). This means we already wait for nothing (except recovery) to perform the switch. This optimization allows continuing already started operations during or after the switch if they ar

Re: [DISCUSS] Data loss handling improvements

Alexei, 1,2,4,5 - looks good to me, no objections here. >> 3. Lost state is impossible to reset if a topology doesn't have at least >> one owner for each lost partition. Do you mean that, according to your example, where >> a node2 has left, soon a node3 has left. If the node2 is returned to >>

[jira] [Created] (IGNITE-12984) Distributed join incorrectly processed when batched:unicast on primary key is used

Ilya Kasnacheev created IGNITE-12984: Summary: Distributed join incorrectly processed when batched:unicast on primary key is used Key: IGNITE-12984 URL: https://issues.apache.org/jira/browse/IGNITE-12984

[DISCUSS] Data loss handling improvements

Folks, I've almost finished a patch bringing some improvements to the data loss handling code, and I wish to discuss proposed changes with the community before submitting. *The issue* During the grid's lifetime, it's possible to get into a situation when some data nodes have failed or mistakenly

[jira] [Created] (IGNITE-12983) Logging exceptions inside IgniteSecurityProcessor#withContext(java.util.UUID)

Denis Garus created IGNITE-12983: Summary: Logging exceptions inside IgniteSecurityProcessor#withContext(java.util.UUID) Key: IGNITE-12983 URL: https://issues.apache.org/jira/browse/IGNITE-12983 Proje

[RESULT][VOTE] Release Apache Ignite Spring Boot extensions 1.0.0 RC2

The vote for a new release candidate is closed, now Vote result: Vote passes with 4 votes +1 (4 binding +1 votes), no 0 and no -1. +1 votes: - Nikolay Izhikov (binding) - Maxim Muzafarov (binding) - Saikat Maitra (binding) - Denis Magda (binding) Vote thread https://lists.apache.org/thread.html

Re: ExecutorServices hide assertions without logging and node stop

Hello, Maxim. I can confirm this itching issue. It also happens when some custom Security plugin throws an exception while processing a communication message. ``` UUID newSecSubjId = secSubjId != null ? secSubjId : nodeId; try (OperationSecurityContext s = ctx.security().withContext(newSecSubjI