Hi, Yi,
I couldn't find any errors in the log indicating any issue writing to those
particular changelog partitions. I event went ahead and removed all
checkpoint, coordinator and changelog topics and started fresh. This issue
is still manifested itself with offsets of 0:
partition offset
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48393/
---
(Updated June 13, 2016, 11:59 p.m.)
Review request for samza and Yi Pan (Data
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48393/
---
(Updated June 13, 2016, 11:52 p.m.)
Review request for samza and Yi Pan (Data
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48080/
---
(Updated June 13, 2016, 10:28 p.m.)
Review request for samza.
Changes
Hey Jack,
Be sure to check the AM log in addition to the container logs. The AM log
will show cases where the AM killed a container (e.g. for exceeding
yarn.container.memory.mb).
The only time I've ever seen a container die with nothing in the container
log, syserr, or AM log, it was being
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48080/#review137376
---
Ship it!
Really like this latest diff. Addresses all my
Hi, David,
Did you check the log to see whether there is any log lines indicating the
producer issues on the three partitions that you suspect? And could you
also check whether you have auto-commit turned on? If your auto-commit is
on and producer does not report any issue writing to the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48621/
---
Review request for samza.
Bugs: SAMZA-949
Hi, Pan,
I was reading the 10.0 documentation on Samza state management. One
particular section that explains counting the number of page views for each
user stands out to me, as it also uses a full table scan to output
aggregation results:
Note that this job effectively pauses at the hour mark
