[GitHub] ignite pull request #866: Ignite 3424

[AndreyVel]

Github user AndreyVel closed the pull request at:

https://github.com/apache/ignite/pull/866


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #945: ignite-3197 added method tryChanelLock

[AndreyVel]

Github user AndreyVel closed the pull request at:

https://github.com/apache/ignite/pull/945


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #940: Ignite 2079

[AndreyVel]

GitHub user AndreyVel opened a pull request:

https://github.com/apache/ignite/pull/940

Ignite 2079

Please, make review changes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/AndreyVel/ignite ignite-2079

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/940.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #940


commit 91a88be909a9c22abb6d91a7d58f46c9dad2c874
Author: AndreyVel <andrey4...@gmail.com>
Date:   2016-08-09T12:42:40Z

ignite-2079 unit test done

commit cc4651a6c7448f15921477bf476527651db87981
Author: AndreyVel <andrey4...@gmail.com>
Date:   2016-08-09T13:34:40Z

Merge branch 'ignite-2079' of https://github.com/AndreyVel/ignite into 
ignite-2079




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #915: ignite-3601 Added unit test testConcurrentTxGet

[AndreyVel]

GitHub user AndreyVel opened a pull request:

https://github.com/apache/ignite/pull/915

ignite-3601 Added unit test testConcurrentTxGet

Please, make review changes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/AndreyVel/ignite ignite-3601

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/915.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #915


commit 396ad5de3b018060452760823eeb14dcd885ac64
Author: AndreyVel <andrey4...@gmail.com>
Date:   2016-08-02T09:04:24Z

ignite-3601 Added unit test testConcurrentTxGet




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Ignite message ping metric

[AndreyVel]

Hi everyone,

What do you think if to add ignite message ping metric between nodes and 
display it in monitoring tools?

This metric can be displayed as matrix [All nodes] * [All nodes]

Sometime to hard find, why cluster has bad performance, one of reason 
can be bad network performance between same nodes.
One bad network card or network configuration can kill performance whole 
cluster.

Re: Ignite 2.0 tasks/roadmap

[AndreyVel]

Good feature may be Aggregated cache - analog materialized view in DBMS
Aggregated cache is great for performance (KPI, analytecal reports).

Recently I learned network traffic between nodes when node 
restart/startup and do no found any compressing for transferred data.


I know there is IgniteDataStreamer for writing cache, but how about 
reading cache as stream for iterate all elements with scan performane 
1-3M tuple/sec?



14.07.2016 4:43, Alexey Goncharuk пишет:

So, no excitement about Ignite 2.0? :)

I went ahead and created a 2.0 version in Ignite Jira, and included the
following tickets so far based on the chance that this ticket will require
breaking changes in APIs/Configuration
  - IGNITE-3469 - Get rid of deprecated APIs and code
  - IGNTIE-3477 - Rework offheap storage
  - IGNITE-3478 - Transactional SQL
  - IGNITE-1605 - Provide stronger data loss check
  - IGNITE-3306 - Extend IgniteCluster interface with the methods to send
and receive custom discovery events

I believe that there are many more changes that we wanted to make but
delayed because they would break binary compatibility, so if you have
something in mind - it's time to create a ticket or assign it to 2.0 if it
exists. It's good to know the scope of work.

Also, it would be great if you review/comment the above-mentioned tickets.

Thanks,
AG

Cache performance for LOCAL mode + setIndexedTypes

[AndreyVel]

Hello, I have created simple test for testing performance put operations 
on single computer,
can anybody explain why performance for LOCAL mode different for Indexed 
and non Indexed mode?



 Cache performance put(Integer, String)/sec: one client and 2
 remote servers.

CacheMode   TRANSACTIONAL   TRANSACTIONAL
setIndexedTypes(Integer, String)ATOMIC  ATOMIC
setIndexedTypes(Integer, String)
LOCAL   45154   107306  340627  581250
REPLICATED  3270286572725694
PARTITIONED 6773540385586714


VM options -Xms1g -Xmx1g
Topology snapshot [ver=5, servers=2, clients=1, CPUs=8, heap=3.0GB]


