[jira] [Created] (IGNITE-13316) The left join table's index is not used in Ignite SQL execution

2020-07-30 Thread Xie Bo (Jira) 
Xie Bo created IGNITE-13316:
---

 Summary: The left join table's index is not used in Ignite SQL 
execution
 Key: IGNITE-13316
 URL: https://issues.apache.org/jira/browse/IGNITE-13316
 Project: Ignite
  Issue Type: Improvement
  Components: springdata
Affects Versions: 2.8.1
Reporter: Xie Bo


 

SELECT * FROM issue LEFT JOIN issue_fixed_version ver ON issue.id=ver.id WHERE 
*issue.id in (select distinct id from issue_fixed_version where fixed_version = 
'4.15')*;
 12 rows selected (*0.062 seconds*)
 
 SELECT * FROM issue LEFT JOIN issue_fixed_version ver ON issue.id=ver.id WHERE 
*ver.FIXED_VERSION = '4.15'*;
 12 rows selected (*2.015 second*s)



Note: 'issue' is a table with over a million rows and 'issue_fixed_version' is 
another table with much less rows. There is an index on 'FIXED_VERSION' column 
in 'issue_fixed_version' table.

The above 2 SQLs do the same thing but have different performance. The first 
SQL's explain plan shows that the index (on 'FIXED_VERSION' column in 
'issue_fixed_version' table) is used and then its performance is good; the 
second SQL's explain plan shows that the index (on 'FIXED_VERSION' column in 
'issue_fixed_version' table) is not used, why? Any way to force the second SQL 
to use the index (on 'FIXED_VERSION' column in 'issue_fixed_version' table)?



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

Re: Re[2]: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

2020-07-30 Thread Ilya Kasnacheev 
Hello!

I don't think that IGNITE-13006
 is a blocker in any
way. It is a good candidate for 3.0.

ignite-spring will work with 4.x Spring as well as 5.x and the user is free
to bump Spring version. I think bumping this dependency explicitly is
infeasible since it may break existing code.

Regards,
-- 
Ilya Kasnacheev


ср, 22 июл. 2020 г. в 10:22, Alex Plehanov :

