Re: Right MXBean for new metrics

really confused. What do you need to know the "minimal partition > redundancy" for? What will it give you? > > D. > > On Thu, Nov 23, 2017 at 2:25 PM, Alex Plehanov <plehanov.a...@gmail.com> > wrote: > > > Example was in my previous letters: if we have in our

Re: Right MXBean for new metrics

> Will this work for you? > > D. > > On Thu, Nov 23, 2017 at 10:38 PM, Alex Plehanov <plehanov.a...@gmail.com> > wrote: > > > We have target redundancy level - 4. If, for some reason, minimal > > redundancy level reached the value of 1, then each next node lef

Re: Enable/disable cache statistics in runtime

rak...@apache.org>: > On Wed, Nov 29, 2017 at 12:22 PM, Alex Plehanov <plehanov.a...@gmail.com> > wrote: > > > Hello, Igniters! > > > > We need the ability to enable or disable statistics for caches in > runtime. > > For now, there is a cache configuration

Re: Right MXBean for new metrics

t;: > I think you are talking about the case when cluster temporarily gets into > unbalanced state and needs to rebalance. However, I am still not sure what > this metric would show. Can you provide an example? > > D. > > On Wed, Nov 22, 2017 at 2:10 PM, Alex Plehanov <pl

Re: Right MXBean for new metrics

oups. It should show average metrics across all the caches in the group > and some additional metrics as well. Agree? > > Also, I am not sure I understand what is "partition redundancy level" and > what that metric would show. Can you explain. > > D. > > On Tue, N

Re: Right MXBean for new metrics

Dmitriy Setrakyan <dsetrak...@apache.org>: > On Wed, Nov 22, 2017 at 12:39 PM, Alex Plehanov <plehanov.a...@gmail.com> > wrote: > > > Hello Dmitriy, > > > > I agree. > > > > By "minimal partition redundancy level for cache group" I mea

Enable/disable cache statistics in runtime

Hello, Igniters! We need the ability to enable or disable statistics for caches in runtime. For now, there is a cache configuration property which seems modifiable in runtime and this, at first sight, works for local node. But there are no methods to enable or disable statistics for cache cluster

Right MXBean for new metrics

Hello, Igniters! I would like to discuss the implementation of ticket IGNITE-6871. In our Ignite instance there are more than 1000 caches and about 10 cache groups. To minimize the probability of data loss we need to alert when a critical level of redundancy in cluster is reached. So, we

Request for contributors permissions

Hello Ignite Community! My name is Aleksey. I want to contribute to Apache Ignite and want to start with implementation of some JMX metrics. Please add me as contributor. My account in JIRA is "alex_pl". Thanks!

Re: Annoying extra steps for enabling metrics

Valentine, yes, that's exactly what I'm trying to say. I don't see direct dependencies between these properties (when a property must be set in all cases another property is set). 2017-12-29 22:10 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Guys, > > I'm not sure what issue

Re: Annoying extra steps for enabling metrics

Due to holidays I can start work on this ticket only after 8 jan 2018 2017-12-30 2:12 GMT+03:00 Denis Magda : > Good, closed the original ticket. > > Alex P, do you have time to work on IGNITE-7346 instead to address the > issue with the cache events per cache in 2.4 release?

Re: Ignite diagnostic (SQL system views)

a, > or mark with special prefix. E.g. "IGNITE.TRANSACTIONS" - all transactions > in the cluster, "IGNITE.LOCAL_TRANSACTIONS" - transactions on the local > node. In this case we will be able to merge "local" stuff shortly, and > implement more complex but at th

Re: Ignite diagnostic (SQL system views)

;voze...@gridgain.com> > wrote: > > > Let's start with a single and the most simple view, e.g. > > LOCAL_TRANSACTIONS. We will review and merge it along with necessary > > infrastructure. Then will handle the rest view in separate tickets and > > separate focused disc

Re: Annoying extra steps for enabling metrics

hink about it? 2017-12-30 10:12 GMT+03:00 Alex Plehanov <plehanov.a...@gmail.com>: > Due to holidays I can start work on this ticket only after 8 jan 2018 > > 2017-12-30 2:12 GMT+03:00 Denis Magda <dma...@apache.org>: > >> Good, closed the original ticket. >> &g

