Re: Stop sending IGNITE Created e-mails to dev@

Huge +1 to this. I've already brought up this topic in the past: http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html I hope some day newcomers won't need to set up their email filters when they come to the developers list. Denis ср, 14 апр. 2021 г. в 18:07, Atri

Re: IGNITE-13399 Fix access right issues in computation of system metrics

Mirza, Thanks for the review! Can somebody help with a merge? Denis чт, 1 апр. 2021 г. в 13:07, Mirza Aliev : > Hi Denis! > > Thank you for the PR! > > I've left a comment. > > Best regards, > Mirza Aliev > > чт, 1 апр. 2021 г. в 11:48, Denis Mekhanikov : &

[jira] [Created] (IGNITE-14505) Print information about striped pool in metrics for local node

Denis Mekhanikov created IGNITE-14505: - Summary: Print information about striped pool in metrics for local node Key: IGNITE-14505 URL: https://issues.apache.org/jira/browse/IGNITE-14505 Project

IGNITE-13399 Fix access right issues in computation of system metrics

Hi everyone! I've prepared a PR for the following issue: https://issues.apache.org/jira/browse/IGNITE-13399 Currently on Java 8 CpuLoad metric is reported to be equal to -1 when running in embedded mode. Could anyone take a look? Thanks! Denis

[jira] [Created] (IGNITE-14349) Add query attributes to QueryHistoryTracker#qryHist and QueryHistory

Denis Mekhanikov created IGNITE-14349: - Summary: Add query attributes to QueryHistoryTracker#qryHist and QueryHistory Key: IGNITE-14349 URL: https://issues.apache.org/jira/browse/IGNITE-14349

[jira] [Created] (IGNITE-13886) Change units of cache-related histograms to milliseconds

Denis Mekhanikov created IGNITE-13886: - Summary: Change units of cache-related histograms to milliseconds Key: IGNITE-13886 URL: https://issues.apache.org/jira/browse/IGNITE-13886 Project: Ignite

[jira] [Created] (IGNITE-13642) Nodes fail when they meet objects of unknown type in metastorage

Denis Mekhanikov created IGNITE-13642: - Summary: Nodes fail when they meet objects of unknown type in metastorage Key: IGNITE-13642 URL: https://issues.apache.org/jira/browse/IGNITE-13642 Project

[jira] [Created] (IGNITE-13631) Improve names and descriptions of data storage metrics

Denis Mekhanikov created IGNITE-13631: - Summary: Improve names and descriptions of data storage metrics Key: IGNITE-13631 URL: https://issues.apache.org/jira/browse/IGNITE-13631 Project: Ignite

Re: [DISCUSSION] User-facing API for managing Maintenance Mode

Sergey, Thanks for such a detailed description! I find the first option more attractive. I see the maintenance mode as a special state of a node that a user can turn on and off. If you want to perform defragmentation, you need to turn that mode on. If you try to do it in a normal mode, you get

Re: Too many messages in log in case of exceptions in user computations.

Nikolay, First the error is printed on the map node, then on the reduce node, and then the exception is thrown from the method that triggered the execution. The compute grid seems to use the "print an error message and delegate exception to the caller" which doesn't make much sense. If you don't

[jira] [Created] (IGNITE-13487) Decrease logging level for exceptions throws from compute engine

Denis Mekhanikov created IGNITE-13487: - Summary: Decrease logging level for exceptions throws from compute engine Key: IGNITE-13487 URL: https://issues.apache.org/jira/browse/IGNITE-13487 Project

[jira] [Created] (IGNITE-13399) CpuLoad metric reports -1 under Java 11 in embedded mode

Denis Mekhanikov created IGNITE-13399: - Summary: CpuLoad metric reports -1 under Java 11 in embedded mode Key: IGNITE-13399 URL: https://issues.apache.org/jira/browse/IGNITE-13399 Project: Ignite

