Re: IgniteSemaphore and failoverSafe flag

Hi everyone, I agree with Val, he's got a point; recreating the lock doesn't seem possible (at least not the with the transactional cache lock/semaphore we have). Is this re-create behavior really needed? Best regards, Vladisav On Thu, Mar 16, 2017 at 8:34 PM, Valentin Kulichenko <

Re: IgniteSemaphore and failoverSafe flag

Guys, How does recreation of the lock helps? My understanding is that scenario is the following: 1. Client A creates and acquires a lock, and then starts to execute guarded logic. 2. Client B tries to acquire the same lock and parks to wait. 3. Before client A unlocks, all affinity nodes for the

Re: IGNITE-4536 metrics of new offheap storage

As far as the percentage of the free page space, why do we need to provide 3 ranges: 0 -> 16, 16 -> 32, 32 -> 64, etc? Why not just provide average free bytes percentage as one value? Am I misunderstanding something? On Thu, Mar 16, 2017 at 11:04 AM, Denis Magda wrote: >

Re: IGNITE-4536 metrics of new offheap storage

Sergey, Considering that the swap tier will no longer be supported in 2.0 all the methods that start with ‘getSwap…’ are no longer relevant and have to be removed from metrics. For instance, the swap functionality has already been wiped out from .NET:

Re: IGNITE-4536 metrics of new offheap storage

Sergey, looks good. Can you also provide a list of metrics that you have removed? I think it's best to include this into the Jira ticket. D. On Thu, Mar 16, 2017 at 10:22 AM, Sergey Chugunov wrote: > Denis, > > Here is a version of CacheMetrics interface with all

Re: Cluster name

I am not sure I like naming clusters from an agent. It just sounds counter intuitive for me. How about adding an optional IGNITE_CLUSTER_NAME env property together with optional -DCLUSTER_NAME system property and reserved CLUSTER_NAME user attribute? If user fails to provide any of the above,

Re: IGNITE-4536 metrics of new offheap storage

Denis, Here is a version of CacheMetrics interface with all changes how I see them (pretty long list :)). public interface CacheMetrics { public long getCacheHits(); public float getCacheHitPercentage(); public long getCacheMisses(); public float getCacheMissPercentage();

Re: New Blogs: What's new in Ignite.NET 1.9 and Ignite Kubernetes deployment on Azure

A couple of more blogs got published. * Continous queries in Ignite C++ by Igor - https://isapego.github.io/Continuous-Queries-in-Apache-Ignite-CPP-1-9/#disqus_thread * Modern Application Design With

Re: Timestamp and Time types in SQL queries

Fix C++ :) Sergi 2017-03-16 18:36 GMT+03:00 Igor Sapego : > Well, I wrote tests and they are failing. So what is the solution here? > Can it be fixed somewhere in Ignite or is it not possible without edits in > H2? > > Best Regards, > Igor > > On Thu, Mar 16, 2017 at 6:31

[GitHub] ignite pull request #1630: IGNITE-4795

GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/1630 IGNITE-4795 IGNITE-4795 TransactionException marker created. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite master

