2015-10-15 5 views
5

Ben aws üzerinde şu cümleyi çalıştırıyorumWARN ReliableDeliverySupervisor: Uzak sistemle bağlantı başarısız oldu, adres artık [5000] ms. Sebep: [kaldırdık]

val sqlContext = new org.apache.spark.sql.SQLContext(sc) 
import sqlContext.implicits._ 

case class Wiki(project: String, title: String, count: Int, byte_size: String) 

val data = sc.textFile("s3n://+++/").map(_.split(" ")).filter(_.size ==4).map(p => Wiki(p(0), p(1), p(2).trim.toInt, p(3))) 

val df = data.toDF() 
df.printSchema() 

val en_agg_df = df.filter("project = 'en'").select("title","count").groupBy("title").sum().collect() 

yaklaşık 2 saat aşağıdaki hatayı alıyorum çalıştırdıktan sonra edebilirsiniz kıvılcım:

WARN ReliableDeliverySupervisor: Association with remote system [akka.tcp://[email protected]:42514] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 
15/10/15 17:38:36 WARN YarnSchedulerBackend$YarnSchedulerEndpoint: ApplicationMaster has disassociated: 172.31.14.190:42514 
15/10/15 17:38:36 WARN YarnSchedulerBackend$YarnSchedulerEndpoint: ApplicationMaster has disassociated: 172.31.14.190:42514 
15/10/15 17:38:36 WARN ReliableDeliverySupervisor: Association with remote system [akka.tcp://[email protected]:43340] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 
15/10/15 17:38:36 ERROR YarnScheduler: Lost executor 1 on ip-172-31-14-190.ap-northeast-1.compute.internal: remote Rpc client disassociated 
15/10/15 17:38:36 INFO TaskSetManager: Re-queueing tasks for 1 from TaskSet 0.0 
15/10/15 17:38:36 WARN TaskSetManager: Lost task 4736.0 in stage 0.0 (TID 4736, ip-172-31-14-190.ap-northeast-1.compute.internal): ExecutorLostFailure (executor 1 lost) 
15/10/15 17:38:36 INFO DAGScheduler: Executor lost: 1 (epoch 0) 
15/10/15 17:38:36 INFO BlockManagerMasterEndpoint: Trying to remove executor 1 from BlockManagerMaster. 
15/10/15 17:38:36 INFO BlockManagerMasterEndpoint: Removing block manager BlockManagerId(1, ip-172-31-14-190.ap-northeast-1.compute.internal, 58890) 
15/10/15 17:38:36 INFO BlockManagerMaster: Removed 1 successfully in removeExecutor 
15/10/15 17:38:36 ERROR YarnScheduler: Lost executor 2 on ip-172-31-14-190.ap-northeast-1.compute.internal: remote Rpc client disassociated 
15/10/15 17:38:36 WARN ReliableDeliverySupervisor: Association with remote system [akka.tcp://[email protected]:60961] has failed, address is now gated for [5000] ms. Reason: [Disassociated] 
15/10/15 17:38:36 INFO TaskSetManager: Re-queueing tasks for 2 from TaskSet 0.0 
15/10/15 17:38:36 WARN TaskSetManager: Lost task 4735.0 in stage 0.0 (TID 4735, ip-172-31-14-190.ap-northeast-1.compute.internal): ExecutorLostFailure (executor 2 lost) 
15/10/15 17:38:36 INFO DAGScheduler: Executor lost: 2 (epoch 0) 
15/10/15 17:38:36 INFO BlockManagerMasterEndpoint: Trying to remove executor 2 from BlockManagerMaster. 
15/10/15 17:38:36 INFO BlockManagerMasterEndpoint: Removing block manager BlockManagerId(2, ip-172-31-14-190.ap-northeast-1.compute.internal, 58811) 
15/10/15 17:38:36 INFO BlockManagerMaster: Removed 2 successfully in removeExecutor 

ne demek bu? Bunu nasıl düzeltebilirim?

+1

infaz olasılıkla bellek bitti. Bu yüzden, kapsayıcı günlüğünü kaybeden yöneticilerden birinin ve muhtemelen üzerinde çalıştığı düğümdeki iplik yumurtlama oturumunu denetlemeniz gerekir. – ChristopherB

+0

@ChristopherB thx yorum için çok fazla! –

+0

Çalışıyor mu veya daha fazla hata bilgisi mi buldunuz? – ChristopherB

cevap

0

cevap zaten yorumlarda sağlanacak görünür:

It seems to be a out-of-memory on executor, because it went well if I add more machine to the cluster

İlgili konular