Re: Ignite 1.6 release timelines

I've finished with IGNITE-2959 Ignite JTA and WebSphere Application Server 8.5.5 and has been merged to 1.6. Also, I'm going to finish the following issues before 1.6 relase (they all almost done/under review/waiting for TC): [1] IGNITE-3056 Serv

[jira] [Created] (IGNITE-2973) CacheInterceptor gets mixed user and binary objects in case of 'withKeepBinary' cache and EntryProcessor which sets user object as a value

Artem Shutak created IGNITE-2973: Summary: CacheInterceptor gets mixed user and binary objects in case of 'withKeepBinary' cache and EntryProcessor which sets user object as a value Key: IGNITE-2973

[jira] [Created] (IGNITE-2971) Assertion error inside OPTIMISTIC SERIALIZABLE tx on 'get'

Artem Shutak created IGNITE-2971: Summary: Assertion error inside OPTIMISTIC SERIALIZABLE tx on 'get' Key: IGNITE-2971 URL: https://issues.apache.org/jira/browse/IGNITE-2971 Proje

[jira] [Created] (IGNITE-2959) Ignite JTA and WebSphere Application Server 8.5.5

Artem Shutak created IGNITE-2959: Summary: Ignite JTA and WebSphere Application Server 8.5.5 Key: IGNITE-2959 URL: https://issues.apache.org/jira/browse/IGNITE-2959 Project: Ignite Issue

[jira] [Created] (IGNITE-2958) Ignite Schema Import has to use full class names in fields map.

Artem Shutak created IGNITE-2958: Summary: Ignite Schema Import has to use full class names in fields map. Key: IGNITE-2958 URL: https://issues.apache.org/jira/browse/IGNITE-2958 Project: Ignite

[jira] [Created] (IGNITE-2953) tra marshalling and unmarshalling of invoke result with BinaryMarshaller

Artem Shutak created IGNITE-2953: Summary: tra marshalling and unmarshalling of invoke result with BinaryMarshaller Key: IGNITE-2953 URL: https://issues.apache.org/jira/browse/IGNITE-2953 Project

Re: Cleaning internal thread locals

Alexei, I would follow the Valentin's suggestion in the issue description and would add to Ignite tests a check on thread locals after stopping all grids. And then we will be able to fix thread local cleaning in all places. Thanks, -- Artem -- On Wed, Apr 6, 2016 at 11:18 AM, Alexei Scherbakov <

Re: Ignite 1.6 release timelines

Hi, I've added tests for non-collocated (distributed) SQL joins and found NPE (which can mask another issues). As I know Serj already started looking on it. -- Artem -- On Thu, Mar 17, 2016 at 9:36 PM, Dmitriy Setrakyan wrote: > Thanks Igor! > > Is there any update on the non-collocated SQL fu

[jira] [Created] (IGNITE-2848) Ignite OSGI exit code 1 on TC

Artem Shutak created IGNITE-2848: Summary: Ignite OSGI exit code 1 on TC Key: IGNITE-2848 URL: https://issues.apache.org/jira/browse/IGNITE-2848 Project: Ignite Issue Type: Bug

Re: Full API coverage enhancement

tusDiv Thanks, -- Artem -- On Tue, Mar 1, 2016 at 11:48 AM, Artem Shutak wrote: > > > -- Artem -- > > On Tue, Mar 1, 2016 at 1:31 AM, Dmitriy Setrakyan > wrote: > >> Thanks Artem! I think this test suite should go a long way towards >> removing >> issues wi

Re: Full API coverage enhancement

Feb 29, 2016 at 7:07 AM, Artem Shutak > wrote: > > > Igniters, > > > > I'm glad to announce that Configuration Variations test framework has > been > > merged to master and is ready to use. > > > > The framework provides an opportunity to write a

Re: Full API coverage enhancement

Igniters, I'm glad to announce that Configuration Variations test framework has been merged to master and is ready to use. The framework provides an opportunity to write a test-case once and to run it in many Ignite and Cache configuration variations, for different Ignite topologies (with and wit

