samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Navina Ramesh <nram...@linkedin.com.INVALID>
Subject Re: SAMZA-870 & SAMZA-41
Date Thu, 10 Mar 2016 01:31:30 GMT
Ah my bad. I didn't read your exception properly.

Ok. I haven't seen this exception before. I can give it a try with the
SAMZA-41 patch and try it out on my end.

Navina

On Wed, Mar 9, 2016 at 5:27 PM, José Barrueta <jose@stormpath.com> wrote:

> Hi Navina,
>
> Thanks for your quick reply!
>
> Actually this problem occurs at runtime while deploying our samza jobs in
> our staging environment, we are deploying a custom samza 0.10.0 version
>  with SAMZA-41 in it.
>
> We ran the same job with samza 0.9.1 and we didn't have any issues in it.
>
> Thanks for your help,
>
> José Luis B.
>
>
>
> On Wed, Mar 9, 2016 at 5:13 PM Navina Ramesh <nramesh@linkedin.com.invalid
> >
> wrote:
>
> > Hi Jose,
> > I will review the patch to SAMZA-41 today. Regarding the RocksDB issue, I
> > haven't encountered this issue after we pulled in the latest rocksdb
> > release. Then again, I was trying to build on RHEL6 and not on Debian.
> >
> > Have you tried clearing the gradle caches before building again?
> >
> > Thanks!
> > Navina
> >
> > On Wed, Mar 9, 2016 at 5:06 PM, José Barrueta <jose@stormpath.com>
> wrote:
> >
> > > Hi all,
> > >
> > > I just added a question to SAMZA-870, since we run into the same issue
> > > using Debian GNU/Linux 7 and Java 8 (Oracle 1.8.0_60).
> > >
> > > One thing we tried was to not use compression but the we got this
> error:
> > >
> > > Exception in thread "ThreadJob" org.rocksdb.RocksDBException:
> Corruption:
> > > truncated block read
> > > at org.rocksdb.RocksDB.remove(Native Method)
> > > at org.rocksdb.RocksDB.remove(RocksDB.java:979)
> > > at
> > >
> > >
> >
> org.apache.samza.storage.kv.RocksDbKeyValueStore.putAll(RocksDbKeyValueStore.scala:157)
> > > at
> > >
> > >
> >
> org.apache.samza.storage.kv.SerializedKeyValueStore.putAll(SerializedKeyValueStore.scala:73)
> > > at org.apache.samza.storage.kv.CachedStore.flush(CachedStore.scala:193)
> > > at
> > >
> > >
> >
> org.apache.samza.storage.kv.NullSafeKeyValueStore.flush(NullSafeKeyValueStore.scala:82)
> > > at
> > >
> > >
> >
> org.apache.samza.storage.kv.KeyValueStorageEngine.flush(KeyValueStorageEngine.scala:123)
> > > at
> > >
> > >
> >
> org.apache.samza.storage.kv.KeyValueStorageEngine.close(KeyValueStorageEngine.scala:135)
> > > at
> > >
> > >
> >
> org.apache.samza.storage.kv.KeyValueStorageEngine.stop(KeyValueStorageEngine.scala:12
> > >
> > > Has anyone else run into this issue? Any hints to fix it?
> > >
> > > On a separate note, already pushed an updated patch to SAMZA-41 in case
> > > anyone can review it.
> > >
> > > Thanks,
> > >
> > > Jose Luis Barrueta
> > >
> >
> >
> >
> > --
> > Navina R.
> >
>



-- 
Navina R.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message