Re: Annoying extra steps for enabling metrics

en > return > > true from getEventsEnabled in case it's null. Will this work? > > > > -Val > > > > On Wed, Jan 31, 2018 at 7:31 AM, Alex Plehanov <plehanov.a...@gmail.com> > > wrote: > > > > > Denis, there is a question about IGN

Re: Ignite diagnostic (SQL system views)

? 2018-01-25 16:27 GMT+03:00 Alex Plehanov <plehanov.a...@gmail.com>: > Anton, Vladimir, I've made some fixes. There is only one view left and > it's renamed to 'IGNITE.LOCAL_TRANSACTIONS'. > > High level design of solution: > When IgniteH2Indexing is starting, it c

Re: automatic node failure

Dmitriy, Failure handler not supposed to be triggered by user defined exception, but in some cases user defined exception can cause critical system threads termination and this event will trigger a failure handler (which can shutdown the node). There is still no reproducer or full stack trace on

Re: Metrics for MVCC caches

Hi, Ivan Looks like a bug. Metrics counting described at JSR107 (JCache) specification. It says, that "cache removals" metric should be incremented if remove() method returns true. Since there are no matching keys in the first remove() call should be found, remove() should return false and "cache

Re: ignite PureJavaCrc32 vs java.util.zip.CRC32 bench.

Hello, Igniters! In java8 java.lang.zip.CRC32 methods become intrinsic, moreover new "update" method, which use ByteBuffer was introduced. Since we moved to java8, perhaps we really can get performance boost by using standard java.lang.zip.CRC32 instead of PureJavaCrc32. About compatibility:

Re: QueryDetailMetrics for cache-less SQL queries

Hi Evgeny, Do you propose to move into IgniteMetrics absolutely all Ignite metrics or just dataRegionMetrics, dataStorageMetrics and queryDetailMetrics? I think you can't move all metrics into one place. Pluggable components and different SPI implementations may have their own metric sets, and

Re: ignite PureJavaCrc32 vs java.util.zip.CRC32 bench.

> store > > > > > > write > > > > > > > >> are mostly about IO speed. > > > > > > > >> > > > > > > > >> In the same time, it can make the huge impact on machines > with > >

Re: ignite PureJavaCrc32 vs java.util.zip.CRC32 bench.

> > > Also I think AI 3.0 will have set of incompatible changes that give us > a > > > chance to add an upgrade procedure where compression method update > among > > > other stuff will take into account. > > > > > > On Tue, Aug 21, 2018 at 11:58

Re: Wrong off-heap size is reported for a node

To be more precise we need to multiply it by page size with system overhead (systemPageSize). If we want to print only used offheap memory, this will solve the problem. If we want to print, for example, currently allocated (commited) offheap memory (if persistence is disabled for data region then

Re: Plugins in tests

Hello Maxim, I miss this conversation and ticket when implementing PageMemory tracker plugin. By default, it's disabled (every method do nothing), but plugin instance created anyway. If we want to get clear Ignite instances in the testing framework in the core module, PageMemory tracker plugin

Ignite diagnostic (SQL system views)

Hello, Igniters! For Ignite diagnostic usually it’s helpful to get some Ignite internals information. But currently, in my opinion, there are no convenient tools for this purpose: ·Some issues can be solved by analyzing log files. Log files are useful for dumps, but sometimes they are

Re: SQL management and monitoring improvements

Yuri, I think it will be useful if we extend in future management via SQL tool to cover not only queries but also other parts of Ignite (for example: for canceling tasks, for killing transactions, activation/deactivation, baseline topology change, etc.). Maybe, in this case, we should use a

Re: Page IO statistics for Ignite

Hi, I've made some investigation a couple of months ago about a statistics collected by some RDBMS vendors (Oracle, Postgres, MySQL). These databases collect detailed IO statistics in dimensions such as queries, database objects (tables and indexes), files, sessions, users, event types etc. Some

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

ster, it sends explicit > > request over communication SPI > > 3) For performance reasons we may consider caching - return previously > > collected metrics without re-requesting them again if they are not too > old > > (configurable) > > > > On Tue, Dec 4, 2018

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

