Thanks a lot Pramod for going an extra mile and providing solution on this
issue. The explanation totally makes sense and I will keep this in mind
during any future development
Regards
Vivek
--
View this message in context:
Hi Pramod and Thomas
Below are my findings till now on this issue
1. Fix suggested by Pramod and fix made as apart of
https://issues.apache.org/jira/browse/APEXMALHAR-2526 are doing the same
thing
2. In the comments for https://issues.apache.org/jira/browse/APEXMALHAR-2526
I found that, the new
My bad let me see..
On Fri, Aug 11, 2017 at 11:13 AM, Vivek Bhide
wrote:
> It is present in class.. just after setCapacity method
>
>
>
> --
> View this message in context: http://apache-apex-users-list.
> 78494.x6.nabble.com/How-the-application-recovery-works-
>
It is present in class.. just after setCapacity method
--
View this message in context:
http://apache-apex-users-list.78494.x6.nabble.com/How-the-application-recovery-works-when-its-started-with-originalAppId-tp1821p1838.html
Sent from the Apache Apex Users list mailing list archive at
Provide an empty constructor as well.
On Fri, Aug 11, 2017 at 10:39 AM, Vivek Bhide
wrote:
> Please refer the LRUCache class from the code base I pasted above. Its
> exactly what I m using
>
> Regards
> Vivek
>
>
>
> --
> View this message in context:
Please refer the LRUCache class from the code base I pasted above. Its
exactly what I m using
Regards
Vivek
--
View this message in context:
http://apache-apex-users-list.78494.x6.nabble.com/How-the-application-recovery-works-when-its-started-with-originalAppId-tp1821p1836.html
Sent from the
Can you share the code for your class that extends the linked hash map.
Thanks
On Thu, Aug 10, 2017 at 11:05 PM Vivek Bhide wrote:
> Thank You Pramod and Thomas for all your inputs.
>
> Hi Pramod,
> Jira https://issues.apache.org/jira/browse/APEXMALHAR-2526 that Thomas
Thank You Pramod and Thomas for all your inputs.
Hi Pramod,
Jira https://issues.apache.org/jira/browse/APEXMALHAR-2526 that Thomas
referred seem to be the one inline with what you suggested as a possible
solution. I see there is new class KryoJavaSerializer.java (new in malhar
and not present
Vivek,
Also a slightly more portable modification to what I suggested earlier is
to use kryo.getClassLoader() instead of
Thread.currentThread().getContextClassLoader()
in the JavaSerializer.
Thanks
On Thu, Aug 10, 2017 at 8:25 PM, Pramod Immaneni
wrote:
> I believe
I believe those relate to different problems. This is a scenario where part
of deserializarion is being outsourced to an external deserializer that is
not using the correct class loader. The suggested fix to the behavior of
the external serde seemed to have worked though I plan to follow up with
There are couple bugs that were recently identified that look related to
this:
https://issues.apache.org/jira/browse/APEXMALHAR-2526
https://issues.apache.org/jira/browse/APEXCORE-767
Perhaps the fix for first item is what you need?
Thomas
On Thu, Aug 10, 2017 at 8:41 PM, Pramod Immaneni
I would dig deeper into why serde of the linked hashmap is failing. There
are additional logging you can enable in kryo to get more insight. You can
even try a standalone kryo test to see if it is a problem with the
linkedhashmap itself or because of some other object that was added to it.
You
Thanks Pramod.. This seems to have done trick.. I will check again when I
have some data to process to see if that goes well with it. I am quite
confident that it will
Just curious, Is this the best way to handle this issue or if there is any
other elegant way it can be addressed?
Regards
Vivek
I have already pasted the stack trace in my original post. Also can you
please confirm what is the classpath kryo is using v/s default Java
serializer and where exactly is set for kryo?
Regards
Vivek
--
View this message in context:
Hi Pramod,
As I told we have LRUCache (LinkedHashMap of ) which needs to
be serialized and it is initialized in operator constructor. What we found
that, when operator is serialized for checkpointing the content of the this
LRUcache is not getting serialized and instead its just an
Hi Pramod,
I get this error even when I try to resubmit the exact same apa Is there any
other angle of this problem that i should look for?
Regards
Vivek
--
View this message in context:
It will try to deserialize the old state (from prior applicaiton
checkpoints) with your new jars from the apa that you are trying to launch.
So if there are structural incompatibilities the deser will fail.
On Thu, Aug 10, 2017 at 11:41 AM, Vivek Bhide
wrote:
> Hi All,
>
17 matches
Mail list logo