> Guys,
>
> We are in code-freeze phase now. I've moved almost all non-blocker
> unresolved tickets from 2.9 to the next release. If you think that
> some ticket is a blocker and should be included into 2.9 release, please
> write a note in this thread.
>
> There are some tickets with "blocker" priority targeted to 2.9, some of
> them in "open" state and still unassigned, and I'm not sure we need all of
> these tickets in 2.9:
>
> IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to
> spring 5.2 version or later) - Is it really a blocker for 2.9 release? If
> yes, can somebody help with resolving this ticket?
>
> IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket in
> "Patch available" state. There is a thread on dev-list related to this
> ticket ([6]), but as far as I understand we still don't have consensus
> about version for this patch (2.9, 2.10, 3.0).
>
> IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) -
> perhaps issue is already resolved by some related tickets, there is still
> no reproducer, no additional details and no work in progress. I propose to
> move this ticket to the next release.
>
> IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted
> from a BinaryObject value object --- and SQL enabled) - ticket in "Patch
> available" state, but there is no activity since May 2020. Anton
> Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is it
> still in progress?
>
> IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new metrics
> framework is already released in 2.8 and it's still marked with
> @IgniteExperemental annotation, I think this ticket is not a blocker. I
> propose to change the ticket priority and move it to the next release.
>
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-13006
> [2]: https://issues.apache.org/jira/browse/IGNITE-11942
> [3]: https://issues.apache.org/jira/browse/IGNITE-12489
> [4]: https://issues.apache.org/jira/browse/IGNITE-12911
> [5]: https://issues.apache.org/jira/browse/IGNITE-12553
> [6]:
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
>
> пт, 17 июл. 2020 г. в 11:50, Alex Plehanov :
>
>> Ivan,
>>
>> Merged to 2.9.
>>
>> Thanks
>>
>> пт, 17 июл. 2020 г. в 01:35, Ivan Rakov :
>>
>>> Alex,
>>>
>>> Tracing is merged to master:
>>> https://issues.apache.org/jira/browse/IGNITE-13060
>>>
>>> Can you please port it to 2.9?
>>> For you convenience, there's PR versus 2.9 with conflicts resolved:
>>> https://github.com/apache/ignite/pull/8046/files
>>>
>>> --
>>> Best Regards,
>>> Ivan Rakov
>>>
>>> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov 
>>> wrote:
>>>
 Ivan,

 Looks like master is broken after IGNITE-13246 (but everything is ok in
 2.9
 branch)

 ср, 15 июл. 2020 г. в 18:54, Alex Plehanov :

 > Zhenya, Ivan,
 >
 > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch.
 > Thank you.
 >
 > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov :
 >
 >> Guys,
 >>
 >> can you please backport
 >> https://issues.apache.org/jira/browse/IGNITE-13246
 >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events
 in
 >> release.
 >>
 >> This time I prepared PR with resolved conflicts:
 >> https://github.com/apache/ignite/pull/8042
 >>
 >> Thank you!
 >>
 >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky
 >> >>> >> >:
 >>
 >> >
 >> >
 >> >
 >> > Alex, i also suggest to merge this
 >> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient
 >> > leakage and further TC OOM preventing.
 >> >
 >> > >Ivan,
 >> > >
 >> > >It was already in release scope as discussed in this thread.
 >> > >
 >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com
 >:
 >> > >
 >> > >> Hi,
 >> > >>
 >> > >> We are still waiting for a final review of Tracing
 functionality [1]
 >> > until
 >> > >> the end of tomorrow (July 15).
 >> > >> We anticipate that it will be merged to Ignite master no later
 than
 >> July
 >> > >> 16.
 >> > >>
 >> > >> Sorry for being a bit late here. Alex P., can you include [1]
 to the
 >> > >> release scope?
 >> > >>
 >> > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-13060
 >> > >>
 >> > >> --
 >> > >> Best Regards,
 >> > >> Ivan Rakov
 >> > >>

[jira] [Created] (IGNITE-13315) Uninformative TxDumpsThrottling toString output.

2020-07-30 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-13315:


 Summary: Uninformative TxDumpsThrottling toString output.
 Key: IGNITE-13315
 URL: https://issues.apache.org/jira/browse/IGNITE-13315
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.8.1
Reporter: Konstantin Sirotkin
Assignee: Konstantin Sirotkin


looks like e need additional @GridToStringExclude for:
GridNearTxLocal#txDumpsThrottling

{noformat} 

2020-07-27 18:38:06.983[WARN 
][exchange-worker-#155%DPL_GRID%DplGridNodeName%][o.apache.ignite.internal.diagnostic]
 >>> [txVer=null, exchWait=false, tx=GridNearTxLocal 
[mappings=IgniteTxMappingsSingleImpl [mapping=null], nearLocallyMapped=false, 
colocatedLocallyMapped=false, needCheckBackup=null, hasRemoteLocks=false, 
trackTimeout=false, systemTime=0, systemStartTime=0, prepareStartTime=0, 
prepareTime=0, commitOrRollbackStartTime=0, commitOrRollbackTime=0, 
*txDumpsThrottling=o.a.i.i.processors.cache.transactions.IgniteTxManager$TxDumpsThrottling@66ede293*,
 lb=null, thread=, 
mappings=IgniteTxMappingsSingleImpl [mapping=null], super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView [], 
explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null, 
sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=false, recovery=false], 
super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=206004504, 
order=1595859218447, nodeOrder=1], writeVer=null, implicit=true, loc=true, 
threadId=997408, startTime=1595863641166, 
nodeId=1227c1de-f539-47ef-baef-5d04e259d590, startVer=GridCacheVersion 
[topVer=206004504, order=1595859218447, nodeOrder=1], endVer=null, 
isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
sysInvalidate=false, sys=true, plc=5, commitVer=null, finalizing=NONE, 
invalidParts=null, state=ACTIVE, timedOut=false, topVer=AffinityTopologyVersion 
[topVer=-1, minorTopVer=0], skipCompletedVers=false, duration=645816ms, 
onePhaseCommit=false], size=0