Hi Igniters, In the current implementation, cache metrics are collected on each node and sent across the whole cluster with discovery message (TcpDiscoveryMetricsUpdateMessage) with configured frequency (MetricsUpdateFrequency, 2 seconds by default) even if no one requested them. If there are a

Re: Wrong off-heap size is reported for a node

Hi Dmitriy, Yes, I will finish review tomorrow. ср, 12 сент. 2018 г. в 20:37, Dmitriy Pavlov : > Hi Igniters, > > It seems the issue is a blocker of 2.7. > > We need a volunteer here to run review. > > Alexey P. will you step in? > > Sincerely, > Dmitriy Pavlov > > ср, 29 авг. 2018 г. в 16:16,

Re: MTCGA: SqlSystemViewsSelfTest is flaky

Ok, I will take a look at this test tomorrow. вт, 18 сент. 2018 г. в 16:40, Alexey Goncharuk : > Igniters, > > I noticed a pretty high raise in the SqlSystemViewsSelfTest failure rate > recently [1]. There is a chance that the failure was introduced by another > SQL system view ticket [2]. > >

Re: Thin client: transactions support

llel. > But with TX support we have to somehow switch to single-threaded mode to > avoid unexpected effects. > > Any ideas? > > > On Mon, Apr 1, 2019 at 6:38 PM Alex Plehanov > wrote: > > > Dmitriy, thank you! > > > > Guys, I've created the IEP [1]

Re: Thin client: transactions support

> > > It is thread-safe and can handle multiple async operations in parallel. > > But with TX support we have to somehow switch to single-threaded mode to > > avoid unexpected effects. > > > > Any ideas? > > > > > > On Mon, Apr 1, 2019 at 6:38 PM Alex Pleh

Re: Thin client: transactions support

mands. Wouldn't it be enough to have only two? > > > > START - accepts optional parameters, returns transaction info > > END - provides commit flag, returns void > > > > Vladimir. > > > > On Wed, Mar 27, 2019 at 8:26 AM Alex Plehanov > > wrote: >

Re: Thin client: transactions support

ds on the server side first. Because > without it you will need a dedicated server thread for every client's > transaction which is slow and may even crash the server. > > Vladimir. > > On Wed, Mar 27, 2019 at 11:44 AM Alex Plehanov > wrote: > > > Vladimir, what if we want

Re: Thin client: transactions support

Kozlov : > > > Hi > > > > Looks like I missed something but why we need OP_TX_CLOSE operation? > > > > Also I suggest to reserve a code for SAVEPOINT operation which very > useful > > to understand where transaction has been rolled back > > > > O

Re: Thin client: transactions support

Hello Igniters! I want to pick up the ticket IGNITE-7369 and add transactions support to our thin client implementation. I've looked at our current implementation and have some proposals to support transactions: Add new operations to thin client protocol: OP_TX_GET, 4000, Get current

Re: Thin client: transactions support

complex What do you think? вт, 2 апр. 2019 г. в 16:29, Alex Plehanov : > Ilya, > > > We should be able to multiplex several transactions using a single > Client connection. > In this case, we should significantly change cache operations syntax (for > each implemented

Re: Thin client: transactions support

and believe > me, we do not want to replicated this bad practice to other clients :-) > > Vladimir. > > On Thu, Apr 4, 2019 at 10:08 AM Alex Plehanov > wrote: > > > Guys, so, do we need multiple concurrent transactions per connection? > > > > There are

Re: Thin client: transactions support

anov.alex > > Recently Infra integrated Apache LDAP with confluence, so it is possible to > login using Apache credentials. Probably we can ask infra if extra > permissions to edit pages should be added for committers. > > Sincerely, > Dmitriy Pavlov > > ср, 27 мар. 2019 г. в 1

Re: Thin client: transactions support

close: rollback >- commit, close: do nothing >- rollback, close: do what? (I suppose nothing) > > Also you assume that after commit/rollback we may need to free some > resources on server node(s)or just do on client started TX? > > > > On Tue, Mar 26, 2019 at 10:41 PM Ale

Re: Disk page compression for Ignite persistent store

Hello Igniters! I've implemented compression of WAL page snapshot records. Ticket [1], PR [2]. I've used page compression module implemented by Sergi Vladykin for page store. To configure WAL page records compression there are 2 properties added to DataStorageConfiguration: walPageCompression