[jira] [Created] (IGNITE-2733) Ignite should use actual AffinityTopologyVersion for LOCAL cache

Artem Shutak created IGNITE-2733: Summary: Ignite should use actual AffinityTopologyVersion for LOCAL cache Key: IGNITE-2733 URL: https://issues.apache.org/jira/browse/IGNITE-2733 Project: Ignite

[jira] [Created] (IGNITE-2664) Cache.invokeAll() return a map with BinaryObjects instead of user objects.

Artem Shutak created IGNITE-2664: Summary: Cache.invokeAll() return a map with BinaryObjects instead of user objects. Key: IGNITE-2664 URL: https://issues.apache.org/jira/browse/IGNITE-2664 Project

Re: NoopSwapSpaceSpi and dynamically started caches

there was no swap configured in Ignite. > > Starting FileSwapSpaceSpi all the time is not a good option as user will > face the same problem when trying to change to a different SPI. > > D. > > On Wed, Feb 10, 2016 at 4:39 AM, Artem Shutak > wrote: > > > Igniters, &

[jira] [Created] (IGNITE-2650) Ignite should throw an exception on start of dynamic cache with swap if Ignite uses NoopSwapSpaceSpi

Artem Shutak created IGNITE-2650: Summary: Ignite should throw an exception on start of dynamic cache with swap if Ignite uses NoopSwapSpaceSpi Key: IGNITE-2650 URL: https://issues.apache.org/jira/browse/IGNITE

NoopSwapSpaceSpi and dynamically started caches

Igniters, I've noticed an issue with NoopSwapSpaceSpi and dynamically started cashes. We have the following logic on node start: if (cfg.getSwapSpaceSpi() == null) { boolean needSwap = false; if (cfg.getCacheConfiguration() != null && !Boolean.TRUE.eq

[jira] [Created] (IGNITE-2590) IgniteCache.remove() returns false for LOCAL OFFHEAP_TIERED cache inside OPTIMISTIC REPEATABLE_READ transaction.

Artem Shutak created IGNITE-2590: Summary: IgniteCache.remove() returns false for LOCAL OFFHEAP_TIERED cache inside OPTIMISTIC REPEATABLE_READ transaction. Key: IGNITE-2590 URL: https://issues.apache.org/jira

Re: Full API coverage enhancement

; > What do you think? > > > On Mon, Feb 8, 2016 at 9:52 PM, Sergey Kozlov > wrote: > > > 1000 caches x 50MB = 50GB heap. Do we really have >50GB RAM on each > agents? > > > > On Mon, Feb 8, 2016 at 5:45 PM, Artem Shutak > wrote: > > > > >

Re: Full API coverage enhancement

t; > On Mon, Feb 8, 2016 at 5:07 PM, Artem Shutak wrote: > > > Hi all, > > > > I have an update. > > > > I've started from *CacheConfiguration* permutations. I wrote out a list > > with all CacheConfiguration setters and filtered it wit

Re: Full API coverage enhancement

ite API from all nodes. > > On Wed, Feb 3, 2016 at 6:40 PM, Artem Shutak wrote: > > > Dmitriy, > > > > Actually, I don't have a list with all the permutations. > > > > At first, we need to split in our discussion test cases and Ignite > > configuration w

Re: [jira] [Created] (IGNITE-2554) Affinity.mapKeyToNode() method throw "ArithmeticException: / by zero" for LOCAL cache

? as I am a newbie to ignite. 😁 > > Thanks, > kcheng > > On Thu, Feb 4, 2016 at 11:10 PM, Ken Cheng wrote: > > > Hi Artem Shutak , > > > > *Does this issue easy to reproduce? As I would like to work on it.* > > > > > > > > > > Thanks

[jira] [Created] (IGNITE-2554) Affinity.mapKeyToNode() method throw "ArithmeticException: / by zero" for LOCAL cache

Artem Shutak created IGNITE-2554: Summary: Affinity.mapKeyToNode() method throw "ArithmeticException: / by zero" for LOCAL cache Key: IGNITE-2554 URL: https://issues.apache.org/jira/browse/I

