[jira] [Assigned] (IGNITE-5580) Improve node failure cause information
[ https://issues.apache.org/jira/browse/IGNITE-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-5580: - Assignee: (was: Vadim Opolski) > Improve node failure cause information > -- > > Key: IGNITE-5580 > URL: https://issues.apache.org/jira/browse/IGNITE-5580 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Alexey Goncharuk > Labels: observability > > When a node fails, we do not print out any information about the root cause > of this failure. This makes it extremely hard to investigate the failure > causes - I need to find a previous node for the failed node and check the > logs on the previous node. > I suggest that we add extensive information about the reason of the node > failure and the sequence of events that led to this, e.g.: > [time] [NODE] Sending a message to next node - failed _because_ - write > timeout, read timeout, ...? > [time] [NODE] Connection check - failed - why? Connection refused, handshake > timed out, ...? > ... > [time] [NODE] Decided to drop the node because of the sequence above > Maybe we do not need to print out this information always, but we do need > this when troubleshooting logger is enabled. > Also, DiscoverySpi should collect a set of latest important events and dump > these events in case of local node segmentation. This will allow users to > match the events in the cluster and events on local node and get to the > bottom of the failure. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5561) Warn about long-running cache store operations
[ https://issues.apache.org/jira/browse/IGNITE-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-5561: - Assignee: (was: Vadim Opolski) > Warn about long-running cache store operations > -- > > Key: IGNITE-5561 > URL: https://issues.apache.org/jira/browse/IGNITE-5561 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.7 >Reporter: Alexey Goncharuk > Labels: observability > > When a cache store is used, it may become very confusing if a cache store > performs a very long-running operation, because in this case, Ignite would > output a warning about long-running cache operations. I think, in addition to > that, we should measure and output a warning if a specific cache store > operation took too long. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-2049) Add to GridProductVersionSelfTest new tests for new naming strategy
[ https://issues.apache.org/jira/browse/IGNITE-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-2049: - Assignee: (was: Vadim Opolski) > Add to GridProductVersionSelfTest new tests for new naming strategy > --- > > Key: IGNITE-2049 > URL: https://issues.apache.org/jira/browse/IGNITE-2049 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Priority: Trivial > Labels: newbie > > See > http://apache-ignite-developers.2346864.n4.nabble.com/EA-versioning-td5381.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-3142:
-
Assignee: Vadim Opolski
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3], writeVer=null,
> implicit=true, loc=true, threadId=32, startTime=1463390725843,
> nodeId=df815072-615a-49d4-92e1-2842369ea15a, startVer=GridCacheVersion
> [topVer=74870619, time=1463390725845, order=1463390656380, nodeOrder=3],
> endVer=null, isolation=READ_COMMITTED,
[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178124#comment-16178124
]
Vadim Opolski commented on IGNITE-5979:
---
Hi [~sboikov], [~avinogradov] As I can see, test is failing approximately in
20% of runs. The reason of failure is not matching entry value in local and
backup nodes. It looks like affinity function didn't complete and additional
timeout is needed. Could you please advice, where extra timeout might be needed?
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5136) GridLogThrottle memory leak
[ https://issues.apache.org/jira/browse/IGNITE-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169413#comment-16169413 ] Vadim Opolski commented on IGNITE-5136: --- [~zstan] [~avinogradov] In my opinion tests look good. [TC Overview | https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll_Ignite20Tests=pull%2F2674%2Fmerge=buildTypeStatusDiv] > GridLogThrottle memory leak > --- > > Key: IGNITE-5136 > URL: https://issues.apache.org/jira/browse/IGNITE-5136 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Stanilovsky Evgeny >Assignee: Vadim Opolski > > class GridLogThrottle stores throttle info into map and noone clears it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5136) GridLogThrottle memory leak
[ https://issues.apache.org/jira/browse/IGNITE-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-5136: - Assignee: Vadim Opolski > GridLogThrottle memory leak > --- > > Key: IGNITE-5136 > URL: https://issues.apache.org/jira/browse/IGNITE-5136 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Stanilovsky Evgeny >Assignee: Vadim Opolski > > class GridLogThrottle stores throttle info into map and noone clears it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160775#comment-16160775
]
Vadim Opolski commented on IGNITE-5979:
---
[~EdShangGG] [~avinogradov] I can not reproduce failing test
GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync.
Also in TC I did not see any failures in last builds.
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158672#comment-16158672
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain], all minor cosmetic changes done.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.3
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-5979:
--
Comment: was deleted
(was: [~EdShangGG] is this test failed actual ? I cant recreate it.)
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16153109#comment-16153109
]
Vadim Opolski commented on IGNITE-5979:
---
[~EdShangGG] is this test failed actual ? I cant recreate it.
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-5979:
-
Assignee: Vadim Opolski
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152677#comment-16152677
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] [~avinogradov] In my opinion tests look good. [TC
#2557|https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll_Ignite20Tests=pull%2F2557%2Fhead=buildTypeStatusDiv]
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.3
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152677#comment-16152677
]
Vadim Opolski edited comment on IGNITE-4756 at 9/4/17 2:51 PM:
---
[~tledkov-gridgain] [~avinogradov] In my opinion tests - [TC
#2557|https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll_Ignite20Tests=pull%2F2557%2Fhead=buildTypeStatusDiv]
look good.
was (Author: javaller):
[~tledkov-gridgain] [~avinogradov] In my opinion tests look good. [TC
#2557|https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_RunAll_Ignite20Tests=pull%2F2557%2Fhead=buildTypeStatusDiv]
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.3
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-5979:
-
Assignee: (was: Vadim Opolski)
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-5979:
-
Assignee: Vadim Opolski
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski resolved IGNITE-4756.
---
Resolution: Fixed
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reopened IGNITE-4756:
---
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4756:
--
Comment: was deleted
(was: [~tledkov-gridgain] [~avinogradov] Changing logging in progress.)
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4756:
--
Comment: was deleted
(was: [~tledkov-gridgain] [~avinogradov] Log4JLogger dependency removed from
core module. Log have been initialize early. I'm working on printing cache
group name in log and calculating statistics only for loacal node. What's the
next step?
)
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4756:
--
Comment: was deleted
(was: [~tledkov-gridgain] [~avinogradov] Added print cache / group name in log
message. Removing calculating statistics to method calculate in progress.)
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4756:
--
Comment: was deleted
(was: [~tledkov-gridgain] [~avinogradov]] Review please -
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-277)
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4756:
--
Comment: was deleted
(was: [~tledkov-gridgain] [~avinogradov] Added local node filtering in
calculating statistics.)
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123379#comment-16123379
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] [~avinogradov]] Review please -
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-277
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087117#comment-16087117
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] [~avinogradov] Added print cache / group name in log
message. Removing calculating statistics to method calculate in progress.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085540#comment-16085540
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] [~avinogradov] Added local node filtering in calculating
statistics.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=3(75%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083691#comment-16083691
]
Vadim Opolski edited comment on IGNITE-4756 at 7/12/17 9:38 AM:
[~tledkov-gridgain] [~avinogradov] Log4JLogger dependency removed from core
module. Log have been initialize early. I'm working on printing cache group
name in log and calculating statistics only for loacal node. What's the next
step?
was (Author: javaller):
[~tledkov-gridgain] [~avinogradov] Log4JLogger dependency removed from core
module. Log have been initialize early. I'm working on printing cache group
name in log and calculating statistics only for loacal node. What the next step?
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=4(100%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16083691#comment-16083691
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] [~avinogradov] Log4JLogger dependency removed from core
module. Log have been initialize early. I'm working on printing cache group
name in log and calculating statistics only for loacal node. What the next step?
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=4(100%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082134#comment-16082134
]
Vadim Opolski commented on IGNITE-4756:
---
Removing Log4JLogger in progress.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=4(100%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082134#comment-16082134
]
Vadim Opolski edited comment on IGNITE-4756 at 7/11/17 12:34 PM:
-
[~tledkov-gridgain] [~avinogradov] Changing logging in progress.
was (Author: javaller):
Removing Log4JLogger in progress.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to print warn message only when nodes count differs more then
> threshold;
> # The statistic is calculated and printed only for the local node;
> # Statistic is placed at the {{GridAffinityAssignmentCache#calculate}} and
> calculated for new {{idealAssignment}}.
> # Message format is
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=,
> expectedPrimary=,
> exectedBackups=,
> primary=, backups=].
> {noformat}
> e.g. for cache with name "test", 2 backups, 4 partition, 3 nodes:
> {noformat}
> Local node affinity assignment distribution is not ideal [cache=test,
> expectedPrimary=1.33 (33.3%), exectedBackups=2.66 (66.66%), primary=1 (25%),
> backups=4(100%)].
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078154#comment-16078154
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] [~avinogradov]
Removed initialization from constructor -
https://github.com/vadopolski/ignite/pull/3/files. Trying to use
IgniteMockWithLocalNode.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Summarize discussions:
> Add log message in case partitions distribution is not close to even
> distribution:
> # Add system property IGNITE_PART_DISTRIBUTION_WARN_THRESHOLD with default
> value 0.1 to
> {noformat}
> : primary, [, ,
> ], ..., [, ,
> ]
> : backup_0, [, ,
> ], ..., [, ,
> ]
> ...
> : backup_N, [, ,
> ], ..., [, ,
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078142#comment-16078142
]
Vadim Opolski commented on IGNITE-3142:
---
[~avinogradov] [~v.pyatkov] I checked the test in Ignite 1.6, there was not
exception. Also I checked the attached project there was exception in Ignite
1.6 and it was not in ignite 2.0. I'm compare test and project to find
differences to recreate exception in Ignite 1.6 in test.
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Fix For: 2.2
>
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845,
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074732#comment-16074732
]
Vadim Opolski commented on IGNITE-4756:
---
[~tledkov-gridgain] Is written log suitable for this issue ?
https://github.com/vadopolski/ignite/pull/3/files
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.2
>
>
> Print information about affinity assignment to log.
> e.g.:
> {noformat}
> : primary, [, ,
> ], ..., [, ,
> ]
> : backup_0, [, ,
> ], ..., [, ,
> ]
> ...
> : backup_N, [, ,
> ], ..., [, ,
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-2049) Add to GridProductVersionSelfTest new tests for new naming strategy
[ https://issues.apache.org/jira/browse/IGNITE-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-2049: - Assignee: Vadim Opolski > Add to GridProductVersionSelfTest new tests for new naming strategy > --- > > Key: IGNITE-2049 > URL: https://issues.apache.org/jira/browse/IGNITE-2049 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Assignee: Vadim Opolski >Priority: Trivial > Labels: newbie > > See > http://apache-ignite-developers.2346864.n4.nabble.com/EA-versioning-td5381.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5580) Improve node failure cause information
[ https://issues.apache.org/jira/browse/IGNITE-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-5580: - Assignee: Vadim Opolski > Improve node failure cause information > -- > > Key: IGNITE-5580 > URL: https://issues.apache.org/jira/browse/IGNITE-5580 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Assignee: Vadim Opolski > Labels: observability > Fix For: 2.1 > > > When a node fails, we do not print out any information about the root cause > of this failure. This makes it extremely hard to investigate the failure > causes - I need to find a previous node for the failed node and check the > logs on the previous node. > I suggest that we add extensive information about the reason of the node > failure and the sequence of events that led to this, e.g.: > [time] [NODE] Sending a message to next node - failed _because_ - write > timeout, read timeout, ...? > [time] [NODE] Connection check - failed - why? Connection refused, handshake > timed out, ...? > ... > [time] [NODE] Decided to drop the node because of the sequence above > Maybe we do not need to print out this information always, but we do need > this when troubleshooting logger is enabled. > Also, DiscoverySpi should collect a set of latest important events and dump > these events in case of local node segmentation. This will allow users to > match the events in the cluster and events on local node and get to the > bottom of the failure. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5561) Warn about long-running cache store operations
[ https://issues.apache.org/jira/browse/IGNITE-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-5561: - Assignee: Vadim Opolski > Warn about long-running cache store operations > -- > > Key: IGNITE-5561 > URL: https://issues.apache.org/jira/browse/IGNITE-5561 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Assignee: Vadim Opolski > Labels: observability > Fix For: 2.1 > > > When a cache store is used, it may become very confusing if a cache store > performs a very long-running operation, because in this case, Ignite would > output a warning about long-running cache operations. I think, in addition to > that, we should measure and output a warning if a specific cache store > operation took too long. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5136) GridLogThrottle memory leak
[ https://issues.apache.org/jira/browse/IGNITE-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-5136: - Assignee: Vadim Opolski > GridLogThrottle memory leak > --- > > Key: IGNITE-5136 > URL: https://issues.apache.org/jira/browse/IGNITE-5136 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Stanilovsky Evgeny >Assignee: Vadim Opolski > > class GridLogThrottle stores throttle info into map and noone clears it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055890#comment-16055890
]
Vadim Opolski edited comment on IGNITE-3142 at 6/20/17 2:59 PM:
[~v.pyatkov] review please https://github.com/apache/ignite/pull/2165/files .
Added attached by you test with adding pause for 10 seconds before restart.
was (Author: javaller):
https://github.com/apache/ignite/pull/2165/files
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Fix For: 2.2
>
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3],
[jira] [Comment Edited] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055877#comment-16055877
]
Vadim Opolski edited comment on IGNITE-3142 at 6/20/17 2:51 PM:
Was discovered that test executed successfully with pause for 10 seconds before
restart.
was (Author: javaller):
Was discovered that test executed successfully with pause for 10 seconds before
restart.
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3], writeVer=null,
> implicit=true, loc=true, threadId=32,
[jira] [Commented] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055877#comment-16055877
]
Vadim Opolski commented on IGNITE-3142:
---
Was discovered that test executed successfully with pause for 10 seconds before
restart.
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3], writeVer=null,
> implicit=true, loc=true, threadId=32, startTime=1463390725843,
> nodeId=df815072-615a-49d4-92e1-2842369ea15a, startVer=GridCacheVersion
> [topVer=74870619, time=1463390725845, order=1463390656380,
[jira] [Commented] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053595#comment-16053595
]
Vadim Opolski commented on IGNITE-3142:
---
[~v.pyatkov] I checked the test and attached project. In both cases it recieves
the event, with ignite version 2.0.0.
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: EventsListenerTest.java, Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3], writeVer=null,
> implicit=true, loc=true, threadId=32, startTime=1463390725843,
> nodeId=df815072-615a-49d4-92e1-2842369ea15a, startVer=GridCacheVersion
> [topVer=74870619, time=1463390725845,
[jira] [Commented] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049233#comment-16049233
]
Vadim Opolski commented on IGNITE-4756:
---
[~yzhdanov] , [~tledkov-gridgain] I cant find information about where to create
log message in correct format. Help please.
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.1
>
>
> Print information about affinity assignment to log.
> e.g.:
> {noformat}
> : primary, [, ,
> ], ..., [, ,
> ]
> : backup_0, [, ,
> ], ..., [, ,
> ]
> ...
> : backup_N, [, ,
> ], ..., [, ,
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048870#comment-16048870
]
Vadim Opolski edited comment on IGNITE-3142 at 6/14/17 8:37 AM:
[~v.pyatkov]
There is not error after manually adding ignite-spring.
I still need help with starting first and second server node and client.
was (Author: javaller):
[~vldpyatkov]
There is not error after manually adding ignite-spring.
I still need help with starting first and second server node and client.
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845,
[jira] [Commented] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048870#comment-16048870
]
Vadim Opolski commented on IGNITE-3142:
---
[~vldpyatkov]
There is not error after manually adding ignite-spring.
I still need help with starting first and second server node and client.
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3], writeVer=null,
> implicit=true, loc=true, threadId=32, startTime=1463390725843,
> nodeId=df815072-615a-49d4-92e1-2842369ea15a, startVer=GridCacheVersion
> [topVer=74870619,
[jira] [Assigned] (IGNITE-3142) When remote filter is set, event is not send, if primary node has left grid.
[
https://issues.apache.org/jira/browse/IGNITE-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-3142:
-
Assignee: Vadim Opolski
> When remote filter is set, event is not send, if primary node has left grid.
>
>
> Key: IGNITE-3142
> URL: https://issues.apache.org/jira/browse/IGNITE-3142
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vadim Opolski
> Attachments: Ignite-Events - Copy.zip
>
>
> If you try to start one server node and another then. After update of
> topology, you can stop the first node and get the exception:
> {noformat}
> [12:25:25] (err) Failed to execute compound future reducer:
> GridNearTxFinishFuture
> [futId=fbe41e8b451-b79beebc-da21-4cfc-a83e-e1cb4b34151b, tx=GridNearTxLocal
> [mappings=IgniteTxMappingsSingleImpl [mapping=GridDistributedTxMapping
> [entries=[IgniteTxEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601, partId=-1,
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], cacheId=-2100569601],
> val=[op=TRANSFORM, val=null], prevVal=[op=NOOP, val=null],
> entryProcessorsCol=[IgniteBiTuple [val1=MetadataProcessor
> [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], nearLocallyMapped=false,
> colocatedLocallyMapped=false, needCheckBackup=false, hasRemoteLocks=false,
> thread=sys-#20%null%, mappings=IgniteTxMappingsSingleImpl
> [mapping=GridDistributedTxMapping [entries=[IgniteTxEntry
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601, partId=-1, txKey=IgniteTxKey
> [key=KeyCacheObjectImpl [val=BinaryMetadataKey [typeId=887264644],
> hasValBytes=true], cacheId=-2100569601], val=[op=TRANSFORM, val=null],
> prevVal=[op=NOOP, val=null], entryProcessorsCol=[IgniteBiTuple
> [val1=MetadataProcessor [newMeta=BinaryMetadata [typeId=887264644,
> typeName=org.jsr166.ConcurrentLinkedDeque8, fields=null,
> affKeyFieldName=null, isEnum=false]], val2=[Ljava.lang.Object;@4807a494]],
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null,
> dhtVer=null, filters=[], filtersPassed=false, filtersSet=true,
> entry=GridDhtDetachedCacheEntry [super=GridDistributedCacheEntry
> [super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=BinaryMetadataKey
> [typeId=887264644], hasValBytes=true], val=null, startVer=1463390656382,
> ver=GridCacheVersion [topVer=74870619, time=1463390725860,
> order=1463390656382, nodeOrder=3], hash=887264644, extras=null, flags=0]]],
> prepared=0, locked=false, nodeId=5f3be800-b89a-419b-8d7e-ba5adbb36fab,
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0,
> partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3]]], explicitLock=false,
> dhtVer=null, last=false, near=false, clientFirst=false,
> node=5f3be800-b89a-419b-8d7e-ba5adbb36fab]], super=GridDhtTxLocalAdapter
> [nearOnOriginatingNode=false, nearNodes=[], dhtNodes=[], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxImplicitSingleStateImpl [init=true],
> super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=74870619,
> time=1463390725845, order=1463390656380, nodeOrder=3], writeVer=null,
> implicit=true, loc=true, threadId=32, startTime=1463390725843,
> nodeId=df815072-615a-49d4-92e1-2842369ea15a, startVer=GridCacheVersion
> [topVer=74870619, time=1463390725845, order=1463390656380, nodeOrder=3],
> endVer=null, isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0,
> sysInvalidate=false, sys=true,
[jira] [Commented] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047903#comment-16047903 ] Vadim Opolski commented on IGNITE-1084: --- I'm wrong > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > Fix For: 2.1 > > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-1084: -- Fix Version/s: (was: 2.0) 2.1 > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > Fix For: 2.1 > > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047872#comment-16047872 ] Vadim Opolski commented on IGNITE-1084: --- Done > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > Fix For: 2.0 > > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski resolved IGNITE-1084. --- > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > Fix For: 2.0 > > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski resolved IGNITE-1084. --- Resolution: Fixed > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski closed IGNITE-1084. - > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4756) Print info about partition distribution to log
[
https://issues.apache.org/jira/browse/IGNITE-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-4756:
-
Assignee: Vadim Opolski
> Print info about partition distribution to log
> ---
>
> Key: IGNITE-4756
> URL: https://issues.apache.org/jira/browse/IGNITE-4756
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Reporter: Taras Ledkov
>Assignee: Vadim Opolski
>Priority: Minor
> Labels: newbie
> Fix For: 2.1
>
>
> Print information about affinity assignment to log.
> e.g.:
> {noformat}
> : primary, [, ,
> ], ..., [, ,
> ]
> : backup_0, [, ,
> ], ..., [, ,
> ]
> ...
> : backup_N, [, ,
> ], ..., [, ,
> ]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE
[
https://issues.apache.org/jira/browse/IGNITE-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-5053:
-
Assignee: (was: Vadim Opolski)
> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
> Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute.
> Final name is yet to be defined. May be we should have several synonyms
> resembling other databases to make migration to Ignite easier.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Hello , Prachi! I reviewed reference. Removing occurrence it was the right action, Thank you! Vadim Opolski > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Prachi Garg >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-5053) Add missing features to H2 parser for CREATE/DROP TABLE
[
https://issues.apache.org/jira/browse/IGNITE-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-5053:
-
Assignee: Vadim Opolski
> Add missing features to H2 parser for CREATE/DROP TABLE
> ---
>
> Key: IGNITE-5053
> URL: https://issues.apache.org/jira/browse/IGNITE-5053
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vadim Opolski
> Labels: important
> Fix For: 2.1
>
>
> We need to {{AFFINITY KEY}} attribute.
> Final name is yet to be defined. May be we should have several synonyms
> resembling other databases to make migration to Ignite easier.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Hello Prachi! I reassigned issue https://issues.apache.org/jira/browse/IGNITE-4052 to you to approve changes of page - https://apacheignite.readme.io/docs/mesos-deployment#section-ignite-mesos-framework Vadim > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Prachi Garg >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-4052: - Assignee: Prachi Garg (was: Vadim Opolski) > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Prachi Garg >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-4447) Remove "Ignite 150 Clients" suite.
[ https://issues.apache.org/jira/browse/IGNITE-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-4447: - Assignee: Vadim Opolski > Remove "Ignite 150 Clients" suite. > -- > > Key: IGNITE-4447 > URL: https://issues.apache.org/jira/browse/IGNITE-4447 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: 1.8 >Reporter: Vladimir Ozerov >Assignee: Vadim Opolski >Priority: Minor > Fix For: 2.1 > > > It has only 1 tests. It runs for ~1m, but takes ~6m including build phase. > Let's just embed it into one of cache suites. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Added screen: https://www.dropbox.com/s/12wywposbhy6p4l/Documentation.docx?dl=0 Vadim > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5206) Test mesos user and mesos role parameters on real mesos cluster.
Vadim Opolski created IGNITE-5206: - Summary: Test mesos user and mesos role parameters on real mesos cluster. Key: IGNITE-5206 URL: https://issues.apache.org/jira/browse/IGNITE-5206 Project: Ignite Issue Type: Task Reporter: Vadim Opolski In current implementation Ignite Mesos Framework connects to MESOS cluster via system env properties (user and role). Need to test this locally, on real mesos cluster. We need to understand which exception user will get if user name and/or role incorrect. Documentation: https://apacheignite.readme.io/docs/mesos-deployment http://mesos.apache.org/gettingstarted/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[
https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4052:
--
Hello guys!
I want to update https://apacheignite.readme.io/docs/mesos-deployment with
new text according with
https://cwiki.apache.org/confluence/display/IGNITE/Documentation
But have a problem with authentication, registered login
vaopols...@gmail.com.
Help me, please.
New text:
3.Copy the following application definition (in JSON format) and save to
marathon.json file. Update any parameters which would like to change.
*A role name must be a valid directory name, so it cannot: • Be an empty
string • Be . or .. • Start with - • Contain any slash, backspace, or
whitespace character*
If doesn't set restriction on cluster then the framework will try to
occupy all resources in Mesos cluster. See Configuration section below.
JSON
{
"id": "ignition",
"instances": 1,
"cpus": 2,
"mem": 2048,
"ports": [0],
"uris": [
"http://host/ignite-mesos--jar-with-dependencies.jar"
],
"env": {
"IGNITE_NODE_COUNT": "4",
"MESOS_MASTER_URL": "zk://localhost:2181/mesos",
"IGNITE_RUN_CPU_PER_NODE": "2",
"IGNITE_MEMORY_PER_NODE": "2048",
"IGNITE_VERSION": "1.0.5",
*"MESOS_USER" : "userA","MESOS_ROLE" : "role1"* },
"cmd": "java -jar ignite-mesos--jar-with-dependencies.jar"
}
Vadim
> Add ability to set up users for MESOS
> -
>
> Key: IGNITE-4052
> URL: https://issues.apache.org/jira/browse/IGNITE-4052
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Vadim Opolski
>Priority: Trivial
>
> In current implementation Ignite Mesos Framework connects to MESOS cluster
> via current user. Need to add ability to configure this parameters via system
> env properties. Also need to add properties for mesos role.
> See org/apache/ignite/mesos/IgniteFramework.java:537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Hi guys! Nikolay, the next improvements are maden ( https://github.com/apache/ignite/pull/1783): - changed code according with code style (extra space, if else blocks, javadoc) - written two tests one which will testing new parametes and other which will testing role validation - used PowerMock framework to getRole getUser testing - ridden #setEnv method I did not test this parameters on real mesos cluster. Nikolay, I dont work with Mesos and think that anyone who has experience should make it. OK? Vadim Opolski > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4760) Hibernate L2 cache stores value in wrong cache
[ https://issues.apache.org/jira/browse/IGNITE-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976799#comment-15976799 ] Vadim Opolski commented on IGNITE-4760: --- https://github.com/apache/ignite/pull/1841 > Hibernate L2 cache stores value in wrong cache > -- > > Key: IGNITE-4760 > URL: https://issues.apache.org/jira/browse/IGNITE-4760 > Project: Ignite > Issue Type: Sub-task > Components: Hibernate L2 cache >Reporter: Semen Boikov >Assignee: Vadim Opolski > Fix For: 2.1 > > > Issue is reported here: > http://apache-ignite-developers.2346864.n4.nabble.com/issue-with-Hibernate-2L-cache-region-factory-ignite-1-8-td14912.html > First it is necessary add JUnit test reproducing issue (see existing tests in > IgniteHibernateTestSuite). > Currently Hibernate access strategies track updates using thread locals, and > it looks like updates for different caches can be mixed. I think per-cache > thread local can fix issue for HibernateNonStrictAccessStrategy, but > per-cache thread local can not be used for HibernateReadWriteAccessStrategy, > since it is assumed that all updates should be part of the same cross-cache > ignite transaction. > So possible fix: > - use per-cache thread local for HibernateNonStrictAccessStrategy (or somehow > track target cache in HibernateNonStrictAccessStrategy) > - use single thread local for HibernateReadWriteAccessStrategy -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976791#comment-15976791 ] Vadim Opolski commented on IGNITE-1084: --- https://github.com/apache/ignite/pull/1841 > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Labels: (was: https://github.com/apache/ignite/pull/1783) > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972274#comment-15972274 ] Vadim Opolski commented on IGNITE-4052: --- The following improvements was maken: 1) Moved framework builder related code to separate method, so it make code cleaner and framework testable. 2) Call framework builder method from test to test role and user. 3) Added validating mesos role according with mesos role documentation http://mesos.apache.org/documentation/latest/roles/ 4) Still using setEnv method because in IgniteFramework we cannot override static method and make mock static methods (except powermock, but it would require 3 extra dependencies in the module). P.S. setEnv method designed to worked both on Linux and Windows, and it does not left variable in system environment after testing. > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-1084) [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken
[ https://issues.apache.org/jira/browse/IGNITE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-1084: - Assignee: Vadim Opolski (was: Milap Wadhwa) > [Test] HibernateL2CacheSelfTest#testNaturalIdCache() is broken > -- > > Key: IGNITE-1084 > URL: https://issues.apache.org/jira/browse/IGNITE-1084 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Sergey Evdokimov >Assignee: Vadim Opolski >Priority: Minor > Labels: Muted_test > > Test HibernateL2CacheSelfTest#testNaturalIdCache() should be unmuted and > fixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[
https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-4052:
--
Hello guys!
Nikolai, I improved method getRole and getUser,
Review please again:
https://github.com/apache/ignite/pull/1783
but what do mean about override ?
Something like this:
public class IgniteFrameworkUnderTest extends IgniteFramework{
...
@Override
public String getUser(){
...
}
@Override
public String getRole(){
...
}
}
Vadim Opolski
> Add ability to set up users for MESOS
> -
>
> Key: IGNITE-4052
> URL: https://issues.apache.org/jira/browse/IGNITE-4052
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Vadim Opolski
>Priority: Trivial
>
> In current implementation Ignite Mesos Framework connects to MESOS cluster
> via current user. Need to add ability to configure this parameters via system
> env properties. Also need to add properties for mesos role.
> See org/apache/ignite/mesos/IgniteFramework.java:537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966414#comment-15966414 ] Vadim Opolski commented on IGNITE-4052: --- https://github.com/apache/ignite/pull/1783 > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-1794:
-
Assignee: Vadim Opolski
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Sub-task
> Components: Hibernate L2 cache
>Reporter: Artem Shutak
>Assignee: Vadim Opolski
> Labels: important, newbie
> Fix For: 2.0
>
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Hello guys! Nikolay, I looked at cassandra mesos integration, but cant find how to test ability to configure mesos and user via system env properties. I will continue to search in another projects which use Mesos. Review please pull request - https://github.com/vadopolski/ignite/pull/2. It contains new test and method for setting system environments. Can you close issue https://issues.apache.org/jira/browse/IGNITE-4052 and open new, about testing Mesos Integration. Vadim Opolski > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4760) Hibernate L2 cache stores value in wrong cache
[ https://issues.apache.org/jira/browse/IGNITE-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963212#comment-15963212 ] Vadim Opolski commented on IGNITE-4760: --- Test check corresponding IgniteCaches contain expected number of entries. Test fails for HibernateNonStrictAccessStrategy. And per-cache thread local in method threadLocalForCache fix this issue. https://github.com/apache/ignite/pull/1768/files > Hibernate L2 cache stores value in wrong cache > -- > > Key: IGNITE-4760 > URL: https://issues.apache.org/jira/browse/IGNITE-4760 > Project: Ignite > Issue Type: Sub-task > Components: Hibernate L2 cache >Reporter: Semen Boikov >Assignee: Vadim Opolski > Fix For: 2.1 > > > Issue is reported here: > http://apache-ignite-developers.2346864.n4.nabble.com/issue-with-Hibernate-2L-cache-region-factory-ignite-1-8-td14912.html > First it is necessary add JUnit test reproducing issue (see existing tests in > IgniteHibernateTestSuite). > Currently Hibernate access strategies track updates using thread locals, and > it looks like updates for different caches can be mixed. I think per-cache > thread local can fix issue for HibernateNonStrictAccessStrategy, but > per-cache thread local can not be used for HibernateReadWriteAccessStrategy, > since it is assumed that all updates should be part of the same cross-cache > ignite transaction. > So possible fix: > - use per-cache thread local for HibernateNonStrictAccessStrategy (or somehow > track target cache in HibernateNonStrictAccessStrategy) > - use single thread local for HibernateReadWriteAccessStrategy -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski updated IGNITE-4052: -- Hello everybody! Nikolay, I didn't have experience with ignite-yarn integration and didn't have idea how fix it, but its interesting for me. Can you write name of another java application, in which I can see how they connect to mesos. Also, can you write how correctly to test working of Builder#setRoleBytes and Builder#setUserBytes without library org.junit.Rule and org.junit.contrib.java.lang.system.EnvironmentVariables. Vadim > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS
[ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946667#comment-15946667 ] Vadim Opolski commented on IGNITE-4052: --- https://github.com/apache/ignite/pull/1662 > Add ability to set up users for MESOS > - > > Key: IGNITE-4052 > URL: https://issues.apache.org/jira/browse/IGNITE-4052 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 1.7 >Reporter: Nikolay Tikhonov >Assignee: Vadim Opolski >Priority: Trivial > > In current implementation Ignite Mesos Framework connects to MESOS cluster > via current user. Need to add ability to configure this parameters via system > env properties. Also need to add properties for mesos role. > See org/apache/ignite/mesos/IgniteFramework.java:537 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (IGNITE-4760) Hibernate L2 cache stores value in wrong cache
[ https://issues.apache.org/jira/browse/IGNITE-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15936214#comment-15936214 ] Vadim Opolski commented on IGNITE-4760: --- https://github.com/apache/ignite/pull/1662 > Hibernate L2 cache stores value in wrong cache > -- > > Key: IGNITE-4760 > URL: https://issues.apache.org/jira/browse/IGNITE-4760 > Project: Ignite > Issue Type: Bug > Components: Hibernate L2 cache >Reporter: Semen Boikov >Assignee: Vadim Opolski > Fix For: 2.0 > > > Issue is reported here: > http://apache-ignite-developers.2346864.n4.nabble.com/issue-with-Hibernate-2L-cache-region-factory-ignite-1-8-td14912.html > First it is necessary add JUnit test reproducing issue (see existing tests in > IgniteHibernateTestSuite). > Currently Hibernate access strategies track updates using thread locals, and > it looks like updates for different caches can be mixed. I think per-cache > thread local can fix issue for HibernateNonStrictAccessStrategy, but > per-cache thread local can not be used for HibernateReadWriteAccessStrategy, > since it is assumed that all updates should be part of the same cross-cache > ignite transaction. > So possible fix: > - use per-cache thread local for HibernateNonStrictAccessStrategy (or somehow > track target cache in HibernateNonStrictAccessStrategy) > - use single thread local for HibernateReadWriteAccessStrategy -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-13) String marshalling can be optimized for binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski updated IGNITE-13:
Component/s: (was: general)
binary
> String marshalling can be optimized for binary marshaller
> -
>
> Key: IGNITE-13
> URL: https://issues.apache.org/jira/browse/IGNITE-13
> Project: Ignite
> Issue Type: Task
> Components: binary
>Reporter: Yakov Zhdanov
>Assignee: Vadim Opolski
>
> Currently string serialization is done in two steps (see
> {{BinaryWriterExImpl#doWriteString}}):
> {code}
> strArr = BinaryUtils.strToUtf8Bytes(val); // Encode string into byte array.
> out.writeByteArray(strArr); // Write byte array into stream.
> {code}
> Probably we can write directly into stream while string is encoded, without
> intermediate array. This both reduces memory consumption and eliminates array
> copy step.
> Need to create a micro benchmark first to check if it gives any improvement.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-13) String marshalling can be optimized for binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904736#comment-15904736
]
Vadim Opolski commented on IGNITE-13:
-
Results of measuring
Benchmark
(message) Mode CntScore
Error Units
LatchBenchmark.binaryHeapOutputStreamDirect
TestTestTestTestTestTestTestTestTest avgt 50 128,036 ± 4,360 ns/op
LatchBenchmark.binaryHeapOutputStreamDirect
TestTestTestavgt 5044,934 ± 1,463 ns/op
LatchBenchmark.binaryHeapOutputStreamDirect
Test avgt 5021,254 ± 0,776 ns/op
LatchBenchmark.binaryHeapOutputStreamInDirect
TestTestTestTestTestTestTestTestTest avgt 5083,262 ± 2,264 ns/op
LatchBenchmark.binaryHeapOutputStreamInDirect
TestTestTest avgt 5058,975 ± 1,559 ns/op
LatchBenchmark.binaryHeapOutputStreamInDirect
Test avgt 5048,506 ± 1,116 ns/op
> String marshalling can be optimized for binary marshaller
> -
>
> Key: IGNITE-13
> URL: https://issues.apache.org/jira/browse/IGNITE-13
> Project: Ignite
> Issue Type: Task
> Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vadim Opolski
>
> Currently string serialization is done in two steps (see
> {{BinaryWriterExImpl#doWriteString}}):
> {code}
> strArr = BinaryUtils.strToUtf8Bytes(val); // Encode string into byte array.
> out.writeByteArray(strArr); // Write byte array into stream.
> {code}
> Probably we can write directly into stream while string is encoded, without
> intermediate array. This both reduces memory consumption and eliminates array
> copy step.
> Need to create a micro benchmark first to check if it gives any improvement.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-13) String marshalling can be optimized for binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904735#comment-15904735
]
Vadim Opolski commented on IGNITE-13:
-
Results of measuring
https://github.com/javaller/mybenchmark/blob/master/out.txt
Benchmark
https://github.com/javaller/mybenchmark/blob/master/src/main/java/org/sample/ExampleTest.java
UTest
https://github.com/javaller/mybenchmark/blob/master/src/main/java/org/sample/BinaryMarshallerSelfTest.java
> String marshalling can be optimized for binary marshaller
> -
>
> Key: IGNITE-13
> URL: https://issues.apache.org/jira/browse/IGNITE-13
> Project: Ignite
> Issue Type: Task
> Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vadim Opolski
>
> Currently string serialization is done in two steps (see
> {{BinaryWriterExImpl#doWriteString}}):
> {code}
> strArr = BinaryUtils.strToUtf8Bytes(val); // Encode string into byte array.
> out.writeByteArray(strArr); // Write byte array into stream.
> {code}
> Probably we can write directly into stream while string is encoded, without
> intermediate array. This both reduces memory consumption and eliminates array
> copy step.
> Need to create a micro benchmark first to check if it gives any improvement.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-1794) Ignite should support Hibernate 5
[
https://issues.apache.org/jira/browse/IGNITE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-1794:
-
Assignee: Vadim Opolski (was: Mykola Pereyma)
> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
> Issue Type: Task
> Components: Hibernate L2 cache
>Reporter: Artem Shutak
>Assignee: Vadim Opolski
> Labels: newbie
> Fix For: 2.0
>
> Attachments: HibernateCollectionRegionForIgnite.java,
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java,
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4.
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws
> CacheException;}}
> Original user list:
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-933) GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically
[ https://issues.apache.org/jira/browse/IGNITE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-933: Assignee: (was: Vadim Opolski) > GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically > > > Key: IGNITE-933 > URL: https://issues.apache.org/jira/browse/IGNITE-933 > Project: Ignite > Issue Type: Bug > Components: general, newbie >Affects Versions: sprint-5 >Reporter: Denis Magda > Labels: newbie > > The timeout for latch (500 millis) seems to be not enough for some machines. > Investigate and fix appropriately. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-933) GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically
[ https://issues.apache.org/jira/browse/IGNITE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-933: Assignee: Vadim Opolski > GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically > > > Key: IGNITE-933 > URL: https://issues.apache.org/jira/browse/IGNITE-933 > Project: Ignite > Issue Type: Bug > Components: general, newbie >Affects Versions: sprint-5 >Reporter: Denis Magda >Assignee: Vadim Opolski > Labels: newbie > > The timeout for latch (500 millis) seems to be not enough for some machines. > Investigate and fix appropriately. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-933) GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically
[ https://issues.apache.org/jira/browse/IGNITE-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-933: Assignee: Vadim Opolski (was: Yakov Zhdanov) > GridFailFastNodeFailureDetectionSelfTest.testFailFast fails periodically > > > Key: IGNITE-933 > URL: https://issues.apache.org/jira/browse/IGNITE-933 > Project: Ignite > Issue Type: Bug > Components: general, newbie >Affects Versions: sprint-5 >Reporter: Denis Magda >Assignee: Vadim Opolski > Labels: newbie > > The timeout for latch (500 millis) seems to be not enough for some machines. > Investigate and fix appropriately. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-13) String marshalling can be optimized for binary marshaller
[
https://issues.apache.org/jira/browse/IGNITE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Opolski reassigned IGNITE-13:
---
Assignee: Vadim Opolski
> String marshalling can be optimized for binary marshaller
> -
>
> Key: IGNITE-13
> URL: https://issues.apache.org/jira/browse/IGNITE-13
> Project: Ignite
> Issue Type: Task
> Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vadim Opolski
>
> Currently string serialization is done in two steps (see
> {{BinaryWriterExImpl#doWriteString}}):
> {code}
> strArr = BinaryUtils.strToUtf8Bytes(val); // Encode string into byte array.
> out.writeByteArray(strArr); // Write byte array into stream.
> {code}
> Probably we can write directly into stream while string is encoded, without
> intermediate array. This both reduces memory consumption and eliminates array
> copy step.
> Need to create a micro benchmark first to check if it gives any improvement.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (IGNITE-13) String marshalling can be optimized for Optimized marshaller
[ https://issues.apache.org/jira/browse/IGNITE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-13: --- Assignee: Vadim Opolski > String marshalling can be optimized for Optimized marshaller > > > Key: IGNITE-13 > URL: https://issues.apache.org/jira/browse/IGNITE-13 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Yakov Zhdanov >Assignee: Vadim Opolski > > Instead of existing logic in readUtf/writeUtf in GridOptimizedMarshaller try > to implement more optimal marshaling when chars are encoded directly to byte > array and unmarshaling when chars are decoded to prepared char array. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (IGNITE-3537) Add tests checking that data structures work inside user transactions
[ https://issues.apache.org/jira/browse/IGNITE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vadim Opolski reassigned IGNITE-3537: - Assignee: Vadim Opolski > Add tests checking that data structures work inside user transactions > - > > Key: IGNITE-3537 > URL: https://issues.apache.org/jira/browse/IGNITE-3537 > Project: Ignite > Issue Type: Task > Components: data structures >Reporter: Semen Boikov >Assignee: Vadim Opolski >Priority: Minor > Labels: newbie > Fix For: 1.9 > > > Need create tests to check that Ignite data structures work inside user > transaction. Now data structures should use independent transactions, test > should jus check that there are no exceptions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