Re: {DISCUSSION] Cluster read-only mode.

Ivan, >From a user's point of view: Inactive cluster - deny writes, deny reads. Read-only cluster - deny writes, allow reads. ср, 5 июн. 2019 г. в 10:44, Павлухин Иван : > Sergey, > > > On inactive cluster caches aren't started. So you can't get data from > cache. > > As a user I do not

Re: Thin client: transactions support

ich is impossible > to deal with. Or am I missing something here? > > One workaround I can imagine is failing a transactions execution from > concurrent threads for a first time. > > [1] https://issues.apache.org/jira/browse/IGNITE-11685 > > вт, 21 мая 2019 г. в 19:05, Alex Pleha

Re: Thin client: transactions support

eady have a good > approach for that. If not then I suppose it worth a discussion. > > пн, 27 мая 2019 г. в 12:51, Alex Plehanov : > > > > Hi Ivan. > > > > Thin client transactions support is not only for java thin client. There > > are other clients, some of them already work in as

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

Remove "force server mode" for client nodes (already was discussed on dev list earlier [1]). [1] : http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-force-server-mode-for-clients-td33614.html пн, 17 июн. 2019 г. в 19:22, Pavel Tupitsyn : > Big changes for .NET: > * Remove legacy

Re: How to know memory used by a cache or a set

I create a cachegroup to handle it, then I > > clean everything. > > > > Le jeu. 13 juin 2019 à 13:28, Alex Plehanov a > > écrit : > > > >> Hello, > >> > >> It's a known issue [1]. Now you can get cache group size via JMX only if > >&

Re: [IEP-35] GridJobProcessorMetrics migration

ions? > > > > > > > But, what if a user doesn't use any > > > external monitoring system and wants to know the health of Ignite > instance? > > > > It depends on how we define "health". > > And it's not trivial question :) > > > >

Re: Connection pool for Java thin client?

Hello Shane, It's safe to share one java thin client between threads. The client in current implementation uses an exclusive lock on the connection while sending request and processing response. But in a high loaded application, using one client will give smaller throughput than using a

Re: [IEP-35] GridJobProcessorMetrics migration

Hi Nikolay, I think "idle time" is a useful metric, but it can be calculated outside of Ignite using external monitoring system. About execution and waiting time, it's not the right way to calculate it using a jobs list. Will jobs list contain only active jobs? In this case, you can't calculate

Re: Thin client: transactions support

hope that we will > do it. > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support > > вт, 30 апр. 2019 г. в 13:24, Alex Plehanov : > > > > Hello, Igniters! > > > > I've update IEP [1] and implement

Re: Thin client: transactions support

add "In transaction" boolean flag to cache > operation request header > to avoid bloating message size in non-affected scenarios. > > Best Regards, > Igor > > > On Mon, May 13, 2019 at 1:58 PM Alex Plehanov > wrote: > > > Hi, Ivan. > > > > T

Re: Thin client: transactions support

t values for tx > concurrency and isolation in client configuration? > > пн, 20 мая 2019 г. в 19:34, Alex Plehanov : > > > > Igor, > > > > Perhaps we don't really need to use server's default values for tx > > parameters. It's a minor fix and can be easily imp

Re: Thin client: transactions support

Guys, I've updated the IEP [1]. Please have a look. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support вт, 21 мая 2019 г., 14:19 Alex Plehanov : > Ivan, > > Yes, I have plans to do that (at least for java thin client). Something > li

Re: Thin client: transactions support

gt; > > I believe that if we want to add ability to client to adopt some > server's > > > defaults > > > we should implement it as separate feature, and it should not be a > > default > > > behaviour for client, user should explicitly state that they want this > > &g

Re: Thin client: transactions support

ory pressure on a cluster node. We already work >> this >> way for MVCC transactions which are spawned from JDBC driver, and believe >> me, we do not want to replicated this bad practice to other clients :-) >> >> Vladimir. >> >> On Thu, Apr 4, 2019 at 1

Re: Thin client: transactions support

ood to me. See reply in > Jira. > But we certainly need more eyes on this. > > On Thu, Aug 15, 2019 at 10:36 AM Alex Plehanov > wrote: > > > Hi Ivan, > > > > Java thin client doesn't support affinity awareness yet (ticket [1] is in > > progress now), but ch

