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

Sean Owen commented on SPARK-8896:
----------------------------------

Why do you have multiple contexts? I think that's not allowed, right?

> StreamingSource should choose a unique name
> -------------------------------------------
>
>                 Key: SPARK-8896
>                 URL: https://issues.apache.org/jira/browse/SPARK-8896
>             Project: Spark
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.4.0
>            Reporter: Aniket Bhatnagar
>
> If 2 instances of StreamingContext are created and run using the same 
> SparkContext, it results the following exception in the logs and causes the 
> latter StreamingContext's metrics to go unreported.
> [ForkJoinPool-2-worker-7] [info] o.a.s.m.MetricsSystem -Metrics already 
> registered
> java.lang.IllegalArgumentException: A metric named 
> <AppName>.StreamingMetrics.streaming.lastReceivedBatch_processingEndTime 
> already exists
>         at 
> com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91)~[metrics-core-3.1.0.jar:3.1.0]
>         at 
> com.codahale.metrics.MetricRegistry.registerAll(MetricRegistry.java:385)~[metrics-core-3.1.0.jar:3.1.0]
>         at 
> com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:85)~[metrics-core-3.1.0.jar:3.1.0]
>         at 
> org.apache.spark.metrics.MetricsSystem.registerSource(MetricsSystem.scala:148)
>  ~[spark-core_2.11-1.4.0.jar:1.4.0]
>         at 
> org.apache.spark.streaming.StreamingContext.<init>(StreamingContext.scala:199)
>  [spark-streaming_2.11-1.4.0.jar:1.4.0]
>         at 
> org.apache.spark.streaming.StreamingContext.<init>(StreamingContext.scala:71) 
> [spark-streaming_2.11-1.4.0.jar:1.4.0]



--
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