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

fengchaoge edited comment on SPARK-26570 at 10/14/19 3:00 AM:
--------------------------------------------------------------

hello, [~srowen] [~viirya]

jmap logs is shown below,and filestatus keep rising。

!image-2019-10-14-10-00-27-361.png!

The dump log is too big, I will upload it later

 

!image-2019-10-14-10-32-17-949.png!

!file:///C:/Users/chaogefeng/Documents/WXWork/1688853326421109/Cache/Image/2019-10/e3bd43f7df20a95aab7094e9a1dc0094.jpg!


was (Author: fengchaoge):
hello, [~srowen] [~viirya]

jmap logs is shown below:

!image-2019-10-14-10-00-27-361.png!

The dump log is too big, I will upload it later

 

!image-2019-10-14-10-32-17-949.png!

!file:///C:/Users/chaogefeng/Documents/WXWork/1688853326421109/Cache/Image/2019-10/e3bd43f7df20a95aab7094e9a1dc0094.jpg!

> Out of memory when InMemoryFileIndex bulkListLeafFiles
> ------------------------------------------------------
>
>                 Key: SPARK-26570
>                 URL: https://issues.apache.org/jira/browse/SPARK-26570
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.3.2
>            Reporter: deshanxiao
>            Priority: Major
>         Attachments: image-2019-10-13-18-41-22-090.png, 
> image-2019-10-13-18-45-33-770.png, image-2019-10-14-10-00-27-361.png, 
> image-2019-10-14-10-32-17-949.png, image-2019-10-14-10-47-47-684.png, 
> image-2019-10-14-10-50-47-567.png, image-2019-10-14-10-51-28-374.png, 
> screenshot-1.png
>
>
> The *bulkListLeafFiles* will collect all filestatus in memory for every query 
> which may cause the oom of driver. I use the spark 2.3.2 meeting with the 
> problem. Maybe the latest one also exists the problem.



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

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

Reply via email to