[jira] [Commented] (ATLAS-855) Atlas logs contain stale transaction eviction message

["Hemanth Yamijala (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312610#comment-15312610 ] 

Hemanth Yamijala commented on ATLAS-855:
----------------------------------------

One recent case when I got it, I performed the following operations:

* Created a taxonomy via REST client
* Created 5 terms one after the other and one under the other (t1.t2.t3.t4.t5) from the UI
* Browsed the terms a bit from the UI.
* Created another 4-5 terms from the taxonomy root. (d1.d2.d3..)
* Deleted t1
* Deleted d1.d2.d3.d4.d5
* Deleted d1.d2.d3.

Checking in the logs, there were about 5 cache eviction messages. There is no guarantee repeating these steps will give the problem for sure.

Will try and attach logs for this case.

> Atlas logs contain stale transaction eviction message
> -----------------------------------------------------
>
>                 Key: ATLAS-855
>                 URL: https://issues.apache.org/jira/browse/ATLAS-855
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.7-incubating
>            Reporter: Hemanth Yamijala
>            Priority: Critical
>             Fix For: 0.7-incubating
>
>
> In situations that are hard to replicate, we are getting a message in the Atlas server logs as follows:
> {code}
> Evicted [16@c0a801069313-hemanthijalambp-home1] from cache but waiting too long for transactions to close. Stale transaction alert on: [standardtitantx[null]] (ManagementLogger:189)
> {code}
> I started seeing this a lot more often with the business catalog delete functionality (ATLAS-793), although it is not consistent with this.
> This jira is to track down the cause and fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)