Re: Thin client: transactions support

ot, does Java thin client support affinity awareness? Will it work > properly if it does not? > > ср, 14 авг. 2019 г. в 13:59, Alex Plehanov : > > > > Hi Igniters, > > > > Finally, all dependent tickets are resolved and I've completed the > > impleme

Re: Thin client: transactions support

described in IEP [2]. Can anyone review the patch? [1]: https://issues.apache.org/jira/browse/IGNITE-9410 [2]: https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support пн, 27 мая 2019 г. в 13:27, Alex Plehanov : > Ivan, > > Yes, .NET c

Re: Thin client: transactions support

gt; > > Do we still need to separate client connector configuration from > > thin > > > > > > connector configuration from ODBC connector configuration? > > > > > > > > > > > > I think this is a bad practice: For example, people ofte

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

uires additional options for JVM. However, some > options are optional and used to suppress warning messages. > > Tested with Open JDK 9.0.4, 10.0.2, 11.0.2, 12.0.2 on Ubuntu and Mac OS. > > > Best regards, Dmitry Sherstobitov > On 26 Aug 2019, 16:22 +0300, Alex Plehanov ,

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

t; > 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 clien

Re: Thin client: transactions support

ion. > E.g. does it apply to JDBC Thin Client? No, it does not, but it is easy to > assume it does. > > On Tue, Aug 27, 2019 at 5:07 PM Alex Plehanov > wrote: > > > Ilya, Igor, > > > > Nested property is what exactly I've done in the last fix. > &

Re: New Сommitter: Maxim Muzafarov

Maxim, congratulations! ср, 28 авг. 2019 г. в 18:13, Nikita Amelchev : > My congratulations, Maxim! > > ср, 28 авг. 2019 г. в 18:11, Dmitriy Pavlov : > > > > Dear community, > > > > The Project Management Committee (PMC) for Apache Ignite has invited > Maxim > > Muzafarov to become a committer

Re: Thin client: transactions support

figuration will be useless for > > JDBC and ODBC (since they use one transaction per connection) and may be > > confusing. > > > > Which way is better, WDYT? > > > > > > > > чт, 15 авг. 2019 г. в 11:46, Pavel Tupitsyn : > > > > > Hi Alex, > >

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

Denis, Thin client uses BinaryHeapOutputStream, which uses Unsafe. I've got some warnings when I run thin client with --illegal-access=debug flag, for example: WARNING: Illegal reflective access by org.apache.ignite.internal.util.GridUnsafe$2

Re: Thin client: transactions support

Pavel, ClientConnectorConfiguration is related to JDBC, ODBC and thin clients, the new property only related to thin clients. If we put the new property directly into ClientConnectorConfiguration, someone might think that it also affects JDBC and ODBC. пт, 23 авг. 2019 г. в 19:59, Pavel Tupitsyn

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

"--illegal-access=deny" is set. пт, 23 авг. 2019 г. в 19:44, Denis Magda : > Hmm, looks like we need to provide some VM options for the thin clients as > well. > > Alex, would you mind checking and sharing a full subset of such options for > the thin clients? I'll update

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

pensate future Java defaults changes from permit > to deny. We can save one more release if Ignite will work on a future > release of Java, where `permit` is not default. > > Sincerely, > Dmitriy Pavlov > > пн, 26 авг. 2019 г. в 15:51, Alex Plehanov : > > > Denis,

Re: The ASF Slack

Denis, You don't need an apache email to register in the ASF Slack. Here is the link [1] to join with any email. [1]: https://s.apache.org/slack-invite вт, 10 сент. 2019 г. в 12:52, Denis Mekhanikov : > Anton, > > You need to have an apache email to register in the ASF Slack. Is it > supposed

Re: [IEP-35] Monitoring & Profiling. Phase 2

One more point to discuss: Wouldn't it be better to have enabled system views by default? To enable views admin must restart the node, sometimes it's an issue. Views cost almost nothing in terms of performance until they are explicitly requested, so is their a reason to disable views by default?

Re: Re[2]: [VOTE] Apache Ignite PMC Chair