Re: ignite-4823 - ready for review (SpringCache#putIfAbsent - wrong implementation)

Vyacheslav, I will review and merge in nearest time. -Val On Thu, Mar 16, 2017 at 8:08 AM, Vyacheslav Daradur wrote: > Hello everyone. > > Please review changes: *https://issues.apache.org/jira/browse/IGNITE-4823 > * > >

Re: Timestamp and Time types in SQL queries

Well, I wrote tests and they are failing. So what is the solution here? Can it be fixed somewhere in Ignite or is it not possible without edits in H2? Best Regards, Igor On Thu, Mar 16, 2017 at 6:31 PM, Sergi Vladykin wrote: > This happens because H2 does not work

Re: Timestamp and Time types in SQL queries

This happens because H2 does not work with these classes directly and we do some conversions to SQL types, then from H2 JDBC API we get what H2 gives us. The resulting types can be different. I guess you have to just write tests for all these types and cover all these cases in C++ code. Sergi

Timestamp and Time types in SQL queries

Hi guys, I'm working on java.sql.Time type support for ODBC [1], and I'm facing following behaviour: Lets suppose I perform an SQL query from C++ on field of java.sql.Time type: SELECT dateField from SomeType Nothing special here. The problem is in C++ I get value of type Date instead of Time.

[GitHub] ignite pull request #1629: IGNITE-3429: org.hibernate.cache.spi.CacheKey not...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1629 IGNITE-3429: org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller You can merge this pull request into a Git repository by running: $ git pull

Re: distributed transaction of non-single coordinator

The problem "How to run millions of entities, and millions of operations on a single Pentium3" is out of scope here. Do the math, plan capacity reasonably. Sergi 2017-03-16 15:54 GMT+03:00 ALEKSEY KUZNETSOV : > hmm, If we have millions of entities, and millions of

[jira] [Created] (IGNITE-4832) Service is deployed on client when service configuration is provided on startup

Valentin Kulichenko created IGNITE-4832: --- Summary: Service is deployed on client when service configuration is provided on startup Key: IGNITE-4832 URL: https://issues.apache.org/jira/browse/IGNITE-4832

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Hi igniters, GridDhtAtomicCache class isFastMap method always returns false now. Do you think you need to remove it? > 14 марта 2017 г., в 14:30, Andrey Gura написал(а): > > I've added comments about IgniteConfiguration to JIRA ticket. > > On Tue, Mar 14, 2017 at 2:06

[jira] [Created] (IGNITE-4831) Add an option to disable MBeans

Valentin Kulichenko created IGNITE-4831: --- Summary: Add an option to disable MBeans Key: IGNITE-4831 URL: https://issues.apache.org/jira/browse/IGNITE-4831 Project: Ignite Issue Type:

[GitHub] ignite pull request #1516: IGNITE-3429: org.hibernate.cache.spi.CacheKey not...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1516 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: distributed transaction of non-single coordinator

hmm, If we have millions of entities, and millions of operations, would not this approache lead to memory overflow and perfomance degradation чт, 16 мар. 2017 г. в 15:42, Sergi Vladykin : > 1. Actually you have to check versions on all the values you have read > during

Re: Cluster name

Alexey, Cluster doesn't know about the console, but web agent does, right? I think it should be his responsibility to assign the name. I.e. when starting the agent next to a particular cluster, user has to specify the name. If the console already has the cluster with this name, agent should not

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

It still unclear , how could i notify coordinator that cache creation failed чт, 9 мар. 2017 г. в 17:46, Yakov Zhdanov : Alexey, you should understand how caches startup and partition map exchange work. I would suggest you start couple of nodes in single VM and simply do

Re: Unused argument in DirectMessageWriter

watch him, he is gonna remove all the messages he doesn't like :) чт, 16 мар. 2017 г. в 14:56, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Hi, > > These classes are part of plugin framework. Even though 'name' argument is > not used by Ignite implementations, it can be used by

Re: distributed transaction of non-single coordinator

1. Actually you have to check versions on all the values you have read during the tx. For example if we have [k1 => v1, k2 => v2] and do: put(k1, get(k2) + 5) We have to remember the version for k2. This logic can be relatively easily encapsulated in a framework atop of Ignite. You need to

Re: Usability Issue: Web Console doesn't give an option to add a primary key to object fields list

Dima & Denis, See: https://issues.apache.org/jira/browse/IGNITE-3487 and http://apache-ignite-developers.2346864.n4.nabble.com/DML-data-streaming-td14385.html On Thu, Mar 16, 2017 at 8:18 AM, Dmitriy Setrakyan wrote: > On Wed, Mar 15, 2017 at 5:42 PM, Alexey Kuznetsov

Re: Unused argument in DirectMessageWriter

Hi, These classes are part of plugin framework. Even though 'name' argument is not used by Ignite implementations, it can be used by others. Therefore it should not be removed. -Val On Thu, Mar 16, 2017 at 10:36 AM, Александр Меньшиков wrote: > Hello, everyone! > > I

Re: Cluster name

Dmitriy, Sergi and Val. Web Console will be connected to several clusters at once. And clusters do not know about Web Console, because Web Console collect info from cluster via our REST-HTTP module. So, I can distinguish clusters only by collection of node IDs and give them names like: "Cluster1,

Re: Cluster name

Alexey, How does the workflow look like? How do you add a cluster to this dropdown on the console? I think that assigning a name should be part of this process and should happen on the console itself. Adding yet another "name" to configuration will only confuse users even more. -Val On Thu,

Re: distributed transaction of non-single coordinator

Yeah, now i got it. There are some doubts on this approach 1) During optimistic commit phase, when you assure no one altered the original values, you must check versions of other dependent keys. How could we obtain those keys(in an automative manner, of course) ? 2) How could we lock a key before

Unused argument in DirectMessageWriter

Hello, everyone! I found some strange thing. In 'MessageWriter' there are a lot of methods like 'write*(String name, * val)'. But in implementation 'DirectMessageWriter' argument 'name' isn't used in these methods. And there aren't other 'MessageWriter' implementations. Maybe we can remove

Re: Cluster name

I don't like to add anything like this into Ignite config. It is a problem of Web console how to name or rename different clusters for a user, but not Ignite cluster itself. Sergi 2017-03-16 4:21 GMT+03:00 Dmitriy Setrakyan : > I am OK with having a cluster name, but I

[GitHub] ignite pull request #1625: IGNITE-4712 (tests fix)

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1625 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

ignite-3682 - GridFunc: move all inner anonymous classes to separate top-level classes.

Hello everyone. I have some questions about the issue https://issues.apache.org/jira/browse/IGNITE-3682 1) Can I do some minor refactoring of GridFunc class within this task? (to remove unused methods and code duplicates) Or just to extract anonymous classes? 2) Should @Depricated be added to

ignite-4823 - ready for review (SpringCache#putIfAbsent - wrong implementation)

Hello everyone. Please review changes: *https://issues.apache.org/jira/browse/IGNITE-4823 * I found this when I worked on an another issue. If I'm not mistaken it's wrong implementation. -- Best Regards, Vyacheslav