Re: Full API coverage enhancement

; Maybe someone see any other permutation to be supported? > > > > -- Artem -- > > > > On Tue, Feb 2, 2016 at 10:05 PM, Artem Shutak > > wrote: > > > > > Dmitriy, > > > > > > There is a branch at my fork and a pull request at Ig

Re: Full API coverage enhancement

enum value - We should also test Enums as keys and Enums as values - All operations should have single-key and multi-key operations Maybe someone see any other permutation to be supported? -- Artem -- On Tue, Feb 2, 2016 at 10:05 PM, Artem Shutak wrote: > Dmitriy, > > There is a bra

Re: Full API coverage enhancement

2, 2016 at 9:45 PM, Dmitriy Setrakyan wrote: > Artem, > > This is great. I have noticed from the ticket that you have created some > initial suite already. Is there a branch I can look at it? > > D. > > On Tue, Feb 2, 2016 at 10:02 AM, Artem Shutak > wrote: > > &

Full API coverage enhancement

Igniters, I'm working on an enhancement of Full API coverage [1] [2]. Ignite already has Full API test, but currently it's hard to test all configuration combinations. Feel free to add comments in the jira if you have any thought. [1] https://issues.apache.org/jira/browse/IGNITE-2521 [2] https:

[jira] [Created] (IGNITE-2521) Need to increase test coverage (support all configurations combinations)

Artem Shutak created IGNITE-2521: Summary: Need to increase test coverage (support all configurations combinations) Key: IGNITE-2521 URL: https://issues.apache.org/jira/browse/IGNITE-2521 Project

[jira] [Created] (IGNITE-2506) A damon node with binary marshaller hangs on unmarshalling of a user class

Artem Shutak created IGNITE-2506: Summary: A damon node with binary marshaller hangs on unmarshalling of a user class Key: IGNITE-2506 URL: https://issues.apache.org/jira/browse/IGNITE-2506 Project

Re: Binary ID mapper that uses a simple name of classes.

)* property. - BinaryBaseIdMapper - an implementation of BinaryBaseIdMapper that has *setLowerCase(boolean usLowerCase)* property. Thoughts? -- Artem -- On Thu, Jan 21, 2016 at 1:35 PM, Artem Shutak wrote: > Dmitriy, > > Out-of-the-box Ignite wil have 2 IdMappers: > - BinaryLower

Re: Binary ID mapper that uses a simple name of classes.

1 ID mapper with additional configuration properties. > > BTW, I still don’t get what a straight ID mapper means. > > D. > > On Wed, Jan 20, 2016 at 9:45 AM, Artem Shutak > wrote: > > > Dmitriy, > > > > BinaryStraightIdMapper - calculate hash code for given stri

Re: Binary ID mapper that uses a simple name of classes.

ust have one ID mapper with config properties, like > isSimpleName(), isLowerCase()? > > Also, what is a straight ID mapper? > > D. > > On Wed, Jan 20, 2016 at 4:01 AM, Artem Shutak > wrote: > > > Dmitriy, thanks for reminding me about this thread. > > > > Acc

Re: Binary ID mapper that uses a simple name of classes.

and BinaryStraightIdMapper names. Thanks, -- Artem -- On Wed, Jan 20, 2016 at 1:46 AM, Dmitriy Setrakyan wrote: > Artem, what name do you plan to give to the BinaryInternalIdMapper? > > On Fri, Jan 15, 2016 at 1:52 AM, Artem Shutak > wrote: > > > All Binary-related classes

Re: GridFutureAdapter: deprecate startTime(), duration() and endTime()

If it really can give as 5% of performance we have to do it. If anyone uses this methods we can support it by user request (if user explicitly asked about) and it will work slower in that case. For example, we can add *IgniteCache.withAsync(boolean useFutureWithTimer)* that will give to user an as

[jira] [Created] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

Artem Shutak created IGNITE-2395: Summary: Binary marshaller: id mapper must be resolved according to configuration. Key: IGNITE-2395 URL: https://issues.apache.org/jira/browse/IGNITE-2395 Project

