Re: Trouble running samza 0.14 in standalone mode
Great! Glad that you were able to figure it out! -Yi On Thu, Mar 7, 2019 at 3:14 AM Anoop Krishnakumar < anoop.krishnaku...@gmail.com> wrote: > Hi Yi, > > Apologies for my ignorance. I did not realize that attachments wont make > through and gist is the preferred method of sharing logs and code snippets. > > Issue is resolved. I was using the default task.name.grouper.factory > instead of GroupByContainerIdsFactory. > Appreciate and thanks for the response. I will consider using 1.0 version. > > -anoop > > > On Thu, 7 Mar 2019 at 01:41, Yi Pan wrote: > > > Hi, Anoop, > > > > 1. Please provide the full log file if possible. Just listing out a > single > > log line reporting the failure does not help. > > 2. Is there any reason that you still stay with Samza 0.14? I would > highly > > recommend to upgrade to 1.0 since there are tons of API and standalone > > related improvements went in to that version after 0.14. > > > > -Yi > > > > On Wed, Mar 6, 2019 at 1:54 PM Anoop Krishnakumar < > > anoop.krishnaku...@gmail.com> wrote: > > > > > I am prototyping an application where I have two input topics and two > > > output topics. The application also uses a rocksdb state store that is > > > backed by kafka. > > > > > > I followed WikipediaZkLocalApplication example, but the application > > always > > > exits without listening for messages from topic. I could see the > > execution > > > plan and job coordinator communicating with zookeeper. I could see the > > > following line in logs > > > StreamProcessor [INFO] Container is not instantiated for stream > > processor: > > > 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35. > > > I could not figure out why the container wouldn't start. Any help would > > be > > > appreciated. > > > > > > Attached is the log and the job configuration. > > > > > > -anoop > > > > > >
Re: Trouble running samza 0.14 in standalone mode
Hi Yi, Apologies for my ignorance. I did not realize that attachments wont make through and gist is the preferred method of sharing logs and code snippets. Issue is resolved. I was using the default task.name.grouper.factory instead of GroupByContainerIdsFactory. Appreciate and thanks for the response. I will consider using 1.0 version. -anoop On Thu, 7 Mar 2019 at 01:41, Yi Pan wrote: > Hi, Anoop, > > 1. Please provide the full log file if possible. Just listing out a single > log line reporting the failure does not help. > 2. Is there any reason that you still stay with Samza 0.14? I would highly > recommend to upgrade to 1.0 since there are tons of API and standalone > related improvements went in to that version after 0.14. > > -Yi > > On Wed, Mar 6, 2019 at 1:54 PM Anoop Krishnakumar < > anoop.krishnaku...@gmail.com> wrote: > > > I am prototyping an application where I have two input topics and two > > output topics. The application also uses a rocksdb state store that is > > backed by kafka. > > > > I followed WikipediaZkLocalApplication example, but the application > always > > exits without listening for messages from topic. I could see the > execution > > plan and job coordinator communicating with zookeeper. I could see the > > following line in logs > > StreamProcessor [INFO] Container is not instantiated for stream > processor: > > 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35. > > I could not figure out why the container wouldn't start. Any help would > be > > appreciated. > > > > Attached is the log and the job configuration. > > > > -anoop > > >
Re: Trouble running samza 0.14 in standalone mode
Hi, Anoop, 1. Please provide the full log file if possible. Just listing out a single log line reporting the failure does not help. 2. Is there any reason that you still stay with Samza 0.14? I would highly recommend to upgrade to 1.0 since there are tons of API and standalone related improvements went in to that version after 0.14. -Yi On Wed, Mar 6, 2019 at 1:54 PM Anoop Krishnakumar < anoop.krishnaku...@gmail.com> wrote: > I am prototyping an application where I have two input topics and two > output topics. The application also uses a rocksdb state store that is > backed by kafka. > > I followed WikipediaZkLocalApplication example, but the application always > exits without listening for messages from topic. I could see the execution > plan and job coordinator communicating with zookeeper. I could see the > following line in logs > StreamProcessor [INFO] Container is not instantiated for stream processor: > 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35. > I could not figure out why the container wouldn't start. Any help would be > appreciated. > > Attached is the log and the job configuration. > > -anoop >
Re: Trouble running samza 0.14 in standalone mode
Can you please attach the container logs? I noticed only job configurations were attached. -- Bharath From: Anoop Krishnakumar Reply-To: "dev@samza.apache.org" Date: Wednesday, March 6, 2019 at 1:54 PM To: "dev@samza.apache.org" Subject: Trouble running samza 0.14 in standalone mode I am prototyping an application where I have two input topics and two output topics. The application also uses a rocksdb state store that is backed by kafka. I followed WikipediaZkLocalApplication example, but the application always exits without listening for messages from topic. I could see the execution plan and job coordinator communicating with zookeeper. I could see the following line in logs StreamProcessor [INFO] Container is not instantiated for stream processor: 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35. I could not figure out why the container wouldn't start. Any help would be appreciated. Attached is the log and the job configuration. -anoop
Trouble running samza 0.14 in standalone mode
I am prototyping an application where I have two input topics and two output topics. The application also uses a rocksdb state store that is backed by kafka. I followed WikipediaZkLocalApplication example, but the application always exits without listening for messages from topic. I could see the execution plan and job coordinator communicating with zookeeper. I could see the following line in logs StreamProcessor [INFO] Container is not instantiated for stream processor: 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35. I could not figure out why the container wouldn't start. Any help would be appreciated. Attached is the log and the job configuration. -anoop job.name=iva-stream-application job.default.system=kafka job.coordinator.factory=org.apache.samza.zk.ZkJobCoordinatorFactory job.coordinator.zk.connect=localhost:2181 # Kafka System systems.kafka.samza.factory=org.apache.samza.system.kafka.KafkaSystemFactory systems.kafka.consumer.zookeeper.connect=localhost:2181 systems.kafka.producer.bootstrap.servers=localhost:9092 systems.kafka.producer.max.request.size=15000180 systems.kafka.default.stream.replication.factor=1 # Input Streams streams.sensor-audit.samza.system=kafka streams.sensor-audit.samza.physical.name=rsdata.public.issues streams.risk-updates.samza.system=kafka streams.risk-updates.samza.physical.name=rsdata.public.rs_updates_issues_timestamps2 # State store serializers.registry.string.class=org.apache.samza.serializers.StringSerdeFactory serializers.registry.assetlabelserde.class=com.rootsecure.insights.serde.AssetLabelSerdeFactory stores.AssetLabelStore.factory=org.apache.samza.storage.kv.RocksDbKeyValueStorageEngineFactory stores.AssetLabelStore.changelog=kafka.asset-labels-changelog stores.AssetLabelStore.key.serde=string stores.AssetLabelStore.msg.serde=assetlabelserde
