Re: Akka dissassociated
The amount of resource assigned to JobManager looks fine. How much resource (CPU and memory) did you allocate for TaskManager? On Wed, Jul 19, 2017 at 3:07 AM, Stephan Ewen wrote: > Hi Greg! > > Akka disassociation means that the network connection between the > JobManager and TaskManager broke. > > This can be cause by > - actual failures of JobManager / TaskManager (I assume is not the case > here) > - A limit in the number of open file handles > - Network flakeyness > - I have seen cases where it looks like it was caused by network overload > where shuffles basically starve/suppress the akka network connections > > > Handling this in akka is not very nice - one does not get an easy way to > actually deal with the root issues, but the actor systems sort of hides > these things. This is yet one more reason why I am thinking to move away > from akka - it may simply not be the best match for what we are doing. > > > Greetings, > Stephan > > > On Fri, Jul 14, 2017 at 7:11 PM, Greg Hogan wrote: > > > Hi all, > > > > I’m having some issues with Akka running on a modest cluster where > > increasing the parallelism results in disassociation messages. > > > > I am running a batch job, Gelly’s TriangleListing (for simplicity) which > > is join-based. I have not seen this issue running AdamicAdar which is > > sort-based. > > > > I have increased both of the following timeouts and the job takes less > > than 100 seconds. > > akka.ask.timeout: 1000 s > > akka.lookup.timeout: 100 s > > > > I have not changed taskmanager.exit-on-fatal-akka-error from the default > > value of false but the JobManager is dropping all TaskManager > connections. > > > > I can run the TriangleListing job with the same 127 TaskManagers with a > > smaller parallelism. Dropping from 2286 to around 1000 is often > successful. > > > > CPU and memory should not be a bottleneck for the JobManager (18 cores > and > > 18 GB). > > > > I would be grateful for solutions, suggestions, or pointers to debugging > > this issue. > > > > Thanks, > > Greg > > > > > > 2017-07-14 16:50:08,119 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (30/2286) ( > > 5a2e8f0a00530bd2216d7d3ee10688f7) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:08,312 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (26/2286) ( > > c6a91db2d6b6797768596d9f746d316f) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:09,831 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (131/2286) ( > > 2c77b1e4b90b951d3be1e09bf4cf41d2) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:10,057 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (133/2286) ( > > d0c4c4eda4f0c44fe594a1b94eb66c93) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:11,861 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (70/2286) ( > > 69ce8d91fbbad943c277ee92d3c38aaa) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:15,029 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (38/2286) ( > > a72c2dee009342bc4d90ec98427fa717) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:16,583 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (27/2286) ( > > e79ec6229d4afdc6669c1c221a19ad8c) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:19,498 INFO org.apache.flink.runtime. > executiongraph.ExecutionGraph > > - GroupReduce (Generate triplets) (44/2286) ( > > 53e35ddbd0e02d256620e5310276bea6) switched from RUNNING to FINISHED. > > 2017-07-14 16:50:21,021 WARN akka.remote.ReliableDeliverySupervisor > > - Association with remote system > > [akka.tcp://flink@ip-10-0-28-115:40713] has failed, address is now gated > > for [5000] ms. Reason: [Disassociated] > > 2017-07-14 16:50:21,097 WARN akka.remote.ReliableDeliverySupervisor > > - Association with remote system > > [akka.tcp://flink@ip-10-0-21-141:45899] has failed, address is now gated > > for [5000] ms. Reason: [Disassociated] > > 2017-07-14 16:50:21,129 WARN akka.remote.ReliableDeliverySupervisor > > - Association with remote system > > [akka.tcp://flink@ip-10-0-27-236:37471] has failed, address is now gated > > for [5000] ms. Reason: [Disassociated] > > 2017-07-14 16:50:21,132 WARN akka.remote.ReliableDeliverySupervisor > > - Association with remote system > > [akka.tcp://flink@ip-10-0-18-79:45765] has failed, address is now gated > > for [5000] ms. Reason: [Disassociated] > > 2017-07-14 16:50:21,140 WARN akka.remote.ReliableDeliverySupervisor > > - Association with remote system > > [akka.tcp://flink@ip-10-0-29-112:41017] has failed,
Re: Akka dissassociated
Hi Greg! Akka disassociation means that the network connection between the JobManager and TaskManager broke. This can be cause by - actual failures of JobManager / TaskManager (I assume is not the case here) - A limit in the number of open file handles - Network flakeyness - I have seen cases where it looks like it was caused by network overload where shuffles basically starve/suppress the akka network connections Handling this in akka is not very nice - one does not get an easy way to actually deal with the root issues, but the actor systems sort of hides these things. This is yet one more reason why I am thinking to move away from akka - it may simply not be the best match for what we are doing. Greetings, Stephan On Fri, Jul 14, 2017 at 7:11 PM, Greg Hogan wrote: > Hi all, > > I’m having some issues with Akka running on a modest cluster where > increasing the parallelism results in disassociation messages. > > I am running a batch job, Gelly’s TriangleListing (for simplicity) which > is join-based. I have not seen this issue running AdamicAdar which is > sort-based. > > I have increased both of the following timeouts and the job takes less > than 100 seconds. > akka.ask.timeout: 1000 s > akka.lookup.timeout: 100 s > > I have not changed taskmanager.exit-on-fatal-akka-error from the default > value of false but the JobManager is dropping all TaskManager connections. > > I can run the TriangleListing job with the same 127 TaskManagers with a > smaller parallelism. Dropping from 2286 to around 1000 is often successful. > > CPU and memory should not be a bottleneck for the JobManager (18 cores and > 18 GB). > > I would be grateful for solutions, suggestions, or pointers to debugging > this issue. > > Thanks, > Greg > > > 2017-07-14 16:50:08,119 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (30/2286) ( > 5a2e8f0a00530bd2216d7d3ee10688f7) switched from RUNNING to FINISHED. > 2017-07-14 16:50:08,312 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (26/2286) ( > c6a91db2d6b6797768596d9f746d316f) switched from RUNNING to FINISHED. > 2017-07-14 16:50:09,831 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (131/2286) ( > 2c77b1e4b90b951d3be1e09bf4cf41d2) switched from RUNNING to FINISHED. > 2017-07-14 16:50:10,057 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (133/2286) ( > d0c4c4eda4f0c44fe594a1b94eb66c93) switched from RUNNING to FINISHED. > 2017-07-14 16:50:11,861 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (70/2286) ( > 69ce8d91fbbad943c277ee92d3c38aaa) switched from RUNNING to FINISHED. > 2017-07-14 16:50:15,029 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (38/2286) ( > a72c2dee009342bc4d90ec98427fa717) switched from RUNNING to FINISHED. > 2017-07-14 16:50:16,583 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (27/2286) ( > e79ec6229d4afdc6669c1c221a19ad8c) switched from RUNNING to FINISHED. > 2017-07-14 16:50:19,498 INFO > org.apache.flink.runtime.executiongraph.ExecutionGraph > - GroupReduce (Generate triplets) (44/2286) ( > 53e35ddbd0e02d256620e5310276bea6) switched from RUNNING to FINISHED. > 2017-07-14 16:50:21,021 WARN akka.remote.ReliableDeliverySupervisor > - Association with remote system > [akka.tcp://flink@ip-10-0-28-115:40713] has failed, address is now gated > for [5000] ms. Reason: [Disassociated] > 2017-07-14 16:50:21,097 WARN akka.remote.ReliableDeliverySupervisor > - Association with remote system > [akka.tcp://flink@ip-10-0-21-141:45899] has failed, address is now gated > for [5000] ms. Reason: [Disassociated] > 2017-07-14 16:50:21,129 WARN akka.remote.ReliableDeliverySupervisor > - Association with remote system > [akka.tcp://flink@ip-10-0-27-236:37471] has failed, address is now gated > for [5000] ms. Reason: [Disassociated] > 2017-07-14 16:50:21,132 WARN akka.remote.ReliableDeliverySupervisor > - Association with remote system > [akka.tcp://flink@ip-10-0-18-79:45765] has failed, address is now gated > for [5000] ms. Reason: [Disassociated] > 2017-07-14 16:50:21,140 WARN akka.remote.ReliableDeliverySupervisor > - Association with remote system > [akka.tcp://flink@ip-10-0-29-112:41017] has failed, address is now gated > for [5000] ms. Reason: [Disassociated] > 2017-07-14 16:50:21,142 WARN akka.remote.ReliableDeliverySupervisor > - Association with remote system > [akka.tcp://flink@ip-10-0-25-70:39625] has failed, address is now gated > for [5000] ms. Reason: [Disassociated] > 2017-07-14 16:50:21,159 WARN akka.remote.ReliableDeliverySupervisor >
Akka dissassociated
Hi all, I’m having some issues with Akka running on a modest cluster where increasing the parallelism results in disassociation messages. I am running a batch job, Gelly’s TriangleListing (for simplicity) which is join-based. I have not seen this issue running AdamicAdar which is sort-based. I have increased both of the following timeouts and the job takes less than 100 seconds. akka.ask.timeout: 1000 s akka.lookup.timeout: 100 s I have not changed taskmanager.exit-on-fatal-akka-error from the default value of false but the JobManager is dropping all TaskManager connections. I can run the TriangleListing job with the same 127 TaskManagers with a smaller parallelism. Dropping from 2286 to around 1000 is often successful. CPU and memory should not be a bottleneck for the JobManager (18 cores and 18 GB). I would be grateful for solutions, suggestions, or pointers to debugging this issue. Thanks, Greg 2017-07-14 16:50:08,119 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (30/2286) (5a2e8f0a00530bd2216d7d3ee10688f7) switched from RUNNING to FINISHED. 2017-07-14 16:50:08,312 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (26/2286) (c6a91db2d6b6797768596d9f746d316f) switched from RUNNING to FINISHED. 2017-07-14 16:50:09,831 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (131/2286) (2c77b1e4b90b951d3be1e09bf4cf41d2) switched from RUNNING to FINISHED. 2017-07-14 16:50:10,057 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (133/2286) (d0c4c4eda4f0c44fe594a1b94eb66c93) switched from RUNNING to FINISHED. 2017-07-14 16:50:11,861 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (70/2286) (69ce8d91fbbad943c277ee92d3c38aaa) switched from RUNNING to FINISHED. 2017-07-14 16:50:15,029 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (38/2286) (a72c2dee009342bc4d90ec98427fa717) switched from RUNNING to FINISHED. 2017-07-14 16:50:16,583 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (27/2286) (e79ec6229d4afdc6669c1c221a19ad8c) switched from RUNNING to FINISHED. 2017-07-14 16:50:19,498 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph- GroupReduce (Generate triplets) (44/2286) (53e35ddbd0e02d256620e5310276bea6) switched from RUNNING to FINISHED. 2017-07-14 16:50:21,021 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-28-115:40713] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,097 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-21-141:45899] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,129 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-27-236:37471] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,132 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-18-79:45765] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,140 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-29-112:41017] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,142 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-25-70:39625] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,159 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-28-105:39127] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,170 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-28-117:38923] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,181 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-20-172:40007] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 2017-07-14 16:50:21,190 WARN akka.remote.ReliableDeliverySupervisor - Association with remote system [akka.tcp://flink@ip-10-0-22-220:44391] has failed, address is now gated for [5000] ms. Reason: [Disassociated]
