[GitHub] ignite pull request #1694: IGNITE-3548 .NET: Rename ILifecycleBean

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1694 IGNITE-3548 .NET: Rename ILifecycleBean You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3548 Alternatively you

Re: distributed transaction of non-single coordinator

So, what do u think on my idea ? ср, 29 мар. 2017 г. в 10:35, ALEKSEY KUZNETSOV : > Hi! No, i dont have ticket for this. > In the ticket i have implemented methods that change transaction status to > STOP, thus letting it to commit transaction in another thread. In another > thread you r going to

[jira] [Created] (IGNITE-4882) Sometime network request will be produce when cache entry is locked

Vladislav Pyatkov created IGNITE-4882: - Summary: Sometime network request will be produce when cache entry is locked Key: IGNITE-4882 URL: https://issues.apache.org/jira/browse/IGNITE-4882 Project

Re: distributed transaction of non-single coordinator

Aleksey, I doubt your approach works as expected. Current transaction recovery protocol heavily relies on the originating node ID in its internal logic. For example, currently a transaction will be rolled back if you want to transfer a transaction ownership to another node and original tx owner fa

Re: putting entity into cache while commiting.Why!?

But i managed to read dirty. That is my example : Ignite ignite0 = ignite(0); IgniteTransactions transactions = ignite0.transactions(); IgniteCache cache = ignite0.getOrCreateCache("testCache"); Object monitor = new Object(); GridTestUtils.runAsync(new Callable() { @Override public Object

Re: putting entity into cache while commiting.Why!?

Can you please paste the full example? 2017-03-30 11:50 GMT+03:00 ALEKSEY KUZNETSOV : > But i managed to read dirty. That is my example : > > Ignite ignite0 = ignite(0); > IgniteTransactions transactions = ignite0.transactions(); > IgniteCache cache = ignite0.getOrCreateCache("testCache"); > Obje

[GitHub] ignite pull request #1655: IGNITE-4302 BinaryMetadata exchange protocol refa...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1655 --- 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 ena

Re: putting entity into cache while commiting.Why!?

public class FooTest extends GridCacheAbstractSelfTest { @Override protected void afterTestsStopped() throws Exception { super.afterTestsStopped(); stopAllGrids(); } @Override protected int gridCount() { return 3; } @Override protected Cach

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Denis, CacheAtomicWriteOrderMode enum already removed. > 30 марта 2017 г., в 7:38, Denis Magda написал(а): > > Maxim, Andrey G., Igniters, > > What if go further and remove CacheAtomicWriteOrderMode enum from the public > API at all? I see no sense to keep it for the only one option left - P

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

+ Denis > 30 марта 2017 г., в 12:14, Kozlov Maxim написал(а): > > Denis, > > CacheAtomicWriteOrderMode enum already removed. > >> 30 марта 2017 г., в 7:38, Denis Magda написал(а): >> >> Maxim, Andrey G., Igniters, >> >> What if go further and remove CacheAtomicWriteOrderMode enum from the

[GitHub] ignite pull request #1695: IGNITE-3506 .NET: Fix ContinuousQuery, QueryBase,...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1695 IGNITE-3506 .NET: Fix ContinuousQuery, QueryBase, and SqlFieldsQuery class constants You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupits

[GitHub] ignite pull request #1696: IGNITE-4847 integrate log4j2 2.8.1

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1696 IGNITE-4847 integrate log4j2 2.8.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-1 Alternatively you can revi

Re: putting entity into cache while commiting.Why!?

Aleksey, It looks like in your test the result of method atomicityMode() is not used because you do getOrCreateCache() without the configuration argument, which will create a cache with a default configuration, which is ATOMIC. 2017-03-30 12:06 GMT+03:00 ALEKSEY KUZNETSOV : > public class FooTes

[jira] [Created] (IGNITE-4883) Web Console: Improve the tables on Admin Panel Screen

Vica Abramova created IGNITE-4883: - Summary: Web Console: Improve the tables on Admin Panel Screen Key: IGNITE-4883 URL: https://issues.apache.org/jira/browse/IGNITE-4883 Project: Ignite Issu

[GitHub] ignite pull request #1697: IGNITE-4849 Review and refactoring the versioned ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1697 IGNITE-4849 Review and refactoring the versioned classes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignit

Re: putting entity into cache while commiting.Why!?

Well, i changed code , added : CacheConfiguration config = cache.getConfiguration(CacheConfiguration.class); System.out.println(config.getAtomicityMode());//TRANSACTIONAL So, atomicity is transactional чт, 30 мар. 2017 г. в 12:43, Alexey Goncharuk : > Aleksey, > > It looks like in your test the

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Do we need to merge anything else to the master branch or you mean the enum was removed with the rest of the changes before and merged by Andrey G? — Denis > On Mar 30, 2017, at 5:16 AM, Kozlov Maxim wrote: > > + Denis > >> 30 марта 2017 г., в 12:14, Kozlov Maxim >

Question: local cache on client nodes

Hello Igniters, Participating in big effort of reworking cache storage structures (IGNITE-3477 [1]) I came across a test that looks strange to me: *CacheStopAndDestroySelfTest::testLocalClose*. It is very simple: it starts two server nodes and one client node (with forceServerMode flag set to tru

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Yakov, can I take this ticket or you have already started to implement it? Ask because you are an assignee in JIRA. 2017-03-07 22:21 GMT+03:00 Denis Magda : > Good, the ticket is ready: > https://issues.apache.org/jira/browse/IGNITE-4799 < > https://issues.apache.org/jira/browse/IGNITE-4799> > >

Re: putting entity into cache while commiting.Why!?

Agree, the cache is transactional, however, the second transaction does not see the dirty value: Ignite ignite0 = ignite(0); IgniteTransactions transactions = ignite0.transactions(); final IgniteCache cache = ignite0.getOrCreateCache("testCache"); final Object monitor = new Object(); GridTes

Re: Renaming TcpDiscoverySpi.heartbeatsFrequency to TcpDiscoverySpi.metricsUpdateFrequency

Alex, I am finishing this up. --Yakov 2017-03-30 14:03 GMT+03:00 Александр Меньшиков : > Yakov, can I take this ticket or you have already started to implement it? > Ask because you are an assignee in JIRA. > > 2017-03-07 22:21 GMT+03:00 Denis Magda : > >> Good, the ticket is ready: >> https://i

[jira] [Created] (IGNITE-4884) Visorcmd - minor text mistake

Vyacheslav Daradur created IGNITE-4884: -- Summary: Visorcmd - minor text mistake Key: IGNITE-4884 URL: https://issues.apache.org/jira/browse/IGNITE-4884 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1698: IGNITE-4884

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1698 IGNITE-4884 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-4884 Alternatively you can review and apply these change

ignite-4884 - ready for review (Visorcmd - minor text mistake)

Hello everyone. Looks like minor mistake. Please review if someone has time. -- Best Regards, Vyacheslav

[GitHub] ignite pull request #1699: Ignite 4760

Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1699 --- 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

[GitHub] ignite pull request #1699: Ignite 4760

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1699 Ignite 4760 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4760 Alternatively you can review and apply these chan

[GitHub] ignite pull request #1700: Ignite 4760

GitHub user vadopolski opened a pull request: https://github.com/apache/ignite/pull/1700 Ignite 4760 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vadopolski/ignite ignite-4760 Alternatively you can review and apply these chan

[GitHub] ignite pull request #1700: Ignite 4760

Github user vadopolski closed the pull request at: https://github.com/apache/ignite/pull/1700 --- 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: ignite-4884 - ready for review (Visorcmd - minor text mistake)

I will do it tomorrow. On Thu, Mar 30, 2017 at 6:29 PM, Vyacheslav Daradur wrote: > Hello everyone. > > Looks like minor mistake. > > Please review if someone has time. > > -- > Best Regards, Vyacheslav > -- Alexey Kuznetsov

Re: Question: local cache on client nodes

It's abdolutely fine to have local caches on client nodes if an application needs to cache data locally in hashtable like data structure and talk to it using Ignite APIs. The upshot is that this kind of cache can be started on any node and we should keep supporting this capability in 2.0. -- Deni

Re: putting entity into cache while commiting.Why!?

I've edited code and now DIRTY READ occures! Ignite ignite0 = ignite(0); IgniteTransactions transactions = ignite0.transactions(); IgniteCache cache = ignite0.getOrCreateCache("testCache"); Object monitor = new Object(); GridTestUtils.runAsync(new Callable() { @Override public Object call

[jira] [Created] (IGNITE-4885) .NET: Meaningless exception on generic type in BinaryConfiguration

Pavel Tupitsyn created IGNITE-4885: -- Summary: .NET: Meaningless exception on generic type in BinaryConfiguration Key: IGNITE-4885 URL: https://issues.apache.org/jira/browse/IGNITE-4885 Project: Ignit

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Den, Mentioned enum is removed in PR for IGNITE-4587 issue. This PR isn't merged into master branch yet. On Thu, Mar 30, 2017 at 1:40 PM, Denis Magda wrote: > Do we need to merge anything else to the master branch or you mean the enum > was removed with the rest of the changes before and merged

[GitHub] ignite pull request #1701: IGNITE-2558: Remove extends MutableConfiguration,...

GitHub user dream-x opened a pull request: https://github.com/apache/ignite/pull/1701 IGNITE-2558: Remove extends MutableConfiguration, add setCopyOnRead method. [Jira](https://issues.apache.org/jira/browse/IGNITE-2558) You can merge this pull request into a Git repository by runnin

Real size of a stored data in IgniteCache

Hello everyone. How do I know real size of a stored data in the IgniteCache? For example: I created new cache and put one object, and I want to know real size of one object in cache. try (Ignite ignite = Ignition.start("cache-config.xml")) { IgniteCache cache = ignite.getOrCreateCache("myCa

Re: IGNITE-4052 ready for review

Hello everyone! Nikolay, method Protos.FrameworkInfo.Builder#setRoleBytes and Protos.FrameworkInfo.Builder#setUserBytes were added into IgniteFrameworkInfoTest. Details please what do you want to me do with the methods. How correctly to test methods work? The code was changed with official "Codi

[jira] [Created] (IGNITE-4886) VisorServiceTask should properly handle ClassNotFound exceptions.

Alexey Kuznetsov created IGNITE-4886: Summary: VisorServiceTask should properly handle ClassNotFound exceptions. Key: IGNITE-4886 URL: https://issues.apache.org/jira/browse/IGNITE-4886 Project: Ig

Re: Real size of a stored data in IgniteCache

Vyacheslav, Will JVisualVM + heap dump + analyzing objects count and sizes in heap dump works in your case? On Thu, Mar 30, 2017 at 8:26 PM, Vyacheslav Daradur wrote: > Hello everyone. > > How do I know real size of a stored data in the IgniteCache? > > For example: I created new cache and p

[GitHub] ignite pull request #1702: Ignite 4587

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/1702 Ignite 4587 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-4587 Alternatively you can review and apply these chan

Re: Real size of a stored data in IgniteCache

Alexey, Yes, it works in my case. Does Ignite provide any methods for my case? 2017-03-30 17:04 GMT+03:00 Alexey Kuznetsov : > Vyacheslav, > > Will JVisualVM + heap dump + analyzing objects count and sizes in heap > dump works in your case? > > > > On Thu, Mar 30, 2017 at 8:26 PM, Vyacheslav

Re: putting entity into cache while commiting.Why!?

Note that you call doInTransaction() for ignite(1), but you have acquired the cache reference for ignite(0), thus your cache.put() commits immediately from another node, because transactional scope is node-local. If you change the test either to use ignite(0) for doInTransaction, or to get the cac

Re: Real size of a stored data in IgniteCache

Hi Vyacheslav, No, Ignite doesn't provide such methods. However, you can see how it is overcome in one of EvictionPolicy implementations and make a proposal how it could be implemented. On Thu, Mar 30, 2017 at 5:20 PM, Vyacheslav Daradur wrote: > Alexey, > > Yes, it works in my case. > > Does I

[jira] [Created] (IGNITE-4887) Support for starting transaction in another thread

Alexey Kuznetsov created IGNITE-4887: Summary: Support for starting transaction in another thread Key: IGNITE-4887 URL: https://issues.apache.org/jira/browse/IGNITE-4887 Project: Ignite I

Re: distributed transaction of non-single coordinator

Hi ! Thanks for help. I've created ticket : https://issues.apache.org/jira/browse/IGNITE-4887 and a commit : https://github.com/voipp/ignite/commit/aa3487bd9c203394f534c605f84e06436b638e5c We really need this feature чт, 30 мар. 2017 г. в 11:31, Alexey Goncharuk : > Aleksey, > > I doubt your appr

Re: putting entity into cache while commiting.Why!?

I don't see point of commiting key1 only to zero node and thus creating drity value on zero node. чт, 30 мар. 2017 г. в 17:36, Alexey Goncharuk : > Note that you call doInTransaction() for ignite(1), but you have acquired > the cache reference for ignite(0), thus your cache.put() commits > immedi

[jira] [Created] (IGNITE-4888) An assertion error in TcpDiscoverySelfTest

Igor Seliverstov created IGNITE-4888: Summary: An assertion error in TcpDiscoverySelfTest Key: IGNITE-4888 URL: https://issues.apache.org/jira/browse/IGNITE-4888 Project: Ignite Issue Typ

[jira] [Created] (IGNITE-4889) Replacement of Cache Key classes with fields not participating in equals operation

Sergey Chugunov created IGNITE-4889: --- Summary: Replacement of Cache Key classes with fields not participating in equals operation Key: IGNITE-4889 URL: https://issues.apache.org/jira/browse/IGNITE-4889

Re: putting entity into cache while commiting.Why!?

Actually, there is no dirty value. The value is visible only in scope of the transaction. You call doInTransaction for ignite(1) thus initiating a pessimistic transaction. Inside doInTransaction cache.put is called, but cache belongs to the ignite(0) and therefore the put happens in an implicit tra

[GitHub] ignite pull request #1703: IGNITE-4888

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/1703 IGNITE-4888 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4888 Alternatively you can review and apply these

Re: Real size of a stored data in IgniteCache

Would it help if you had the total data size for a cache and a number of entries, which I believe Ignite provides? In this case, you can divide one by another and have your average object size. D. On Thu, Mar 30, 2017 at 7:42 AM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi Vyaches

Re: Making News page more visible

Sure, will implement it soon. Thanks, -P On Wed, Mar 29, 2017 at 7:16 PM, Denis Magda wrote: > Prachi, as one of the site maintainers, would you mind contributing this? > > Denis > > > On Wednesday, March 29, 2017, Tom Diederich > wrote: > >> Thanks, Denis! I agree that an anchor would make se

Re: Real size of a stored data in IgniteCache

Dmitry, as I understand Ignite doesn't provide a possibility to show real total size of objects in a IgniteCache. чт, 30 марта 2017 г. в 19:03, Dmitriy Setrakyan : > Would it help if you had the total data size for a cache and a number of > entries, which I believe Ignite provides? In this case,

Re: Real size of a stored data in IgniteCache

On Thu, Mar 30, 2017 at 9:30 AM, Vyacheslav Daradur wrote: > Dmitry, as I understand Ignite doesn't provide a possibility to show real > total size of objects in a IgniteCache. > Currently no, but the 2.0 release, which is fully off-heap, will provide a precise cache size.

[GitHub] ignite pull request #1704: IGNITE-4879: System pool starvation while partiti...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1704 IGNITE-4879: System pool starvation while partition evicting. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-

[GitHub] ignite pull request #1704: IGNITE-4879: System pool starvation while partiti...

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1704 --- 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

[GitHub] ignite pull request #1705: Ignite 4879

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1705 Ignite 4879 for tests purpose You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4879 Alternatively you can revie

usimg of other JTA implementation

Igniters! Why havent u made use of some open JTA implementation for distributed transactions instead of implementing own one -- *Best Regards,* *Kuznetsov Aleksey*

Re: usimg of other JTA implementation

On Thu, Mar 30, 2017 at 10:04 AM, ALEKSEY KUZNETSOV < alkuznetsov...@gmail.com> wrote: > Igniters! Why havent u made use of some open JTA implementation for > distributed transactions instead of implementing own one > Because using standard JTA would be much slower. Instead we chose to support JT

[GitHub] ignite pull request #1706: Ignite 4862

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1706 Ignite 4862 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4862 Alternatively you can review and apply the

Re: Apache Ignite 2.0 Release

Igniters, We are getting closer to proposed code freeze date. Could you please go through the list of required [1] tickets and provide brief update on where we are? As per myself, I am curerntly working on CREATE/DROP index feature stabilization and expect it to be ready for review on the next we

Re: Real size of a stored data in IgniteCache

Vyacheslav, Objects have different size in different runtime (x86 or Power, compress pointer on or off and so on). So only one possible way to see real size is do it in runtime. You can see how many bytes was allocated in one thread by using import *com.sun.management*.ThreadMXBean; ThreadMXB

[jira] [Created] (IGNITE-4890) Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions

Venky created IGNITE-4890: - Summary: Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions Key: IGNITE-4890 URL: https://issues.apache.org/jira/browse/

[jira] [Created] (IGNITE-4891) Key is deserialized during transactional get() even if withKeepBinary is set

Valentin Kulichenko created IGNITE-4891: --- Summary: Key is deserialized during transactional get() even if withKeepBinary is set Key: IGNITE-4891 URL: https://issues.apache.org/jira/browse/IGNITE-4891

[jira] [Created] (IGNITE-4892) Support DML for thin client based JDBC driver

Denis Magda created IGNITE-4892: --- Summary: Support DML for thin client based JDBC driver Key: IGNITE-4892 URL: https://issues.apache.org/jira/browse/IGNITE-4892 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4893) Release Ignite JDBC driver(s) under a single JAR

Denis Magda created IGNITE-4893: --- Summary: Release Ignite JDBC driver(s) under a single JAR Key: IGNITE-4893 URL: https://issues.apache.org/jira/browse/IGNITE-4893 Project: Ignite Issue Type: T

Re: jdbc vs jdbc2 packages

Folks, I had a chance to validate usability of both Ignite JDBC drivers at PGConf USA today trying to connect to the cluster from the new JetBrains DataGrip SQL tool [1]. Together with JetBrains folks we agreed on the following or spotted the issues listed below. 1) Default JDBC driver, that c

Re: Apache Ignite 2.0 Release

Vovan, I expect to finalize and merge Spring Data Integration by the code freeze time (April 14th):  IGNITE-1192Provide integration with Spring Data — Denis > On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov wrote: > > Igniters, > > We are ge

Cassandra store issues

Hi Igor, There are two recent questions on the user forum regarding ignite-cassandra module, and they seem to be very similar to each other: - http://apache-ignite-users.70518.x6.nabble.com/Timestamp-is-not-stored-correctly-with-Cassandra-td11590.html - http://apache-ignite-users.70

Re: Cassandra store issues

Hi Val, Thanks for the info. I replied to both questions. Regarding the first question - we just don't support mapping from java.sql.Timestamp to Cassandra's Datatype.Name.TIMESTAMP type, cause there are no direct mapping for it http://docs.datastax.com/en/developer/java-driver/3.1/manual/#cql-to

Re: Cassandra store issues

Igor, Thanks for clarifications! -Val On Thu, Mar 30, 2017 at 9:09 PM, Igor Rudyak wrote: > Hi Val, > > Thanks for the info. I replied to both questions. > > Regarding the first question - we just don't support mapping from > java.sql.Timestamp to Cassandra's Datatype.Name.TIMESTAMP type, caus

Re: distributed transaction of non-single coordinator

so what do u think on the issue ? чт, 30 Мар 2017 г., 17:49 ALEKSEY KUZNETSOV : > Hi ! Thanks for help. I've created ticket : > https://issues.apache.org/jira/browse/IGNITE-4887 > and a commit : > https://github.com/voipp/ignite/commit/aa3487bd9c203394f534c605f84e06436b638e5c > We really need thi