Do note that this problem may be fixed in Spark 1.2, as we changed the
default transfer service to use a Netty-based one rather than the
ConnectionManager.
On Thu, Jan 8, 2015 at 7:05 AM, Spidy wrote:
> Hi,
>
> Can you please explain which settings did you changed?
>
>
>
> --
> View this message
Hi,
Can you please explain which settings did you changed?
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/ERROR-ConnectionManager-Corresponding-SendingConnection-to-ConnectionManagerId-tp17050p21035.html
Sent from the Apache Spark User List mailing list ar
Yes please can you share. I am getting this error after expanding my
application to include a large broadcast variable. Would be good to know if
it can be fixed with configuration.
On 23 October 2014 18:04, Michael Campbell
wrote:
> Can you list what your fix was so others can benefit?
>
> On W
Can you list what your fix was so others can benefit?
On Wed, Oct 22, 2014 at 8:15 PM, arthur.hk.c...@gmail.com <
arthur.hk.c...@gmail.com> wrote:
> Hi,
>
> I have managed to resolve it because a wrong setting. Please ignore this .
>
> Regards
> Arthur
>
> On 23 Oct, 2014, at 5:14 am, arthur.hk.c
Hi,
I have managed to resolve it because a wrong setting. Please ignore this .
Regards
Arthur
On 23 Oct, 2014, at 5:14 am, arthur.hk.c...@gmail.com
wrote:
>
> 14/10/23 05:09:04 WARN ConnectionManager: All connections not cleaned up
>