{noformat}



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

[jira] [Created] (IGNITE-13314) Tasks from GridClient.compute() are processed with wrong SecurityContext

2020-07-30 Thread Ryabov Dmitrii (Jira) 
Ryabov Dmitrii created IGNITE-13314:
---

 Summary: Tasks from GridClient.compute() are processed with wrong 
SecurityContext
 Key: IGNITE-13314
 URL: https://issues.apache.org/jira/browse/IGNITE-13314
 Project: Ignite
  Issue Type: Task
Reporter: Ryabov Dmitrii
 Attachments: ComputeTaskRemoteSecurityContextCheckGridClientTest.java

Currently, tasks started from {{GridClient.compute()}} are processed with 
server node's security context. 

Example attached.



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

[jira] [Created] (IGNITE-13313) IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node startup

2020-07-30 Thread Grigory Domozhirov (Jira) 
Grigory Domozhirov created IGNITE-13313:
---

 Summary: IndexOutOfBoundsException from GridDhtAtomicUpdateRequest 
on server node startup
 Key: IGNITE-13313
 URL: https://issues.apache.org/jira/browse/IGNITE-13313
 Project: Ignite
  Issue Type: Bug
Reporter: Grigory Domozhirov


Sometimes server node fails on startup with following exception.

GGCE 8.7.21, no persistance, atomic caches

 
2020-07-30 13:39:02,962 [sys-stripe-0-#1] ERROR o.a.i.i.p.c.GridCacheIoManager 
- Failed processing message [senderId=98dc3c18-ea57-4805-9603-b92eb7e62be2, 
msg=GridD
htAtomicUpdateRequest [keys=ArrayList 
[com.moex.esb.blackhole.model.fx.trade.Securities$Key [idHash=4701836, 
hash=890931906, secboard=AETS, seccode=GLDRUB_TOD],
*__*
... and 111883 skipped ...=0,_**_
 prevVals=ArrayList [null, null, null, null, null, null, null, null, null, 
null, null, null, null, null, null, null, null, null, null, null, null, null, 
null, null,
 null, null, null, null, null, null, null, null, null, null, null, null, null, 
null, null, null, null, null, null, null, null, null, null, null, null, null, 
null, n
ull, null, null, null, null, null, null, null, null, null, null, null, null, 
null, null, null, null, null, null, null, null, null, null, null, null, null, 
null, nul
l, null, null, null, null, null, null, null, null, null, null, null, null, 
null, null, null, null, null, null, null, null, null... and 19 more], 
ttls=null, conflict
ExpireTimes=null, nearTtls=null, nearExpireTimes=null, nearKeys=null, 
nearVals=null, obsoleteIndexes=null, forceTransformBackups=false, 
updateCntrs=GridLongList [id
x=174, 
arr=[1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,
1,2,1,1,1,1,1,1,3,1,1,1,1,1,1,1,1,1,2,2,1,1,1,1,2,1,1,3,1,1,1,1,1,2,1,2,1,1,1,1,2,1,1,1,2,1,2,1,2,1,1,1,2,1,2,2,1,4,1,3,3,1,2,2,2,2,1,3,1,1,1,1,1,2,3,4,1,1,2,1,1,1,
1,4,1,1,1,2,1,2,1,1,1,1,3,1,1,1]], super=GridDhtAtomicAbstractUpdateRequest 
[onRes=false, nearNodeId=ae4abad0-d501-4703-98bf-b5eabd10f159, 
nearFutId=147459, flags=k
eepBinary|hasRes]]]
java.lang.IndexOutOfBoundsException: Index 119 out of bounds for length 119
        at 
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) 
~[na:na]
        at 
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
 ~[na:na]
        at 
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) 
~[na:na]
        at java.base/java.util.Objects.checkIndex(Objects.java:373) ~[na:na]
        at java.base/java.util.ArrayList.get(ArrayList.java:425) ~[na:na]
        at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest.previousValue(GridDhtAtomicUpdateRequest.java:391)
 ~[ignite
-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3363)
 ~[ignit
e-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:141)
 ~[ignite-core-8.7.21.jar:8.
7.21]
        at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:311)
 ~[ignite-core-8.7.21.jar:8.7.2
1]
        at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:306)
 ~[ignite-core-8.7.21.jar:8.7.2
1]
        at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1711)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1331)
 ~[ignite-core-8.7.21.jar:8.7.21]
        at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4800(GridIoManager.java:153)