public class CachePerformance {

private static int CACHE_SIZE =100 * 1000;
private static StringCACHE_NAME ="cachePerf";

public static void main(String[] args) {
try {
Ignition.setClientMode(true);
IgniteConfiguration igniteCfg =new IgniteConfiguration();
igniteCfg.setPeerClassLoadingEnabled(true);

Ignite ignite = Ignition.start(igniteCfg);
CachePerformance.execute(ignite);
}catch (Throwable ex) {
ex.printStackTrace();
}
}

public static void execute(Ignite ignite)throws Exception {

Random rand =new Random();

for (CacheMode cacheMode : CacheMode.values()) {

for (CacheAtomicityMode atomMode : CacheAtomicityMode.values()) {
for (int indexMode =0; indexMode <=1; indexMode++) {

CacheConfiguration cacheCfg =new 
CacheConfiguration<>(CACHE_NAME);
if (indexMode ==1)
cacheCfg.setIndexedTypes(Integer.class, String.class);

cacheCfg.setAtomicityMode(atomMode);
cacheCfg.setCacheMode(cacheMode);

ignite.destroyCache(CACHE_NAME);
IgniteCache cache = 
ignite.getOrCreateCache(cacheCfg);
String cacheDesc ="cacheMode=" + cacheMode +", atomMode=" + atomMode 
+", indexMode=" + indexMode;

long time = System.nanoTime();
for (int ind =0; ind Cache unhandled exception


2016-07-11

Thread
AndreyVel


I have question about https://issues.apache.org/jira/browse/IGNITE-2079

Sametime need send notification for client listener about unhandled 
exception,  what do you think if to add new class CacheExceptionEvent ?

Maybe there is more convenient event type/name ?

Server code
CacheExceptionEvent evt = new CacheExceptionEvent(node, shortMsg, 
ex, EVT_UNHANDLED_EXCEPTION);

ctx.event().record(evt);

Client code example

grid(0).events().localListen(new IgnitePredicate() {
@Override public boolean apply(Event event) {
. . .  return true;
}
}, EventType.EVT_UNHANDLED_EXCEPTION);






[GitHub] ignite pull request #866: Ignite 3424


2016-07-11

Thread
AndreyVel

GitHub user AndreyVel opened a pull request:

https://github.com/apache/ignite/pull/866

Ignite 3424

Added unit test IgniteCacheP2pUnmarshallingContinuousQueryErrorTest

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3424

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/866.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #866


commit 9b096ac50c9e31e11aa07e77527291d73604b44b
Author: agura <ag...@gridgain.com>
Date:   2016-03-17T13:33:17Z

GridCacheOnCopyFlag tests are fixed for binary object marshaller

commit ab8c0dd1990a80f3120be4b6db3aeab3f8aee35b
Author: agura <ag...@gridgain.com>
Date:   2016-01-18T14:23:47Z

IgniteCacheP2pUnmarshallingQueryErrorTest fixed

commit 9a8cf6223d3901c6d155edb4080d94adc7748da6
Author: agura <ag...@gridgain.com>
Date:   2016-03-17T14:40:23Z

GridAffinitySelfTest.testAffinity fixed

commit f922840f42736a7c22d4566fd51da4df18be30b3
Author: agura <ag...@gridgain.com>
Date:   2016-02-29T15:39:45Z

ignite-2734 Binary enum type deserialization from offheap

commit fa356e306e6c8748af1b571427d24e73a12bbd6e
Author: Yakov Zhdanov <yzhda...@gridgain.com>
Date:   2016-03-18T13:09:35Z

Added ability to dump comm SPI stats to log.

commit 5be5fa080c7160184c9fbfa9b8b9b748f80c3078
Author: agura <ag...@gridgain.com>
Date:   2016-03-17T12:18:44Z

ignite-2797 Incorrect timeout calculation for optimistic transactions fixed

commit aafd6f77feb03b1f56efddfbef8f116b65a5ce4e
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-21T15:52:08Z

Fixed CacheContinuousQueryLostPartitionTest.testAtomicClientEvent test.

commit fca47ec77e4ec6753765e531cd557a279d10d125
Author: Tikhonov Nikolay <tikhonovnico...@gmail.com>
Date:   2016-03-21T20:44:56Z

Fixed IGNITE-2791 "Continuous query listener is not notified during 
concurrent key put and registration."

commit d182da2a6d2821182ae6e636711cd15a44e4ca21
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-22T11:03:42Z

Fixed TCK tests.

commit f76a3133f40e67621bd4dec54e173f04cbe21485
Author: Yakov Zhdanov <yzhda...@gridgain.com>
Date:   2016-03-22T12:58:49Z

Added ability to dump comm SPI recovery descriptors

commit 660aa2f7b3948d34f20baac516d29e43984f4ede
Author: Yakov Zhdanov <yzhda...@gridgain.com>
Date:   2016-03-22T14:03:03Z

Added ability to dump direct message reader and writer

commit 3def50cecc70ee45be5d71a7b82c41f9e9e484b4
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-23T11:03:26Z

Fixed tests.

commit aa8dcd11aa311e6dd639e0a25c5b0eb714e663ad
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-23T12:47:17Z

Fixed Ignite Client Nodes suite.

commit 4cb994a7253c6b493b4a376ed1489513ecefd8f9
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-25T08:20:39Z

IGNITE-GG-11048 Fix missed event notification in remove-remove case.

commit 31ae7ea791e258c49f1b25944cba75fd08d0ca49
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-25T09:37:25Z

Removed isDebug from test.

commit 1c04005c08ae7ca2006d6f2f687a95c2638c73fc
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-25T12:22:37Z

IGNITE-GG-11048 Added tests.

commit 53a87290fe028e12a81058fc4b2f2f2341395f9a
Author: Tikhonov Nikolay <tikhonovnico...@gmail.com>
Date:   2016-03-25T16:49:31Z

Fixed tests (renamed test methods).

commit ce56625099b5253f8baf27bfbcff4682787a5ee1
Author: Anton Vinogradov <a...@apache.org>
Date:   2016-03-28T11:13:20Z

Query Suite separation : 1,2,3

commit 08f5981509711e65c0d4c6fc1209068f8958eb06
Author: vozerov-gridgain <voze...@gridgain.com>
Date:   2016-03-28T09:24:16Z

Support optional IO policy resolver in DataStreamer.

commit 60e74618b310dafc28eb5f935859fed4ec87584c
Author: vozerov-gridgain <voze...@gridgain.com>
Date:   2016-03-28T11:52:13Z

Merge remote-tracking branch 'upstream/gridgain-7.5.10' into gridgain-7.5.10

commit 9e84e508a394b790ef046cdcf2a015bcf853c064
Author: nikolay_tikhonov <ntikho...@gridgain.com>
Date:   2016-03-28T13:59:56Z

Divide test suite.

commit d36a2e51e3aa3105dff73839c84e52a531fbd918
Author: Denis Magda <dma...@gridgain.com>
Date:   2016-03-24T17:07:48Z

IGNITE-2849: BinaryObjectBuilder doesn't properly check metadata

commit 9e62b667e73396d3affbc4d1e62449d07d08ec8b
Author: Anton Vinogradov <a...@apache.org>
Date:   2016-03-29T11:56:21Z

 IGNITE-2801 Coordinator floods network with partitions full map exchange 
messages

commit 85a675b7bfbc54745ee9ce95d5786b5bae5be963
Author: iveselovskiy <iveselovs...@gri



[GitHub] ignite pull request #812: IGNITE-1018


2016-06-17

Thread
AndreyVel

GitHub user AndreyVel opened a pull request:

https://github.com/apache/ignite/pull/812

IGNITE-1018

Node local map is not available when LifecycleEventType.BEFORE_NODE_START 
is processed in lifecycle bean

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/AndreyVel/ignite ignite-1018

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/812.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #812


commit a56c8b3140bf9af7f562f4cec879278e4fa0e699
Author: AndreyVel <andrey4...@gmail.com>
Date:   2016-06-17T09:54:00Z

IGNITE-1018

Node local map is not available when LifecycleEventType.BEFORE_NODE_START 
is processed in lifecycle bean




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---