That patch seems to have fixed the problem.
> On Nov 18, 2015, at 3:43 PM, Rick Mangi wrote:
>
> Sorry. Just read the bug. Yes, that makes sense. I deleted a bunch of topics
> and then hit this.
>
>
>> On Nov 18, 2015, at 3:42 PM, Rick Mangi wrote:
>>
>> I take that back, it happened again
Sorry. Just read the bug. Yes, that makes sense. I deleted a bunch of topics
and then hit this.
> On Nov 18, 2015, at 3:42 PM, Rick Mangi wrote:
>
> I take that back, it happened again. Will try your patch.
>
>
>> On Nov 18, 2015, at 3:36 PM, Rick Mangi wrote:
>>
>> I seem to have solved i
I take that back, it happened again. Will try your patch.
> On Nov 18, 2015, at 3:36 PM, Rick Mangi wrote:
>
> I seem to have solved it by only specifying a single zookeeper node in my job
> config. Maybe a race condition of some sort?
>
>
>> On Nov 18, 2015, at 2:37 PM, Yi Pan wrote:
>>
>
I seem to have solved it by only specifying a single zookeeper node in my job
config. Maybe a race condition of some sort?
> On Nov 18, 2015, at 2:37 PM, Yi Pan wrote:
>
> Hi, Rick,
>
> I think that you are running into SAMZA-754. I have a RB available for it
> already. I will upload the patc
Hi, Rick,
I think that you are running into SAMZA-754. I have a RB available for it
already. I will upload the patch and it would be good if you can try the
patch to see whether that solves your problem.
-Yi
On Tue, Nov 17, 2015 at 12:01 PM, Rick Mangi wrote:
> Hi, getting things working on sa
Hi, getting things working on samza 0.10.0 finally :)
I’m seeing the following error about 1/4 of the time from run-job.sh when
starting jobs:
[yarnmaster01] out: 2015-11-17 14:56:00 KafkaSystemAdmin$ [INFO] Got metadata:
Map(__samza_coordinator_t-key-grouper_dev -> SystemStreamMetadata
[strea