Re: Binary ID mapper that uses a simple name of classes.

the same package that start > with word Binary? If not, then I agree. > > > > > > --Yakov > > > > 2016-01-14 4:59 GMT+03:00 Dmitriy Setrakyan : > > > > > I like the last one too. > > > > > > On Wed, Jan 13, 2016 at 7:54 AM, Artem

Binary ID mapper that uses a simple name of classes.

Igniters, I'm working on https://issues.apache.org/jira/browse/IGNITE-2191 (Binary marshaller: support user classes with the same simple name) bug. The fix expects new BinaryIdMapper that uses a simple name of classes. It is required for supporting of platforms (.Net. C++). I would be glade to h

[jira] [Created] (IGNITE-2372) GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes

Artem Shutak created IGNITE-2372: Summary: GridCacheAbstractDataStructuresFailoverSelfTest.testQueueConstant* fail sometimes Key: IGNITE-2372 URL: https://issues.apache.org/jira/browse/IGNITE-2372

Internal Portable -> Binary renaming.

Folks, I'm working on https://issues.apache.org/jira/browse/IGNITE-2065 (Need to get rid of 'Portable' word in internals). I want to ask everyone to not renaming by yourself any 'portable(2)' package or any Portable(2) class. If you will do it when changes can be lost, especially for package rena

Re: keepBinaryInStore

Huge +1 for Alexey's offer. When you did not know about this property, you will get an obscure exception on put operation [1] for the following code: IgniteCache cache = ignite.cache(null).withKeepBinary(); BinaryObject o = ignite.binary().builder("orders").setField("fname", "value

Re: AWS Tests on TeamCity

Igniters (especially Anton and Raul), Can someone shed a lite on the status of AWS build on TC? Presently all tests fail with The AWS Access Key Id you provided does not exist in our records. What does this mean? Someone configured the build with wrong ID? Can we just fix it? Or AWS account wit

[jira] [Created] (IGNITE-2063) Enable 4 windows agents on TC

Artem Shutak created IGNITE-2063: Summary: Enable 4 windows agents on TC Key: IGNITE-2063 URL: https://issues.apache.org/jira/browse/IGNITE-2063 Project: Ignite Issue Type: Task

Re: Disabling patch-validation mechanism on TC

gt; > > > [2] https://ignite.apache.org/community/contribute.html#contribute > > > > -- > > Denis > > > > On 12/1/2015 5:39 PM, Artem Shutak wrote: > >> Igniters, > >> > >> I'm working on adding to TC 4 windows agents. All Ig

Disabling patch-validation mechanism on TC

Igniters, I'm working on adding to TC 4 windows agents. All Ignite build have "Apply patch (if exist)" step which currently fails on Windows. I'm going to disable this step, it will disable "Patch validation" mechanism on TC [1]. As a result no one will be able to run TC for a patch file attached

IGNITE-1864 API

Folks (especially Valentin), I want to fix https://issues.apache.org/jira/browse/IGNITE-1864 (Cannot configure jndiNames for CacheJndiTmLookup). I was going to fix it as Val suggested in comments I think we should deprecate CacheTmLookup interface with its > implementations and txManagerLookupCl

AIEX project contribution.

Igniters, I glad to announce a contribution to Ignite [1]. It's pretty cool separate project which can be used as GUI for Ignite (currently for topology and cache) and works via Ignite REST API. Currently, I am corresponding with the contributor via user list [2]. I think, someone from commiters

Re: IGNITE-1355 Potential NPE in CacheAffinityProxy

o, I would still allow proxy creation for > unexistent caches, but throw an exception if cache does not exist at the > moment of proxy method call. > > --Yakov > > 2015-11-12 16:01 GMT+03:00 Artem Shutak : > > > Igniters, > > > > I'm working on https://issue

Re: Necessity to have MBeanServerResource annotation

Igniters, As I remember, support of the annotation has been deleted intentionally. I think Nik can shed light on this. By the way, currently, you can use IgniteInstanceResource annotation to get Ignite instance and getting MBeanServer. ignite.configuration().getMBeanServer() Thanks, -- Artem --

