Hi, Jose, Sorry for the delay. I left a comment on SAMZA-41.
As for SAMZA-870, could you add your detailed job config file, the version of samza build that you used, and the logs from the failed run to the JIRA? Thanks a lot! On Mon, May 2, 2016 at 2:38 PM, José Barrueta <j...@stormpath.com> wrote: > Hi! > > Do you guys know if there has been any updates in these two issues, or any > other reports around SAMZA-870? For SAMZA-41 any comments on it? > > Thank you! > > - José Luis > > On Wed, Mar 9, 2016 at 5:31 PM Navina Ramesh <nram...@linkedin.com.invalid > > > wrote: > > > 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 <j...@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 > > <nram...@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 <j...@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. > > >
