Re: I want to contribute to Apache Ignite

2019-01-12 Thread Dmitriy Pavlov 
Hi Andrey,

Welcome to Apache Ignite Community.

I've added you to the list of contributors, so now you can assign issues to
yourself.

Sincerely,
Dmitriy Pavlov

P.S. Let me share with you
Short 'How to start' guide
https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite

and full guide version
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute


сб, 12 янв. 2019 г. в 21:04, Андрей Калинин :

> Hello Ignite Community!
>
> My name is Andrey. I want to contribute to Apache Ignite and want to start
> with this issue - IGNITE-10138, my JIRA username "6uest".
>
> Thanks!
>
> --
> C уважением,
> Андрей Калинин
>

I want to contribute to Apache Ignite

2019-01-12 Thread Андрей Калинин 
Hello Ignite Community!

My name is Andrey. I want to contribute to Apache Ignite and want to start
with this issue - IGNITE-10138, my JIRA username "6uest".

Thanks!

-- 
C уважением,
Андрей Калинин

[jira] [Created] (IGNITE-10910) GridTaskProcessor#onKernalStop may lead to a deadlock and execution timeout in "SPI" TC build-plan

2019-01-12 Thread Vyacheslav Daradur (JIRA) 
Vyacheslav Daradur created IGNITE-10910:
---

 Summary: GridTaskProcessor#onKernalStop may lead to a deadlock and 
execution timeout in "SPI" TC build-plan
 Key: IGNITE-10910
 URL: https://issues.apache.org/jira/browse/IGNITE-10910
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.7
Reporter: Vyacheslav Daradur
 Fix For: 2.8


In rare cases calling of {{GridTaskProcessor#onKernalStop}} may lead to a 
deadlock with the following stack trace:
{code:java}
"node-stopper" #225287 prio=5 os_prio=0 tid=0x7f224057a800 nid=0x233aae 
waiting on condition [0x7f24607ef000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at 
org.apache.ignite.internal.util.GridSpinReadWriteLock.tryWriteLock(GridSpinReadWriteLock.java:347)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.onKernalStop(GridTaskProcessor.java:198)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2305)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2253)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2614)
- locked <0x9f42a970> (a 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2577)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
at 
org.apache.ignite.failure.StopNodeFailureHandler$1.run(StopNodeFailureHandler.java:36)
at java.lang.Thread.run(Thread.java:748)
{code}
It's the cause of execution timeout of "SPI" build-plan on TC:
 [https://ci.ignite.apache.org/viewLog.html?buildId=2698887]
 [https://ci.ignite.apache.org/viewLog.html?buildId=2689621]
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)