Re: Branch deletion prohibited

Dmitriy, No, according to a note [1] on the wiki page [2] we need to check on unmerged changes before. Looks like we should add a status column (someone already has proposed it) where we can track is a branch ready to delete or not. [1] *Note. We don’t remove any *unmerged* branches. Even if the

Re: IGNITE-1227 patch available

Denis, Amir, First of all, need to understand how it works on TC. TC downloads a patch file and applies it by 'git am ' to the latest master. That is mentioned on How to Contribute - see "2. Create a Patch-file"/"Applying" As

Re: IGNITE-1355 Potential NPE in CacheAffinityProxy

nite2.cache("myCache").destroy(); affinity.mapPartitionToNode(0); // NPE. This case looks like an exception for me, so I need to change my opinion and I vote for throwing a special exception if cache does not exists. -- Artem -- On Thu, Nov 12, 2015 at 4:01 PM, Artem Shutak wrote: > I

IGNITE-1355 Potential NPE in CacheAffinityProxy

Igniters, I'm working on https://issues.apache.org/jira/browse/IGNITE-1355. I want to hear a community opinion what should do Ignite in case when user uses Affinity for nonexistent cache? Current implementation returns AffinityProxy on a call of Ignite.affinity("nonexistent_cache") and AffinityPr

Re: GIT branch audit

forgot to merge. I ask > that before deleting a branch, we take an extra step to verify that the > changes are in the master. > > D. > > On Tue, Oct 20, 2015 at 8:16 AM, Artem Shutak > wrote: > > > Folks, > > > > I've reviewed branches. > > &

[jira] [Created] (IGNITE-1865) Need to add tests on SpringResource annotation

Artem Shutak created IGNITE-1865: Summary: Need to add tests on SpringResource annotation Key: IGNITE-1865 URL: https://issues.apache.org/jira/browse/IGNITE-1865 Project: Ignite Issue Type

Re: IgniteAtomicReference, compareAndSet, and nulls

Igniters, I've assigned the ticket to yourself and already fixed it. Will check TC (I believe the fix could not brake something) and will send for review. Thanks, -- Artem -- On Thu, Nov 5, 2015 at 4:55 PM, Pavel Tupitsyn wrote: > Done: https://issues.apache.org/jira/browse/IGNITE-1863 > > On

Re: Questions about TeamCity CI organization

hat it's > covered by a TC job. > > Thanks, > > *Raúl Kripalani* > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and > Messaging Engineer > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitte

Re: Questions about TeamCity CI organization

Hi Raul, 1. Yes, this is correct separation. If you are working on some new feature usually in development process you want to run only your build, may be 2, but not all tests. And only when a feature is close to complete you want to run all tests. 2. There are at least 2 goals: - Don't run all t

[jira] [Created] (IGNITE-1824) IgniteCacheTxNearPeekModesTest.testLocalPeek fails on TC sometimes.

Artem Shutak created IGNITE-1824: Summary: IgniteCacheTxNearPeekModesTest.testLocalPeek fails on TC sometimes. Key: IGNITE-1824 URL: https://issues.apache.org/jira/browse/IGNITE-1824 Project: Ignite

[jira] [Created] (IGNITE-1823) Peer class loading can produce ClassCastException with DeploymentMode.SHARED (default)

Artem Shutak created IGNITE-1823: Summary: Peer class loading can produce ClassCastException with DeploymentMode.SHARED (default) Key: IGNITE-1823 URL: https://issues.apache.org/jira/browse/IGNITE-1823

Re: log4j2 garbage files

Hi Raul, Oh, I was sure I deleted these files. Fixed in my PR: https://github.com/apache/ignite/pull/188. Raul, Gianfranco, please, review and merge the fix. Thanks, -- Artem -- On Thu, Oct 29, 2015 at 9:46 PM, Raul Kripalani wrote: > Gianfranco, Artem, > > Could you please check why we have

Re: [Ignite-429] facing problem with node startup

