[jira] [Commented] (IGNITE-13818) Add extended logging topology for node start

2021-01-01 Thread Maria Makedonskaya (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17257289#comment-17257289
 ] 

Maria Makedonskaya commented on IGNITE-13818:
-

[~sk0x50], could you please review changes?

> Add extended logging topology for node start
> 
>
> Key: IGNITE-13818
> URL: https://issues.apache.org/jira/browse/IGNITE-13818
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> At start of the node write topology - the number of server and client nodes, 
> I would like to expand the list of nodes (information about each node: order, 
> id, host, ip), this will help in the case when the logs are only from one 
> node, and when there are logs from all nodes it will speed up the search for 
> coordinator or find the problem node id which was in the transaction



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13818) Add extended logging topology for node start

2021-01-01 Thread Ignite TC Bot (Jira) 


[ 
https://issues.apache.org/jira/browse/IGNITE-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17257288#comment-17257288
 ] 

Ignite TC Bot commented on IGNITE-13818:


{panel:title=Branch: [pull/8559/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8559/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5814780buildTypeId=IgniteTests24Java8_RunAll]

> Add extended logging topology for node start
> 
>
> Key: IGNITE-13818
> URL: https://issues.apache.org/jira/browse/IGNITE-13818
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> At start of the node write topology - the number of server and client nodes, 
> I would like to expand the list of nodes (information about each node: order, 
> id, host, ip), this will help in the case when the logs are only from one 
> node, and when there are logs from all nodes it will speed up the search for 
> coordinator or find the problem node id which was in the transaction



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13949) Insufficient synchronisation in PartitionUpdateCounterTrackingImpl

2021-01-01 Thread Yaroslav Molochkov (Jira) 
Yaroslav Molochkov created IGNITE-13949:
---

 Summary: Insufficient synchronisation in 
PartitionUpdateCounterTrackingImpl
 Key: IGNITE-13949
 URL: https://issues.apache.org/jira/browse/IGNITE-13949
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Yaroslav Molochkov
Assignee: Yaroslav Molochkov


Right now 
org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl 
has 2 AtomicLong variables, cntr and reserveCntr, but there are some methods, 
that are unsynchronised, e.g. next:
{code:java}
@Override public long next() {
long next = cntr.incrementAndGet();

reserveCntr.set(next);

return next;
} {code}

Even though both are AtomicLong, operation like "get then set" is a composite 
one and should be atomic in the context of an object that holds these variables.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)