Re: Thin client test suites failure

After a little bit more experimentation I tend to think that adding java.transaction module is not needed and even brings a negative effect. E.g. if we use an ignite binary release and enable optional jta module (by copying libraries to lib folder) then a node simply fails to start (failing to reso

Data loading with thin clients

Igor, Igniters, I've come across a couple of posts recently where users attempted to preload initial data with a thin client like Python: https://stackoverflow.com/questions/56778778/apache-ignite-inserts-extremely-slow/56791088#56791088 Our JDBC/ODBC drivers have a special streaming mode that bo

Ignite Modularization

Ignite developers and users, I'd like us to consider Ignite modularization as part of Ignite 3.0 timeframe. Presently, Ignite codebase mixes both core capabilities with 3rd party integrations. It leads to the following: - Cumbersome and continuously growing codebase with many 3rd-party depe

Re: [DISCUSSION][IEP-35] Metrics configuration

Nikolay, My only concert is that we should have the metrics framework configuration as the first-citizen of the framework itself. This way, we can configure the metrics not only from file, but change the metrics parameters in runtime from JMX or command-line, etc. Another concern is to have an abi

Re: [DISCUSSION][IEP-35] Metrics configuration

Nikolay, I also agree with your approach thank, you for the explanation. One minor remark: maybe it will be better to explicitly indicate in config the type of the metric? In nutshell: HistrogramMetric: cache.my-cahe.GetLatency=50,100,250,500 HitRateMetric: cache.my-cache.RebalancingKeysRate=6000

Re: IGNITE-8772 WebSessionFilter does not work with jetty 9.4 anymore

Hello! Thank you for this fix, I have applied it! Regards, -- Ilya Kasnacheev вс, 16 июн. 2019 г. в 00:17, Saikat Maitra : > Hi, > > I have raised a PR for the following issue > > Issue : https://issues.apache.org/jira/browse/IGNITE-8772 > > PR : https://github.com/apache/ignite/pull/6612 > >

Re: [DISCUSSION][IEP-35] Metrics configuration

Hello, Anton. Thanks for an answer! > Let's just make sure this syntax is extendable. Yes, I ~can~ will! > I'd like to count only latency greater than 37ms (0-37 - > ignored, 37-52, 52-infinity - recorded), it should be possible to skip some > values. Currently, histogram metric don't support

Re: [DISCUSSION] Ignite 3.0 and to be removed list

Anton, I would like to pull-up the discussion regarding the near caches - I cannot agree this is a feature that needs to be removed. Near caches provide significant read performance improvements and, to the best of my knowledge, are used in several cases in production. Can you elaborate on the sho

Re: [DISCUSSION][IEP-35] Metrics configuration

Nikolay, The approach looks good to me. Let's just make sure this syntax is extendable. For example, I'd like to count only latency greater than 37ms (0-37 - ignored, 37-52, 52-infinity - recorded), it should be possible to skip some values. Another case is to specify 2+ windows for same metric, e

[jira] [Created] (IGNITE-11944) [IEP-35] OpencensusExporter should export Histogram metrics

Nikolay Izhikov created IGNITE-11944: Summary: [IEP-35] OpencensusExporter should export Histogram metrics Key: IGNITE-11944 URL: https://issues.apache.org/jira/browse/IGNITE-11944 Project: Ignite

[DISCUSSION][IEP-35] Metrics configuration

Hello, Igniters. As you may know, I've contributed Phase1 [1] for IEP-35 [2]. Now we have metrics subsystem and can create and export any metrics from Ignite. I think user(administrator of Ignite) should be able to configure some metrics params in a common way [3] I propose to use the same way