default port range is 100, so Ignite will automatically pick the next > > available port in the range. > > > > > > > > > > Regards > > > Saikat > > > > > > On Mon, Oct 26, 2015 at 7:13 PM, Artem Shutak > > > wrote: > > >

[jira] [Created] (IGNITE-1809) GridCacheAtomicMultiNodeP2PDisabledFullApiSelfTest.testWithSkipStore fails on TC sometimes

Artem Shutak created IGNITE-1809: Summary: GridCacheAtomicMultiNodeP2PDisabledFullApiSelfTest.testWithSkipStore fails on TC sometimes Key: IGNITE-1809 URL: https://issues.apache.org/jira/browse/IGNITE-1809

[jira] [Created] (IGNITE-1802) Ignite.countDownLatch() can return null if latch has been already created.

Artem Shutak created IGNITE-1802: Summary: Ignite.countDownLatch() can return null if latch has been already created. Key: IGNITE-1802 URL: https://issues.apache.org/jira/browse/IGNITE-1802 Project

[jira] [Created] (IGNITE-1800) Annotation MBeanServerResource should be deleted as unsupported.

Artem Shutak created IGNITE-1800: Summary: Annotation MBeanServerResource should be deleted as unsupported. Key: IGNITE-1800 URL: https://issues.apache.org/jira/browse/IGNITE-1800 Project: Ignite

[jira] [Created] (IGNITE-1795) TcpCommunicationSpi tests fail only on Mac

Artem Shutak created IGNITE-1795: Summary: TcpCommunicationSpi tests fail only on Mac Key: IGNITE-1795 URL: https://issues.apache.org/jira/browse/IGNITE-1795 Project: Ignite Issue Type: Test

[jira] [Created] (IGNITE-1794) Ignite should support Hibernate 5

Artem Shutak created IGNITE-1794: Summary: Ignite should support Hibernate 5 Key: IGNITE-1794 URL: https://issues.apache.org/jira/browse/IGNITE-1794 Project: Ignite Issue Type: Test

