[jira] [Commented] (SPARK-24558) Driver prints the wrong info in the log when the executor which holds cacheBlock is IDLE.Time-out value displayed is not as per configuration value.
[ https://issues.apache.org/jira/browse/SPARK-24558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512301#comment-16512301 ] Apache Spark commented on SPARK-24558: -- User 'sandeep-katta' has created a pull request for this issue: https://github.com/apache/spark/pull/21565 > Driver prints the wrong info in the log when the executor which holds > cacheBlock is IDLE.Time-out value displayed is not as per configuration value. > > > Key: SPARK-24558 > URL: https://issues.apache.org/jira/browse/SPARK-24558 > Project: Spark > Issue Type: Improvement > Components: Spark Core >Affects Versions: 2.3.1 >Reporter: sandeep katta >Priority: Minor > > > launch spark-sql > spark-sql>cache table sample; > 2018-05-15 14:02:28 INFO ExecutorAllocationManager:54 - New executor 2 has > registered (new total is 1) > 2018-05-15 14:02:28 INFO TaskSetManager:54 - Starting task 0.0 in stage 0.0 > (TID 0, vm3, executor 2, partition 0, NODE_LOCAL, 7956 bytes) > 2018-05-15 14:02:28 INFO BlockManagerMasterEndpoint:54 - Registering block > manager vm3:53439 with 93.3 MB RAM, BlockManagerId(2, vm3, 53439, None) > 2018-05-15 14:02:28 INFO BlockManagerInfo:54 - Added broadcast_1_piece0 in > memory on vm3:53439 (size: 9.5 KB, free: 93.3 MB) > 2018-05-15 14:02:29 INFO BlockManagerInfo:54 - Added broadcast_0_piece0 in > memory on vm3:53439 (size: 33.8 KB, free: 93.3 MB) > 2018-05-15 14:02:29 INFO YarnSchedulerBackend$YarnDriverEndpoint:54 - > Registered executor NettyRpcEndpointRef(spark-client://Executor) > (10.18.99.35:44288) with ID 1 > 2018-05-15 14:02:29 INFO ExecutorAllocationManager:54 - New executor 1 has > registered (new total is 2) > > ... > 2018-05-15 14:04:31 INFO ExecutorAllocationManager:54 - Request to remove > executorIds: 2 > 2018-05-15 14:04:31 INFO YarnClientSchedulerBackend:54 - Requesting to kill > executor(s) 2 > 2018-05-15 14:04:31 INFO YarnClientSchedulerBackend:54 - Actual list of > executor(s) to be killed is 2 > 2018-05-15 14:04:31 INFO ExecutorAllocationManager:54 - Removing executor 2 > because it has been idle for 60 seconds (new desired total will be 1) *//It > should be 120 not 60* > 2018-05-15 14:04:32 INFO ExecutorAllocationManager:54 - Request to remove > executorIds: 1 > 2018-05-15 14:04:32 INFO YarnClientSchedulerBackend:54 - Requesting to kill > executor(s) 1 > 2018-05-15 14:04:32 INFO YarnClientSchedulerBackend:54 - Actual list of > executor(s) to be killed is 1 > 2018-05-15 14:04:32 INFO ExecutorAllocationManager:54 - Removing executor 1 > because it has been idle for 60 seconds (new desired total will be 0) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-24558) Driver prints the wrong info in the log when the executor which holds cacheBlock is IDLE.Time-out value displayed is not as per configuration value.
[ https://issues.apache.org/jira/browse/SPARK-24558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512288#comment-16512288 ] sandeep katta commented on SPARK-24558: --- pull request https://github.com/apache/spark/pull/21565 > Driver prints the wrong info in the log when the executor which holds > cacheBlock is IDLE.Time-out value displayed is not as per configuration value. > > > Key: SPARK-24558 > URL: https://issues.apache.org/jira/browse/SPARK-24558 > Project: Spark > Issue Type: Improvement > Components: Spark Core >Affects Versions: 2.3.1 >Reporter: sandeep katta >Priority: Minor > > > launch spark-sql > spark-sql>cache table sample; > 2018-05-15 14:02:28 INFO ExecutorAllocationManager:54 - New executor 2 has > registered (new total is 1) > 2018-05-15 14:02:28 INFO TaskSetManager:54 - Starting task 0.0 in stage 0.0 > (TID 0, vm3, executor 2, partition 0, NODE_LOCAL, 7956 bytes) > 2018-05-15 14:02:28 INFO BlockManagerMasterEndpoint:54 - Registering block > manager vm3:53439 with 93.3 MB RAM, BlockManagerId(2, vm3, 53439, None) > 2018-05-15 14:02:28 INFO BlockManagerInfo:54 - Added broadcast_1_piece0 in > memory on vm3:53439 (size: 9.5 KB, free: 93.3 MB) > 2018-05-15 14:02:29 INFO BlockManagerInfo:54 - Added broadcast_0_piece0 in > memory on vm3:53439 (size: 33.8 KB, free: 93.3 MB) > 2018-05-15 14:02:29 INFO YarnSchedulerBackend$YarnDriverEndpoint:54 - > Registered executor NettyRpcEndpointRef(spark-client://Executor) > (10.18.99.35:44288) with ID 1 > 2018-05-15 14:02:29 INFO ExecutorAllocationManager:54 - New executor 1 has > registered (new total is 2) > > ... > 2018-05-15 14:04:31 INFO ExecutorAllocationManager:54 - Request to remove > executorIds: 2 > 2018-05-15 14:04:31 INFO YarnClientSchedulerBackend:54 - Requesting to kill > executor(s) 2 > 2018-05-15 14:04:31 INFO YarnClientSchedulerBackend:54 - Actual list of > executor(s) to be killed is 2 > 2018-05-15 14:04:31 INFO ExecutorAllocationManager:54 - Removing executor 2 > because it has been idle for 60 seconds (new desired total will be 1) *//It > should be 120 not 60* > 2018-05-15 14:04:32 INFO ExecutorAllocationManager:54 - Request to remove > executorIds: 1 > 2018-05-15 14:04:32 INFO YarnClientSchedulerBackend:54 - Requesting to kill > executor(s) 1 > 2018-05-15 14:04:32 INFO YarnClientSchedulerBackend:54 - Actual list of > executor(s) to be killed is 1 > 2018-05-15 14:04:32 INFO ExecutorAllocationManager:54 - Removing executor 1 > because it has been idle for 60 seconds (new desired total will be 0) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