[jira] [Created] (IGNITE-13312) Methods of interface Binarylizable should not get accessing to host resources.

2020-07-30 Thread Denis Garus (Jira) 
Denis Garus created IGNITE-13312:


 Summary: Methods of interface Binarylizable should not get 
accessing to host resources.
 Key: IGNITE-13312
 URL: https://issues.apache.org/jira/browse/IGNITE-13312
 Project: Ignite
  Issue Type: Task
  Components: security
Reporter: Denis Garus


Methods of interface Binarylizable should not get accessing to host resources 
on a remote nodes.



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

Re: [MTCGA]: new failures in builds [5496180, 5496178] needs to be handled

2020-07-30 Thread Ivan Pavlukhin 
Anton Kalashnikov, Alexey Goncharuk,

The failures look related to a following commit
https://github.com/apache/ignite/commit/1b9fe33740c31b6947016230ef50ae5bce88bad2

Is someone working on fix?

2020-07-29 22:14 GMT+03:00, dpavlov.ta...@gmail.com :
> Hi Igniters,
>
>  I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
>  If your changes can lead to this failure(s): We're grateful that you were a
> volunteer to make the contribution to this project, but things change and
> you may no longer be able to finalize your contribution.
>  Could you respond to this email and indicate if you wish to continue and
> fix test failures or step down and some committer may revert you commit.
>
>  *New Critical Failure in master-nightly Hadoop
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Hadoop?branch=%3Cdefault%3E
>  Changes may lead to failure were done by
>- ivan daschinskiy 
> https://ci.ignite.apache.org/viewModification.html?modId=905071
>- slava koptilin 
> https://ci.ignite.apache.org/viewModification.html?modId=905065
>- ibessonov 
> https://ci.ignite.apache.org/viewModification.html?modId=905067
>- anton kalashnikov 
> https://ci.ignite.apache.org/viewModification.html?modId=905066
>- aleksey plekhanov 
> https://ci.ignite.apache.org/viewModification.html?modId=905057
>
>  *New Critical Failure in master-nightly IGFS (Linux and MacOS)
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_IgfsLinuxAndMacOS?branch=%3Cdefault%3E
>  Changes may lead to failure were done by
>- ivan daschinskiy 
> https://ci.ignite.apache.org/viewModification.html?modId=905071
>- slava koptilin 
> https://ci.ignite.apache.org/viewModification.html?modId=905065
>- ibessonov 
> https://ci.ignite.apache.org/viewModification.html?modId=905067
>- anton kalashnikov 
> https://ci.ignite.apache.org/viewModification.html?modId=905066
>- aleksey plekhanov 
> https://ci.ignite.apache.org/viewModification.html?modId=905057
>
>- Here's a reminder of what contributors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>- Should you have any questions please contact dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 22:14:21 29-07-2020
>


-- 

Best regards,
Ivan Pavlukhin

Re: Removal of "default" cache from REST APIs

2020-07-30 Thread Ilya Kasnacheev 
Hello!

It is only available for example node startup shipped with our examples.

However, it is not available when you just start a node from a downloaded
distribution.

I concur that we should no longer rely on "default" cache.

Regards,
-- 
Ilya Kasnacheev


ср, 22 июл. 2020 г. в 03:09, Saikat Maitra :