+ 1 Dmitry Pavlov ср, 30 окт. 2019 г. в 20:50, Pavel Kovalenko : > +1 for Dmitry Pavlov > > ср, 30 окт. 2019 г. в 18:46, Alexei Scherbakov < > alexey.scherbak...@gmail.com > >: > > > +1 for Dmitry Pavlov > > > > ср, 30 окт. 2019 г. в 18:22, aealexsandrov : > > > > > +1 Alexey Goncharuk > > > > >

Thin client: compute support

Hello, Igniters! I have plans to start implementation of Compute interface for Ignite thin client and want to discuss features that should be implemented. We already have Compute implementation for binary-rest clients (GridClientCompute), which have the following functionality: - Filtering

Re: Thin client: compute support

hin > client. > >4. Support the labeling for task that may help to investigate issues > on > >cluster (the idea from IEP-34 [1]) > > > > 1. > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support > > >

Re: Check Code Style suite fails on master

Slava, thanks for noticing! Fixed. чт, 5 дек. 2019 г. в 18:57, Nikita Amelchev : > Hello, Thank you. My bad. > > I have created issue to fix it. [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-12420 > > чт, 5 дек. 2019 г. в 18:41, Вячеслав Коптилин : > > > > > Hello Nikita, > > > > It

Re: Ignite diagnostic (SQL system views)

tion, > not > > clear how the users are expected to benefit from the capability and how > > everybody will be aware of the feature existence. > > > > We need to close the gap and spread the word. > > > > Denis > > > > On Thursday, October 17, 2019, Ale

Re: Ignite diagnostic (SQL system views)

ing. > > > > > > On Tue, Feb 13, 2018 at 4:10 AM, Denis Magda > wrote: > > > > > > > Alex P, sounds like a good plan for me. > > > > > > > > Vladimir, do you have any suggestions or corrections? > > > > > > > >

Re: Best Effort Affinity for thin clients

Hello guys, I've implemented affinity awareness support for java thin client [1]. There is only client-side affected by the patch. Can anyone review the change? 1: https://issues.apache.org/jira/browse/IGNITE-11898 ср, 13 мар. 2019 г. в 22:54, Pavel Tupitsyn : > Default value for boolean

Re: Thin client: compute support

;thick" client? > > > On Mon, Nov 25, 2019 at 11:59 PM Alex Plehanov > wrote: > > > > And it is fine to use request ID to identify compute tasks (as we do > with > > query cursors). > > I can't see any usage of request id in query cursors. We send query

Re: Thin client: compute support

of nodes. > > var myGrp = cluster.forServers().forAttribute("foo"); // This does not > issue any server requests, just builds an object with filters on client > while (true) myGrp.compute().executeTask("bar"); // Every request includes > filters, and filters are applied on

Re: Thin client: compute support

> > a > > > >task is the risky operation for cluster (for security reasons). > > Could > > > we > > > >add for Ignite configuration new options: > > > > - Explicit turning on for compute task support for thin > protocol &g

Re: Thin client: compute support

guages different from Java? > > - > Denis > > > On Wed, Nov 20, 2019 at 11:58 PM Alex Plehanov > wrote: > > > Hello, Igniters! > > > > I have plans to start implementation of Compute interface for Ignite thin > > client and want to discuss featur

Re: Thin client: compute support

this information to IEP. As a next step we can implement class deployment from thin clients (will work only for java) or some kind of domain specific language. It will be decided later do we really need this. WDYT? пт, 22 нояб. 2019 г. в 10:19, Alex Plehanov : > Denis, the primary motivat

Re: Thin client: compute support

t, no need to modify the core of the protocol. One request - one > response. > > On Mon, Nov 25, 2019 at 6:20 PM Alex Plehanov > wrote: > > > Pavel, we need to inform the client when the task is completed, we need > the > > ability to cancel the task. I see several ways

Re: Thin client: compute support

ng something - how is topology change relevant to > executing compute tasks from client? > > On Mon, Nov 25, 2019 at 10:17 PM Alex Plehanov > wrote: > > > Pavel, in this case, we will mix entities from different layers > (transport > > layer and

Re: Thin client: compute support

are also different because client controls when they should > end. > There is no reason for task execution to be a special case like queries or > transactions. > > > we always need to send 2 requests to server to execute the task > Nope. We don't need to get nodes on client at

Re: Metric showing how many nodes may safely leave the cluster

Ivan, there already exist metric CacheGroupMetricsMXBean#getMinimumNumberOfPartitionCopies, which shows the current redundancy level for the cache group. We can lose up to ( getMinimumNumberOfPartitionCopies-1) nodes without data loss in this cache group. пт, 4 окт. 2019 г. в 16:17, Ivan Rakov :

Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental

-1 Prohibit пн, 10 февр. 2020 г. в 20:54, Denis Magda : > [-1 Prohibit] > > - > Denis > > > On Mon, Feb 10, 2020 at 12:02 AM Alexey Goncharuk > wrote: > > > Dear Apache Ignite community, > > > > We would like to conduct a formal vote on the subject of whether to allow > > or prohibit a joint

Re: Thin client: compute support

and file detailed protocol changes shortly. вт, 21 янв. 2020 г. в 18:46, Alex Plehanov : > Igor, thanks for the reply. > > > Approach with taskId will require a lot of changes in protocol and thus > more "heavy" for implementation > Do you mean approach with server

Re: Add user attributes to thin clients

Hello, User attributes also (besides authentication) can be used to pass some info about an application that uses a client and then display this information in monitoring tools. Other vendors use such approach (Oracle DB, for example, have DBMS_APPLICATION_INFO package, PostgreeSQL have

Re: [MTCGA]: new failures in builds [4944565] needs to be handled

a small test fix (+8 -4). чт, 23 янв. 2020 г. в 16:32, Ivan Pavlukhin : > Sorry, missed it https://issues.apache.org/jira/browse/IGNITE-12562 > > чт, 23 янв. 2020 г. в 16:30, Ivan Pavlukhin : > > > > Do we have a ticket for it? > > > > ср, 22 ян

Re: Incorrect fillFactor/memory usage metric

Hello Colin, AFAIK fill factor doesn't take into account reuse bucket by design, it's not a bug. To calculate memory consumption you can also use metric totalUsedPages which take into account the reuse bucket (but doesn't take into account free-list fill factor) This metric was introduced in

Re: [MTCGA]: new failures in builds [4944565] needs to be handled

It was caused by my fix. I will try to fix it shortly. ср, 22 янв. 2020 г. в 00:56, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that you were > a volunteer to

Re: Thin client: compute support

Looks like we didn't rich consensus here. Igor, as thin client maintainer, can you please share your opinion? Everyone else also welcome, please share your thoughts about options to implement operations for compute. чт, 28 нояб. 2019 г. в 10:02, Alex Plehanov : > > Since all thin

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Guys, There is an issue [1] caused by page list caching [2], which also affects 2.8 release. IgniteOutOfMemoryException can be thrown in some cases (data region is small, a checkpoint is triggered by "too many dirty pages" reason and pages list cache is rather big). The fix is ready and merged to

Re: Thin client: compute support

ed in order to introduce new features in the future. > > > > So, maybe it's a good time for us to change our backward compatibility > > mechanism from protocol versioning to feature masks? > > > > WDYT? > > > > Best Regards, > > Igor > > > >

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Guys, There is also an issue with cluster activation by thin clients. This feature (.NET thin client API change and protocol change) was added by [1] without any discussion on dev-list. Sergey's patch [2] deprecate methods "IgniteCluster.active(boolean)" and "IgniteCluster.active()", but didn't

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hello guys, I propose to cherry-pick to 2.8.1 following bug-fixes too, which are already in master: Scan query over an evicted partition can cause node failure (IGNITE-12734 [1]) Java thin client: There were problems with deserialization of some types on the client-side, these types can't be used

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

t;>>> пт, 17 апр. 2020 г. в 16:55, Ivan Pavlukhin : > > >>>> > > >>>>> Great! > > >>>>> > > >>>>> Best regards, > > >>>>> Ivan Pavlukhin > > >>>>> > > >>>>&

Re: [DISCUSSION] Hot cache backup

Maxim, I've reviewed your PR and it looks good to me. Good job! пт, 10 апр. 2020 г. в 19:43, Alexey Goncharuk : > Maxim, > > Thanks for raising this PR. I will do a review during next week. > > --AG >

  1   2   3   >