[
https://issues.apache.org/jira/browse/SAMZA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Hoover updated SAMZA-502:
-------------------------------
Description:
To reproduce:
- Create a job that bootstraps topic "config" and consumes topic "events"
- Create both topics in Kafka but only populate the "events" topic
- Start the job
- Now populate the "config" topic
What happens:
- The job will consume the messages in the "config" topic but not unblock the
"events" topic
What should happen:
* Either
** Samza should consider an empty bootstrap topic as "caught up" and
immediately start processing the "event" topic
** Samza should consider an empty bootstrap topic as a fatal error and exit
I uploaded some trace logs here in case they help: http://pastebin.com/RsdwYkRk
In this case, the bootstrap topic is called "ops.web.parse_rules__ck_4_module"
and the event topic is called "ops._raw.web_parsed"
I'm testing using the ProcessJobFactory in case it matters.
was:
To reproduce:
- Create a job that bootstraps topic "config" and consumes topic "events"
- Create both topics in Kafka but only populate the "events" topic
- Start the job
- Now populate the "config" topic
What happens:
- The job will consume the messages in the "config" topic but not unblock the
"events" topic
What should happen:
* Either
** Samza should consider an empty bootstrap topic as "caught up" and
immediately start processing the "event" topic
** Samza should consider an empty bootstrap topic as a fatal error and exit
I uploaded some trace logs here in case they help: http://pastebin.com/RsdwYkRk
In this case, the bootstrap topic is called "ops.web.parse_rules__ck_4_module"
and the event topic is called "ops._raw.web_parsed"
> BootstrappingChooser never unblocks if bootstrap topic is initially empty
> --------------------------------------------------------------------------
>
> Key: SAMZA-502
> URL: https://issues.apache.org/jira/browse/SAMZA-502
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.8.0
> Reporter: Roger Hoover
> Priority: Critical
>
> To reproduce:
> - Create a job that bootstraps topic "config" and consumes topic "events"
> - Create both topics in Kafka but only populate the "events" topic
> - Start the job
> - Now populate the "config" topic
> What happens:
> - The job will consume the messages in the "config" topic but not unblock the
> "events" topic
> What should happen:
> * Either
> ** Samza should consider an empty bootstrap topic as "caught up" and
> immediately start processing the "event" topic
> ** Samza should consider an empty bootstrap topic as a fatal error and exit
> I uploaded some trace logs here in case they help:
> http://pastebin.com/RsdwYkRk
> In this case, the bootstrap topic is called
> "ops.web.parse_rules__ck_4_module" and the event topic is called
> "ops._raw.web_parsed"
> I'm testing using the ProcessJobFactory in case it matters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