> Hi Evgeniy,
>
> Can you please confirm in your configuration you have this example config
> file.
>
>
> https://github.com/apache/ignite/blob/master/examples/config/example-cache.xml#L26-L32
>
> This has instructions on default cache config.
>
> My understanding is when node startup then the default cache should already
> be available.
>
> Regards
> Saikat
>
> On Sun, Jul 19, 2020 at 11:21 PM Evgeniy Rudenko 
> wrote:
>
> > Hi Saikat,
> >
> > I understand this, but as I wrote this is pointless. It is not safe
> > fallback, because there is no "default" cache. If you will try to use any
> > API without a name you will receive the following error:
> >
> > *org.apache.ignite.IgniteCheckedException: Failed to find cache for given
> > cache name: default*
> >
> > Better to replace it by the correctly formed error message that will
> point
> > to the actual problem of the request. API documents will be updated
> > accordingly when PR will be merged.
> >
> > On Sun, Jul 19, 2020 at 12:56 AM Saikat Maitra 
> > wrote:
> >
> > > Hi Evgeniy,
> > >
> > > The default cacheName is safe fallback when cache name is not provided
> in
> > > the request. It is part of rest document.
> > >
> > > https://apacheignite.readme.io/docs/rest-api#put
> > >
> > > When request do not have cacheName since it is optional param then this
> > > DFLT_CACHE_NAME is used
> > >
> > >
> >
> https://github.com/apache/ignite/pull/8041/files#diff-a3477d5e0cfdfcceed3371fc899a9d15L30
> > >
> > > Regards,
> > > Saikat
> > >
> > > On Wed, Jul 15, 2020 at 10:43 PM Evgeniy Rudenko <
> e.a.rude...@gmail.com>
> > > wrote:
> > >
> > > > Hi guys,
> > > >
> > > > Most of the cache APIs are trying to use "default" cache when
> cacheName
> > > is
> > > > not provided. This is pointless, because we don't have such cache by
> > > > default. I would like to change that and just return "Failed to find
> > > > mandatory parameter in request" error if name is absent.
> > > >
> > > > Please tell if you have any concerns. Update can be found at
> > > > https://github.com/apache/ignite/pull/8041
> > > >
> > > > --
> > > > Best regards,
> > > > Evgeniy
> > > >
> > >
> >
> >
> > --
> > Best regards,
> > Evgeniy
> >
>

[jira] [Created] (IGNITE-13311) Put operation may hang if the cache is reconnected

2020-07-30 Thread ff zhou (Jira) 
ff zhou created IGNITE-13311:


 Summary: Put operation may hang if the cache is reconnected
 Key: IGNITE-13311
 URL: https://issues.apache.org/jira/browse/IGNITE-13311
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.8.1
 Environment: # Single-node client (fat node)
 # single-node server
 # use replicated persistence mode
Reporter: ff zhou


Problem description: 
1. Single-node client (fat node), single-node server, and use replicated 
persistence mode 
2) Run the client program and perform the put operation. 
3) Kill the server process. 
4) The client captures the IgniteClientDisconnectedException exception and 
invokes cause.reconnectFuture().get(); to wait for reconnection. 
5) Start the server process. 
6) After the execution（cause.reconnectFuture().get()）is completed, perform the 
put operation immediately. The put operation is hung on the checkProxyIsValid 
interface.

7）if i performed sleep operation after reconnectFuture.get() is completed，then 
do the put operation, it will not hang.（This is a temporary workaround.）

 

hang stack:

"mq-topic-11-3-4" #253 prio=5 os_prio=0 tid=0x7fa70275e000 nid=0x2abb 
waiting on condition [0x7fa4ad29a000]"mq-topic-11-3-4" #253 prio=5 
os_prio=0 tid=0x7fa70275e000 nid=0x2abb waiting on condition 
[0x7fa4ad29a000]   java.lang.Thread.State: WAITING (parking) at 
sun.misc.Unsafe.park(Native Method) at 
java.util.concurrent.locks.LockSupport.park(LockSupport.java:304) at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
 at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4417)
 at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:4388)
 at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.checkProxyIsValid(GatewayProtectedCacheProxy.java:1602)
 at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1619)
 at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:853)
 at 
