.
Jordi
-Mensaje original-
De: Yi Pan [mailto:nickpa...@gmail.com]
Enviado el: miércoles, 12 de agosto de 2015 1:50
Para: dev@samza.apache.org
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi, Jordi,
I see your use case now. Essentially, you want to have an adjunct
ly.
> When
> > I try to access the same storage from a different job I just get null
> > results.
> >
> > How I am supposed to load the DB to be able to use it from the consuming
> > job? Is RocksDB the tool to use or should I use any other technique?
> >
>
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi, Jordi,
The local KV-store is meant to be accessed by the Samza container locally
on the machine. If you were referring to the use case that the local
KV-store is accessed by a container from a different Samza job, it is not
sup
---
> De: Yi Pan [mailto:nickpa...@gmail.com]
> Enviado el: martes, 11 de agosto de 2015 3:27
> Para: dev@samza.apache.org
> Asunto: Re: Missing a change log offset for SystemStreamPartition
>
> Hi, Jordi,
>
> Agree with Yan. More specifically, your class definition should b
[mailto:nickpa...@gmail.com]
Enviado el: martes, 11 de agosto de 2015 3:27
Para: dev@samza.apache.org
Asunto: Re: Missing a change log offset for SystemStreamPartition
Hi, Jordi,
Agree with Yan. More specifically, your class definition should be something
like:
{code}
public class testStore implements
$$anonfun$startStores$2.apply(SamzaContainer.scala:607)
> > at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> > at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> > at
> > scala.collection.MapLike$DefaultValuesIterable.
:
>
> java version "1.7.0_79"
> OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
> log4j:WARN No appenders could be found for logger
> (org.apache.samza.metrics.JmxServer).
> log4j:WARN Please ini
http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
Exception in thread "main" org.apache.samza.SamzaException: Missing a change
log offset for SystemStreamPartition [kafka, test11db-changelog, 2].
at
org.apache.samza.storage.T
samza.SamzaException: Missing a change
log offset for SystemStreamPartition [kafka, commdb-changelog, 2].
at
org.apache.samza.storage.TaskStorageManager$$anonfun$startConsumers$3$$anonfun$1.apply(TaskStorageManager.scala:87)
at
org.apache.samza.storage.TaskStorageManager$$anonfun$startCo
I also eliminated the second one.
> I am getting the same exception.
>
> Exception in thread "main" org.apache.samza.SamzaException: Missing a
> change log offset for SystemStreamPartition [kafka, testdb-changelog, 2].
> at
> org.apache.samza.storage.TaskStorag
I changed the job name and the store name. I was defining two different stores
and in case that was the problem, I also eliminated the second one. I am
getting the same exception.
Exception in thread "main" org.apache.samza.SamzaException: Missing a change
log offset for SystemStrea
String str = storestp.get(code)
> …
> }
>
> When I load it, it goes to running but, whe I send the messages through
> Kafka stream It goes to Failed state. I have found this Exception:
> Exception in thread "main" org.apache.samza.SamzaException: Mis
p.get(code)
…
}
When I load it, it goes to running but, whe I send the messages through Kafka
stream It goes to Failed state. I have found this Exception:
Exception in thread "main" org.apache.samza.SamzaException: Missing a change
log offset for SystemStreamPartition [kafka, stepdb-chang
13 matches
Mail list logo
