[ 
https://issues.apache.org/jira/browse/SPARK-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Owen resolved SPARK-18238.
-------------------------------
    Resolution: Not A Problem

> WARN Executor: 1 block locks were not released by TID
> -----------------------------------------------------
>
>                 Key: SPARK-18238
>                 URL: https://issues.apache.org/jira/browse/SPARK-18238
>             Project: Spark
>          Issue Type: Bug
>         Environment: 2.0.2 snapshot
>            Reporter: Harish
>            Priority: Minor
>              Labels: patch
>
> In spark 2.0.2/hadoop 2.7, i am getting below message. Not sure is this 
> impacting my execution.
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30541:
> [rdd_511_104]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30542:
> [rdd_511_105]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30562:
> [rdd_511_127]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30571:
> [rdd_511_137]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30572:
> [rdd_511_138]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30588:
> [rdd_511_156]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30603:
> [rdd_511_171]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30600:
> [rdd_511_168]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30612:
> [rdd_511_180]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30622:
> [rdd_511_190]
> 16/11/03 01:10:23 WARN Executor: 1 block locks were not released by TID = 
> 30629:
> [rdd_511_197]



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to