com.huawei.donau.master.common.repository.storage.cache.impl.ignite.EventCacheDaoIgniteImpl.insertEvent(EventCacheDaoIgniteImpl.java:105)
 at 
com.huawei.donau.master.core.repository.service.EventService.addEvent(EventService.java:28)
 at 
com.huawei.donau.master.core.jobmanager.task.DonauTask.addEvent(DonauTask.java:234)
 at 
com.huawei.donau.master.core.jobmanager.task.TaskManager.recordTaskStateChangeEvent(TaskManager.java:1290)
 at 
com.huawei.donau.master.core.jobmanager.task.TaskManager.recordAndPersistStateChange(TaskManager.java:986)
 at 
com.huawei.donau.master.core.jobmanager.task.TaskManager.onTaskStateChange(TaskManager.java:941)
 at 
com.huawei.donau.master.core.jobmanager.task.TaskManager.onTaskUpdate(TaskManager.java:333)
 at 
com.huawei.donau.master.core.jobmanager.task.TaskManager.handleTaskUpdateMessage(TaskManager.java:251)
 at 
com.huawei.donau.master.core.jobmanager.task.TaskManager$$Lambda$536/577636327.onReceive(Unknown
 Source) at 
com.huawei.donau.common.mq.ConsumerClient$ConsumerThread.run(ConsumerClient.java:141)
   Locked ownable synchronizers: - None

 

client debug log:

Jul 27, 2020 2:39:05 PM org.apache.ignite.logger.java.JavaLogger infoJul 27, 
2020 2:39:05 PM org.apache.ignite.logger.java.JavaLogger infoINFO: Router node: 
TcpDiscoveryNode [id=98a557e1-0638-486d-8939-4e09ce32726a, 
consistentId=8c821ac6-4bf2-4426-8098-e182f31fd168, addrs=ArrayList 
[0:0:0:0:0:0:0:1%lo, 10.29.88.134, 127.0.0.1, 192.168.122.1], sockAddrs=HashSet 
[/192.168.122.1:47500, hghphicprd08301/10.29.88.134:47500, 
/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=1, 
intOrder=1, lastExchangeTime=1595831945590, loc=false, 
ver=2.8.1#20200521-sha1:86422096, isClient=false]Jul 27, 2020 2:39:05 PM 
org.apache.ignite.logger.java.JavaLogger infoINFO: Stopped cache 
[cacheName=ignite-sys-cache]Jul 27, 2020 2:39:05 PM 
org.apache.ignite.logger.java.JavaLogger infoINFO: Assigned mvcc coordinator 
[crd=MvccCoordinator [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], 
nodeId=98a557e1-0638-486d-8939-4e09ce32726a, ver=1595831945461, local=false, 
initialized=false]]Jul 27, 2020 2:39:05 PM 
org.apache.ignite.logger.java.JavaLogger infoINFO: Stopped cache 
[cacheName=t_migration_jobid]Jul 27, 2020 2:39:05 PM 
org.apache.ignite.logger.java.JavaLogger warningWARNING: Client node was 
reconnected after it was already considered failed by the server topology (this 
could happen after all servers restarted or due to a long network outage 
between the client and servers). All continuous queries and remote event 
listeners created by this client will

[jira] [Created] (IGNITE-13310) Add SQL tracing.

2020-07-30 Thread Mikhail Petrov (Jira) 
Mikhail Petrov created IGNITE-13310:
---

 Summary: Add SQL tracing.
 Key: IGNITE-13310
 URL: https://issues.apache.org/jira/browse/IGNITE-13310
 Project: Ignite
  Issue Type: Improvement
Reporter: Mikhail Petrov
 Fix For: 2.10


It's needed to add SQL tracing  based on the tracing framework that was added 
as part of the [IGNITE-13060|https://issues.apache.org/jira/browse/IGNITE-13060]



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