[jira] [Created] (IGNITE-1793) [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes

Artem Shutak created IGNITE-1793: Summary: [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes Key: IGNITE-1793 URL: https://issues.apache.org/jira/browse/IGNITE-1793

Re: [Ignite-429] facing problem with node startup

My mistake. IgniteConfiguration.setGridName(). -- Artem -- On Mon, Oct 26, 2015 at 4:42 PM, Artem Shutak wrote: > Hi Chandresh, > > As I understand you want to run cluster (more than one Ignite node) in one > JVM. In the case you should specify different names f

Re: [Ignite-429] facing problem with node startup

Hi Chandresh, As I understand you want to run cluster (more than one Ignite node) in one JVM. In the case you should specify different names for nodes via IgniteConfiguration.setName(). I strongly recommend you do not invent the wheel and extend your test class from GridAbstarctTest which has met

Re: Account @ TeamCity, please

gt; raulk > > Cheers, > > *Raúl Kripalani* > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and > Messaging Engineer > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk > > On

Re: Account @ TeamCity, please

Give me please your account. Thanks, -- Artem -- On Mon, Oct 26, 2015 at 3:15 PM, Raul Kripalani wrote: > Ok, got it. But now I need to add new projects for JMS, MQTT, ZooKeeper > with their corresponding test suites. > > Could someone please give me the admin role? > > Thanks, > > *Raúl Kripal

[jira] [Created] (IGNITE-1784) [Failed Test] GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails on TC sometimes.

Artem Shutak created IGNITE-1784: Summary: [Failed Test] GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails on TC sometimes. Key: IGNITE-1784 URL: https://issues.apache.org/jira/browse/IGNITE-1784

Re: TC patch validation

Cos, see email. -- Artem -- On Thu, Oct 22, 2015 at 9:15 PM, Konstantin Boudnik wrote: > On Thu, Oct 22, 2015 at 01:28PM, Artem Shutak wrote: > > Yes, automatic runs were disabled for patches too. > > > > To run patches you can use "Run All for patch" wi

Re: IGNITE-1371 patch is ready

Hi Igor, Please, see my comments in the Jira. -- Artem -- On Wed, Oct 21, 2015 at 3:50 AM, Igor Rudyak wrote: > Hi guys, > > I attached patch for IGNITE-1371 on a previous week, but looks like it > wasn't taken into consideration. > > I am assuming that may be I forgot to do some extra steps w

[jira] [Created] (IGNITE-1776) [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes

Artem Shutak created IGNITE-1776: Summary: [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes Key: IGNITE-1776 URL: https://issues.apache.org/jira/browse/IGNITE-1776

Re: TC patch validation

Yes, automatic runs were disabled for patches too. To run patches you can use "Run All for patch" with specified jira number at "Paramethers / Jira number*". -- Artem -- On Thu, Oct 22, 2015 at 4:11 AM, Dmitriy Setrakyan wrote: > I think Cos’ question also was why the patches attached to Jira

[jira] [Created] (IGNITE-1771) Ignite should support Apache Spark 1.5.1

Artem Shutak created IGNITE-1771: Summary: Ignite should support Apache Spark 1.5.1 Key: IGNITE-1771 URL: https://issues.apache.org/jira/browse/IGNITE-1771 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-1757) [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes

Artem Shutak created IGNITE-1757: Summary: [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes Key: IGNITE-1757 URL: https://issues.apache.org/jira/browse/IGNITE-1757

[jira] [Created] (IGNITE-1756) [Test Failed] GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator fails sometimes

Artem Shutak created IGNITE-1756: Summary: [Test Failed] GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator fails sometimes Key: IGNITE-1756 URL: https://issues.apache.org/jira/browse

Re: URI deployment ticket

Val, I fixed the test and rechecked TC. Please, review and merge my PR: https://github.com/apache/ignite/pull/166. -- Artem -- On Fri, Oct 16, 2015 at 3:44 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Artem, > > I merged the ticket [1] where you fixed URI deployment JavaDoc

Re: GIT branch audit

Folks, I've reviewed branches. Branches under [1] refer to already Closed tickets (61 branches). Branches under [2] don't refer to any Jira (34 branches). I think someone with commiter-rights should remove branches from [1]. Branches from [2] should be deleted by branch creators. [1] ignite-101

[jira] [Created] (IGNITE-1739) [Test Failed] GridUpdateNotifierSelfTest.testNotifier

Artem Shutak created IGNITE-1739: Summary: [Test Failed] GridUpdateNotifierSelfTest.testNotifier Key: IGNITE-1739 URL: https://issues.apache.org/jira/browse/IGNITE-1739 Project: Ignite Issue

[jira] [Created] (IGNITE-1738) [Test Failed] IgniteClientReconnectCacheTest.testReconnect

Artem Shutak created IGNITE-1738: Summary: [Test Failed] IgniteClientReconnectCacheTest.testReconnect Key: IGNITE-1738 URL: https://issues.apache.org/jira/browse/IGNITE-1738 Project: Ignite

Re: Looking to contribute to apache ignite

Hi Nimit, Welcome to Ignite community! We definitely can use your help. The best way to get started, is to download the project and play with examples: https://github.com/apache/ignite/tree/master/examples You should also get familiar with available Ignite resources, like Wiki, Jira, etc: https:

[jira] [Created] (IGNITE-1731) [Test Failed] GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupRollbackOptimistic

Artem Shutak created IGNITE-1731: Summary: [Test Failed] GridCacheTxNodeFailureSelfTest.testPrimaryNodeFailureBackupRollbackOptimistic Key: IGNITE-1731 URL: https://issues.apache.org/jira/browse/IGNITE-1731

[jira] [Created] (IGNITE-1684) NPE in GridCacheProcessor.processClientReconnectData on client left

Artem Shutak created IGNITE-1684: Summary: NPE in GridCacheProcessor.processClientReconnectData on client left Key: IGNITE-1684 URL: https://issues.apache.org/jira/browse/IGNITE-1684 Project: Ignite

[jira] [Created] (IGNITE-1635) Cache.invoke() can work wrong in a failover scenario

Artem Shutak created IGNITE-1635: Summary: Cache.invoke() can work wrong in a failover scenario Key: IGNITE-1635 URL: https://issues.apache.org/jira/browse/IGNITE-1635 Project: Ignite Issue

Re: New 'Deployment tasks' article on readme.io

tem -- On Wed, Sep 30, 2015 at 3:10 PM, Dmitriy Setrakyan wrote: > On Wed, Sep 30, 2015 at 11:08 AM, Artem Shutak > wrote: > > > Dmitriy, I think it should stay under "Compute Grid" block because > > Deployment SPI have the meaning only for ComputeTasks. > > &

Re: New 'Deployment tasks' article on readme.io

gt; > Artem, > > > > I would move the deployment SPI documentation as a bottom section in > "Zero > > Deployment" page. Also, please use this link for documentation: > > > > https://apacheignite.readme.io/docs > > > > D. > > > > On

New 'Deployment tasks' article on readme.io

Folks, In process of working on [1] I've been created new article [2] on readme.io as long as this functionality has been missed in documentation. Please review and feel free to comment. [1] https://issues.apache.org/jira/browse/IGNITE-1559 [2] http://apacheignite.gridgain.org/docs/deployment-tas

[jira] [Created] (IGNITE-1559) Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner.

Artem Shutak created IGNITE-1559: Summary: Need to improve tests, javadoc and documentation of UriDeploymentHttpScanner. Key: IGNITE-1559 URL: https://issues.apache.org/jira/browse/IGNITE-1559

Re: Client node throws exception when server node killed

nodes, I'll try to reproduce this error. > > On Mon, Sep 21, 2015 at 8:31 PM, Artem Shutak > wrote: > > > Igniters, > > > > In process of working on [1] I've found that Ignite client node throws > > CacheException which caused by IgniteClientDisconnec

[jira] [Created] (IGNITE-1524) Client node throws exception when server node killed

Artem Shutak created IGNITE-1524: Summary: Client node throws exception when server node killed Key: IGNITE-1524 URL: https://issues.apache.org/jira/browse/IGNITE-1524 Project: Ignite Issue

Re: Maybe review my first commits

Hi Raul, TC has been down sometime ago and it has been up on http://204.14.53.153/ (proper email has been sent on dev). As I know currently Evgeny is working on stabilization and after TC will be return back on http://204.14.53.152/. Evgeny, am I right? What status of TC stabilization? If TC is

Client node throws exception when server node killed

Igniters, In process of working on [1] I've found that Ignite client node throws CacheException which caused by IgniteClientDisconnectedException (stack trace below) sometimes when I kill one server node at cluster. It looks like not expected behavior for me. Is it know issue? My configuration:

Re: Anyone faced this issue while writing unit tests. Please help

..@gmail.com> wrote: > > > >> While doing git push i am getting Auth error. Its not accepting git-hub > >> profile. > >> > >> > >> On Tue, Sep 15, 2015 at 5:08 PM, Artem Shutak > >> wrote: > >> > >>> Hi Chandresh, >

Re: Anyone faced this issue while writing unit tests. Please help

Hi Chandresh, It looks like for me you have different log4j versions at your classpath. How do you build your project? Did you copy-paste log4j jars by yourself? It would be nice, if you commit and push a current state of your project at your fork on github and point out on your fork, branch at f

[jira] [Created] (IGNITE-1397) Load/consistency test framework

Artem Shutak created IGNITE-1397: Summary: Load/consistency test framework Key: IGNITE-1397 URL: https://issues.apache.org/jira/browse/IGNITE-1397 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-1383) Need to have ability to use apply-pull-request.sh script for non-master branches

Artem Shutak created IGNITE-1383: Summary: Need to have ability to use apply-pull-request.sh script for non-master branches Key: IGNITE-1383 URL: https://issues.apache.org/jira/browse/IGNITE-1383

Re: TC hell

So, I've disabled auto triggering for pull-requests. -- Artem -- On Fri, Aug 28, 2015 at 12:17 PM, Artem Shutak wrote: > I've checked and currently everyone can create TC account for yourself and > the account will have privileges to trigger builds (without any > admini

  1   2   >