[jira] [Created] (IGNITE-13398) NPE in IgniteServiceProcessor when destroying a cache

Denis Mekhanikov created IGNITE-13398: - Summary: NPE in IgniteServiceProcessor when destroying a cache Key: IGNITE-13398 URL: https://issues.apache.org/jira/browse/IGNITE-13398 Project: Ignite

Distinguishing node-local metrics from cluster-wide

Hi Igniters! My team and I are building a monitoring system on top of the new metrics framework described in the following IEP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392 So far it's going well, but we'd like to improve the way metrics are exported from Ignite.

Re: [DISCUSSION] Cache warmup

I keep in mind, now > it will be possible to add own warm-up strategy implementations. Which will > be possible to implement in different ways. > > At the moment, I suggest implementing one "Load all" strategy, which will > be effective if persistent storage is less than RAM

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Guys, Is there a chance to squeeze the fix for the following issue in: https://issues.apache.org/jira/browse/IGNITE-13306 ? The issue makes the CPU load metric show -1 on Java 11. This is a quite important metric, and this bug makes it harder

Re: [DISCUSSION] Cache warmup

Kirill, That will be a great feature! Other popular databases already have it (e.g. Postgres: https://www.postgresql.org/docs/11/pgprewarm.html), so it's good that we're also going to have it in Ignite. What implementation of CacheWarmup interface do you have in mind? Will there be some

Re: Listening cluster activation events by default

Alex, I think it makes sense to enable distribution of these events by default, since they won't introduce any performance impact, and they may be pretty useful for the application lifecycle management. The following events also make sense to be enabled by default: - EVT_BASELINE_CHANGED

Re: Moving binary metadata to PDS storage folder

Users shouldn't care about binary_meta and marshaller directories. Those are internal details. Having to go through the documentation on those things to figure out whether you need to run each of the provided scripts or not will lead to terrible user experience. If we add the

Re: Extensions for control.sh

connection configuration/code. For example, it may be useful to set some attributes to binary rest client. On Thu, May 14, 2020 at 2:09 AM Denis Magda wrote: Perfect idea to use this the tool for configuration and addition of extensions! - Denis On Wed, May 13, 2020 at 11:43 AM Denis Mekhanikov

Re: Moving binary metadata to PDS storage folder

the node start. The right behavior from my point should be: 1. Change the default path of binary/marshaller directory to the new one. 2. Provide migration scripts for users. WDYT? On Wed, 13 May 2020 at 21:10, Denis Mekhanikov wrote: Sounds great! It happens pretty frequently that users

Extensions for control.sh

Hi everyone! Control.sh is a command-line management tool that you can use to manage your grid and check its vital parameters like topology version or availability of baseline nodes. It has is good set of commands which are suitable to work with vanilla Ignite. There is also a way to extend

Re: Moving binary metadata to PDS storage folder

Sounds great! It happens pretty frequently that users migrate to a new version of Ignite and preserve persistence files only without caring too much about the work folder. But it turns out, that the work folder actually has some important stuff. This improvement should help with this issue.

Re: Server Node comes down with : (err) Failed to notify listener: GridDhtTxPrepareFuture Error

Thanks for the report! The issue here is that a remote filter for a continuous query is loaded using peer class loading, and other classes that this remote filter depends on can be lazily loaded during its work. Loading every dependency class involves going to the node where the originating class

[jira] [Created] (IGNITE-12794) Scan query fails with an assertion error: Unexpected row key

Denis Mekhanikov created IGNITE-12794: - Summary: Scan query fails with an assertion error: Unexpected row key Key: IGNITE-12794 URL: https://issues.apache.org/jira/browse/IGNITE-12794 Project

[jira] [Created] (IGNITE-12753) Cache SSL contexts in SslContextFactory

Denis Mekhanikov created IGNITE-12753: - Summary: Cache SSL contexts in SslContextFactory Key: IGNITE-12753 URL: https://issues.apache.org/jira/browse/IGNITE-12753 Project: Ignite Issue

Re: Reference of local service.

to manage local services monitoring: > > > - local services monitoring will be disabled by default - to avoid any > > > backward compatibility issues; > > > - local services monitoring can be enabled runtime with a known > > limitation > > >

Re: Reference of local service.

Vladimir, Slava, In general, I like the idea of abstracting the service deployment from its usage, but there are some backward-compatibility considerations that won't let us do so. Or we can declare usage of services without interfaces incorrect I don't think we can introduce a requirement for

[jira] [Created] (IGNITE-12702) Print warning when a cache value contains @AffinityKeyMapped annotation

Denis Mekhanikov created IGNITE-12702: - Summary: Print warning when a cache value contains @AffinityKeyMapped annotation Key: IGNITE-12702 URL: https://issues.apache.org/jira/browse/IGNITE-12702

[jira] [Created] (IGNITE-12480) Add BinaryFieldExtractionSelfTest to the Binary Objects test suite

Denis Mekhanikov created IGNITE-12480: - Summary: Add BinaryFieldExtractionSelfTest to the Binary Objects test suite Key: IGNITE-12480 URL: https://issues.apache.org/jira/browse/IGNITE-12480

[jira] [Created] (IGNITE-12479) All binary types are registered twice

Denis Mekhanikov created IGNITE-12479: - Summary: All binary types are registered twice Key: IGNITE-12479 URL: https://issues.apache.org/jira/browse/IGNITE-12479 Project: Ignite Issue

Service grid webinar

Hi Igniters! I’ve been working on the Service Grid functionality in Apache Ignite for a while, and at some point I've decided to make a webinar with a high-level overview of this part of the project. If you want to learn more about services, look at some use-cases or just ask a few questions

Re: Gracefully shutting down the data grid

Shiva, What version of Ignite do you use and do you have security configured in the cluster? There was a bug in Ignite before version 2.7, that has similar symptoms:  https://issues.apache.org/jira/browse/IGNITE-7624 It’s fixed under the following ticket: 

[jira] [Created] (IGNITE-12265) JavaDoc doesn't have documentation for the org.apache.ignite.client package

Denis Mekhanikov created IGNITE-12265: - Summary: JavaDoc doesn't have documentation for the org.apache.ignite.client package Key: IGNITE-12265 URL: https://issues.apache.org/jira/browse/IGNITE-12265

[jira] [Created] (IGNITE-12237) Forbid thin client connections dynamically

Denis Mekhanikov created IGNITE-12237: - Summary: Forbid thin client connections dynamically Key: IGNITE-12237 URL: https://issues.apache.org/jira/browse/IGNITE-12237 Project: Ignite

Re: nodes are restarting when i try to drop a table created with persistence enabled

I think, the issue is that Ignite can't recover from IgniteOutOfMemory, even by removing data. Shiva, did IgniteOutOfMemory occur for the first time when you did the DROP TABLE, or before that? Denis ср, 25 сент. 2019 г. в 02:30, Denis Magda : > > Shiva, > > Does this issue still exist? Ignite

Re: Nabble message wrapping

s to the Apache infra in order to do this > > > We can open a ticket for ASF INFRA. Could you please do that and see what > they say? > > - > Denis > > > On Wed, Sep 11, 2019 at 1:36 AM Denis Mekhanikov > wrote: > > > Denis, > > > > I did som

Re: Nabble message wrapping

2019 at 1:18 PM Denis Magda wrote: > > > Denis, > > > > I granted your account the admin access. Please do all the required > > changes and let me know once done. > > > > - > > Denis > > > > > > On Thu, Aug 29, 2019 at 2:00 AM Denis M

Re: The ASF Slack

Guys, please disregard my previous message. What I was missing is the following link: https://s.apache.org/slack-invite Denis On 10 Sep 2019, 12:52 +0300, Denis Mekhanikov , wrote: > Anton, > > You need to have an apache email to register in the ASF Slack. Is it > supposed to be

Re: The ASF Slack

Anton, You need to have an apache email to register in the ASF Slack. Is it supposed to be like this? I don't think it's fair to limit the circle of communication this way. Non-blocking PME discussion is going to happen there, for example, and I won't be able to attend it, since I don't have an

Re: Do I have to use --illegal-access=permit for Java thin client and JDBC with JDK 9/10/11.

"127.0.0.1:10800")); > ClientCache cache = > igniteClient.getOrCreateCache("test.cache"); > cache.put(1, "value1"); > cache.put(2, "value2"); > cache.get(1); > cache.query(new SqlFieldsQuery("SELECT * FROM > IGNITE.NODES&qu

Re: Do I have to use --illegal-access=permit for Java thin client and JDBC with JDK 9/10/11.

Alex, Could you share the project you’re checking? A GitHub repository would be nice. Denis On 3 Sep 2019, 17:10 +0300, Alex Plehanov , wrote: > Dmitrii, > > What version of Ignite you are using? > > I've rechecked Java thin client recently (forgot to share results here), in > my tests: > Client

Re: Nabble message wrapping

Guys, Any update? Who has a Nabble admin account for the developers list? Denis On 27 Aug 2019, 14:55 +0300, Dmitriy Pavlov , wrote: > Hi Denis, > > AFAIK, nabble forums are service, which resides outside of ASF infra. They > have their separate support/feedback form. > > Maybe some PMC members

Nabble message wrapping

Hi! The Nabble forum formats emails in a way that makes quoted messages unreadable. For example, take a look at the latest messages in the following thread:  http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-7-6-Time-Scope-and-Release-manager-td42944.html The beginning of

Re: Asynchronous registration of binary metadata

hurt performance? Otherwise ALL requests will be blocked > > until some unrelated metadata is written which is highly undesirable. > > > > Otherwise looks good if performance will not be affected by implementation. > > > > > > чт, 22 авг. 2019 г. в 15:18, Denis Mekhanikov

[jira] [Created] (IGNITE-12099) Don't write metadata to disk in discovery thread

Denis Mekhanikov created IGNITE-12099: - Summary: Don't write metadata to disk in discovery thread Key: IGNITE-12099 URL: https://issues.apache.org/jira/browse/IGNITE-12099 Project: Ignite

Re: Do I have to use --illegal-access=permit for Java thin client and JDBC with JDK 9/10/11.

nis > > > On Wed, Aug 14, 2019 at 5:56 PM Denis Mekhanikov > wrote: > > > Hi! > > > > There are two JDK internal things that are used by Ignite: Unsafe and > > sun.nio.ch package. > > None of these things are used by thin clients. So, it’s fine to use t

Re: Asynchronous registration of binary metadata

before performing any cache changes. What do you think about such fix? Denis On 22 Aug 2019, 12:44 +0300, Alexei Scherbakov , wrote: > Denis Mekhanikov, > > I think at least one node (coordinator for example) still should write > metadata synchronously to protect from a scenario: >

Re: Asynchronous registration of binary metadata

it in my setup. So please let me know if you see any other drawbacks in the proposed solution. Denis > On 21 Aug 2019, at 15:53, Alexei Scherbakov > wrote: > > Denis Mekhanikov, > > If we are still talking about "proper" solution the metastore (I've meant

Re: Asynchronous registration of binary metadata

gt; > On Tue, Aug 20, 2019 at 11:55 AM Denis Mekhanikov > wrote: > >> Sergey, >> >> Currently metadata is written to disk sequentially on every node. Only one >> node at a time is able to write metadata to its storage. >> Slowness accumulates when yo

Re: Asynchronous registration of binary metadata

chema, what in this case would be with >> grid operability? >> >>> >>>> 2. Yes, for walmode=FSYNC writes to metastore will be slow. But such >> mode >>>> should not be used if you have more than two nodes in grid because it >> has >>&

Re: Asynchronous registration of binary metadata

14 Aug 2019, at 19:37, Alexei Scherbakov > wrote: > > Denis Mekhanikov, > > 1. Yes, only on OS failures. In such case data will be received from alive > nodes later. > 2. Yes, for walmode=FSYNC writes to metastore will be slow. But such mode > should not be used if y

Re: Do I have to use --illegal-access=permit for Java thin client and JDBC with JDK 9/10/11.

Hi! There are two JDK internal things that are used by Ignite: Unsafe and sun.nio.ch package. None of these things are used by thin clients. So, it’s fine to use thin clients without additional flags. Denis > On 13 Aug 2019, at 23:01, Shane Duan wrote: > > Hi Igniter, > > I understand that

Re: Asynchronous registration of binary metadata

rtial data >> unavailability. >> And may be further index corruption. >> 1. Why your meta takes a substantial size? may be context leaking ? >> 2. Could meta be compressed ? >> >> >>> Среда, 14 августа 2019, 11:22 +03:00 от Alexei Scherbakov >>&

Re: Asynchronous registration of binary metadata

I would also like to mention, that marshaller mappings are written to disk even if persistence is disabled. So, this issue affects purely in-memory clusters as well. Denis > On 13 Aug 2019, at 17:06, Denis Mekhanikov wrote: > > Hi! > > When persistence is enabled, binary meta

Asynchronous registration of binary metadata

Hi! When persistence is enabled, binary metadata is written to disk upon registration. Currently it happens in the discovery thread, which makes processing of related messages very slow. There are cases, when a lot of nodes and slow disks can make every binary type be registered for several

[jira] [Created] (IGNITE-11914) Failures to deserialize discovery data should be handled by a failure handler

Denis Mekhanikov created IGNITE-11914: - Summary: Failures to deserialize discovery data should be handled by a failure handler Key: IGNITE-11914 URL: https://issues.apache.org/jira/browse/IGNITE-11914

[jira] [Created] (IGNITE-11907) Registration of continuous query should fail if nodes don't have remote filter class

Denis Mekhanikov created IGNITE-11907: - Summary: Registration of continuous query should fail if nodes don't have remote filter class Key: IGNITE-11907 URL: https://issues.apache.org/jira/browse/IGNITE-11907

[jira] [Created] (IGNITE-11854) Serialization of arrays of primitives in python thin client is not optimal

Denis Mekhanikov created IGNITE-11854: - Summary: Serialization of arrays of primitives in python thin client is not optimal Key: IGNITE-11854 URL: https://issues.apache.org/jira/browse/IGNITE-11854

[jira] [Created] (IGNITE-11792) Web console agent throws NullPointerException if node endpoint is incorrect

Denis Mekhanikov created IGNITE-11792: - Summary: Web console agent throws NullPointerException if node endpoint is incorrect Key: IGNITE-11792 URL: https://issues.apache.org/jira/browse/IGNITE-11792

Re: New Committer: Vyacheslav Daradur

Well done Slava! It was great working with you on the service grid redesign. Looking forward to seeing new commits from you! Denis чт, 11 апр. 2019 г. в 18:27, Denis Magda : > Well deserved, Vyacheslav! Thanks for hardening Service Grid pushing it to > a completely next level! > > - > Denis >

[jira] [Created] (IGNITE-11628) Document the possibility to use JAR files in UriDeploymentSpi

Denis Mekhanikov created IGNITE-11628: - Summary: Document the possibility to use JAR files in UriDeploymentSpi Key: IGNITE-11628 URL: https://issues.apache.org/jira/browse/IGNITE-11628 Project

Re: UriDeploymentSpi and GAR files

an Ignite version upgrade. What do you think? Denis чт, 21 февр. 2019 г. в 17:48, Denis Mekhanikov : > I created the following tickets: > > https://issues.apache.org/jira/browse/IGNITE-11379 – drop support of GARs > https://issues.apache.org/jira/browse/IGNITE-11380 – support

[jira] [Created] (IGNITE-11575) Make UriDeploymentSpi ignore archives with untrusted signature

Denis Mekhanikov created IGNITE-11575: - Summary: Make UriDeploymentSpi ignore archives with untrusted signature Key: IGNITE-11575 URL: https://issues.apache.org/jira/browse/IGNITE-11575 Project

[jira] [Created] (IGNITE-11543) TransactionOptimisticException on topology change when readThrough is enabled

Denis Mekhanikov created IGNITE-11543: - Summary: TransactionOptimisticException on topology change when readThrough is enabled Key: IGNITE-11543 URL: https://issues.apache.org/jira/browse/IGNITE-11543

[jira] [Created] (IGNITE-11531) Merge concurrent registrations of the same binary type

Denis Mekhanikov created IGNITE-11531: - Summary: Merge concurrent registrations of the same binary type Key: IGNITE-11531 URL: https://issues.apache.org/jira/browse/IGNITE-11531 Project: Ignite

[jira] [Created] (IGNITE-11520) SQL schema is overwritten by static query entity configuration

Denis Mekhanikov created IGNITE-11520: - Summary: SQL schema is overwritten by static query entity configuration Key: IGNITE-11520 URL: https://issues.apache.org/jira/browse/IGNITE-11520 Project

[jira] [Created] (IGNITE-11490) System data region metrics are disabled regardless of metricsEnabled flag

Denis Mekhanikov created IGNITE-11490: - Summary: System data region metrics are disabled regardless of metricsEnabled flag Key: IGNITE-11490 URL: https://issues.apache.org/jira/browse/IGNITE-11490

[jira] [Created] (IGNITE-11381) Document XML task config format for UriDeploymentSpi

Denis Mekhanikov created IGNITE-11381: - Summary: Document XML task config format for UriDeploymentSpi Key: IGNITE-11381 URL: https://issues.apache.org/jira/browse/IGNITE-11381 Project: Ignite

Re: UriDeploymentSpi and GAR files

1. Support jar files instead of gar. > 2. Write down documentation about XML config format. > 3. Provide some examples. > > Can you crate a tickets for it? > > > ср, 20 февр. 2019 г. в 11:49, Denis Mekhanikov : > > > Denis, > > > > This XML may cont

[jira] [Created] (IGNITE-11379) Drop support of GAR files

Denis Mekhanikov created IGNITE-11379: - Summary: Drop support of GAR files Key: IGNITE-11379 URL: https://issues.apache.org/jira/browse/IGNITE-11379 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-11380) Make UriDeploymentSpi support JAR files

Denis Mekhanikov created IGNITE-11380: - Summary: Make UriDeploymentSpi support JAR files Key: IGNITE-11380 URL: https://issues.apache.org/jira/browse/IGNITE-11380 Project: Ignite Issue

[jira] [Created] (IGNITE-11371) Cache get operation with readThrough returns null if remove is performed concurrently

Denis Mekhanikov created IGNITE-11371: - Summary: Cache get operation with readThrough returns null if remove is performed concurrently Key: IGNITE-11371 URL: https://issues.apache.org/jira/browse/IGNITE-11371

Re: UriDeploymentSpi and GAR files

lain JARs if anybody needs this at all. > > Might still keep meta info support for compatibility. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 19 февр. 2019 г. в 19:38, Denis Mekhanikov : > > > > > Hi! > > > > >

UriDeploymentSpi and GAR files

Hi! There is a feature in Ignite called DeploymentSpi [1], that allows adding and changing implementation of compute tasks without nodes' downtime. The only usable implementation right now is UriDeploymentSpi [2], which lets you provide classes of compute tasks packaged as an archive of a special

IgniteServices.serviceProxy and local services

Folks, Currently IgniteServices.serviceProxy(...) [1] method is designed to return a locally deployed service if it's available. The remote services will be considered only if current one doesn't have the needed service locally. This behaviour breaks the load-balancing feature of services. Let's

Re: Services hot redeployment

; > > Sounds like a good plan. Does it mean that a user will have to > > register a classloader for service's class explicitly in case of using > > the feature? > > > > On Mon, Feb 4, 2019 at 4:38 PM Denis Mekhanikov > wrote: > > > > > > I

Re: Services hot redeployment

methods like redeploy(ServiceConfiguration). 3. Service versioning and packaging. I'd like to focus on the first point. Service grid will become much more usable and mature once we implement it. Denis вт, 5 февр. 2019 г. в 14:06, Denis Mekhanikov : > Vyacheslav, > > I think, w

Services hot redeployment

Igniters, I'd like to start a dedicated thread for discussion of the design of services hot redeployment. The previous service design discussion can be found in the following thread: [1] Currently adding a new service or implementation change of an existing one requires restarting the hosting

Re: High priority TCP discovery messages

Yakov, > You can put hard limit and process enqued MetricsUpdate message > if last one of the kind was processed more than metricsUpdFreq millisecs ago. Makes sense. I'll try implementing it. > I would suggest we allow queue overflow for 1 min, but if situation does not go to normal then node >

[jira] [Created] (IGNITE-11062) Calculating Compute Usage section contains confusing numbers

Denis Mekhanikov created IGNITE-11062: - Summary: Calculating Compute Usage section contains confusing numbers Key: IGNITE-11062 URL: https://issues.apache.org/jira/browse/IGNITE-11062 Project

[jira] [Created] (IGNITE-10959) Memory leaks in continuous query handlers

Denis Mekhanikov created IGNITE-10959: - Summary: Memory leaks in continuous query handlers Key: IGNITE-10959 URL: https://issues.apache.org/jira/browse/IGNITE-10959 Project: Ignite Issue

Re: High priority TCP discovery messages

I like the idea to make all messages be processed with equal priority. It will make nodes with overgrown discovery message queues die more often, though. But maybe, this is how it's supposed to work. Denis пт, 11 янв. 2019 г. в 16:26, Denis Mekhanikov : > Yakov, > > So

Re: High priority TCP discovery messages

Yakov, Sounds good. But there is a flaw in the procedure, that you described. If we have a TcpDiscoveryMetricsUpdateMessage in a queue, and a newer one arrives, then we will consider the existing one obsolete and won't process it. The newest metrics update message will be moved to the queue's

Re: Time to remove automated messages from the devlist?

ifications@ for this. > > > >> > > > > >> > So only one option to proceed here is to run a formal vote on list > > > >> creation > > > >> > and redirection of github/gitbox messages to a new list. > > > >> > > > >

High priority TCP discovery messages

A bit of background: When TcpDiscoverySpi is used, TcpDiscoveryMetricsUpdateMessage is sent by a coordinator once in metricsUpdateFrequency, which is 2 seconds by default. It serves as a ping message, which ensures, that the ring is connected, and all nodes are alive. These messages have a high

Re: Service grid redesign

'Single' means 'single node', maybe we should use one of the following: > > - 'ServicesSingleNodeDeploymentsResults' > > - 'ServicesNodeDeploymentsResults' > > - 'ServicesInstanceDeploymentsResults' > > > > On Wed, Dec 19, 2018 at 4:26 PM Denis Mekhanikov > > wrote: > > > > > &g

Re: Service grid redesign

> Agree. Lets's do it. > > > > > *ServicesDeploymentManager*, *ServicesDeploymentTask *and all other > classes> with Services word in them. > > > I think, they would look better if we use a singular word *Service > *instead. > > > Same for *Deployments*. &

Re: Continuous queries and duplicates

Guys, FYI: Partition counters are already a part of the public API. The following method reveals this information: CacheQueryEntryEvent#getPartitionUpdateCounter()

Re: Service grid redesign

ymentResult* Let's do this as the final step of the code review to avoid repeated renaming. Denis чт, 6 дек. 2018 г. в 15:21, Denis Mekhanikov : > Alexey, > > I don't see any problem in letting services work on a deactivated cluster. > All services need is discovery messages and c

Re: Use of marshaller at node startup routine (need advice)

Slava, Interface *Service *extends *Serializable.* So, all services are supposed to be serializable by the JdkMarshaller. Usage of *BinaryMarshaller* or *OptimizedMarshaller* makes sense only from performance point of view. But I don't think, that we should try too hard to minimize the

Re: [Result][VOTE] Creation dedicated list for github notifiacations

Great news! Is it possible to move all GitHub messages from the archive of the developers list to the newly-created one? Denis вт, 11 дек. 2018 г. в 10:05, Dmitriy Pavlov : > Hi Igniters, > > Infra changed notifications, so now GitHub emails are being sent to > notifications@ > > Web UI:

Re: Service grid redesign

Alexey, I don't see any problem in letting services work on a deactivated cluster. All services need is discovery messages and compute tasks. Both of these features are available at all times. But it should be configurable. Services may need caches for their work, so it's better to undeploy such

Re: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'

for similar issue in 'examples' module. > > Seems, there are some issues with Platforms module integration. > > Slava, do you think Platforms tests can be fixed as well or one more > ticket > > should be created? > > > > [1] https://issues.apache.org/jira/browse/IG

Re: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'

Slava, These are exactly my thoughts, so I fully support you here. I already wrote about it: http://apache-ignite-developers.2346864.n4.nabble.com/IP-finder-in-tests-td33322.html But I kind of abandoned this activity. Feel free to take over it. Denis ср, 5 дек. 2018 г. в 17:22, Vladimir Ozerov

Re: [DISCUSSION] Performance issue with cluster-wide cache metrics distribution

Alex, Did you measure the impact of metrics collection? What is the overhead you are trying to avoid? Just to make it clear, MetricUpdateMessage-s are used as heartbeats. So they are sent anyways, even if no metrics are distributed between nodes. Denis вт, 4 дек. 2018 г. в 12:46, Alex Plehanov

Re: [VOTE] Creation dedicated list for github notifiacations

+1 I'm for making the dev list readable without filters of any kind. On Tue, Nov 27, 2018, 15:14 Maxim Muzafarov +1 > > Let's have a look at how it will be. > > On Tue, 27 Nov 2018 at 14:48 Seliverstov Igor > wrote: > > > +1 > > > > вт, 27 нояб. 2018 г. в 14:45, Юрий : > > > > > +1 > > > > > >

Re: How to deprecate unused Ignite's system property properly? (IGNITE-7441 Drop IGNITE_SERVICES_COMPATIBILITY_MODE system property)

Vyacheslav, You are right. This property is not used anywhere, so you can safely remove it. I don't think, there is any need in deprecation. You can just go ahead and drop it, since it doesn't have any effect. Denis чт, 22 нояб. 2018 г. в 15:47, Vyacheslav Daradur : > Hi, Igniters! > > Here is

Re: proposed realization KILL QUERY command

Actually, option with separate parameters was mentioned in another thread http://apache-ignite-developers.2346864.n4.nabble.com/proposed-design-for-thin-client-SQL-management-and-monitoring-view-running-queries-and-kill-it-tp37713p38056.html Denis чт, 22 нояб. 2018 г. в 08:51, Vladimir Ozerov :

Re: New API for changing configuration of persistent caches

Guys, I like the idea with the configuration builder more. We could limit the set of properties by providing only modifiable ones in the builder interface. Otherwise only runtime will show whether you tried to modify a proper setting. And if we decide to make another property modifiable, then we

  1   2   3   >