a#
> L659-L691 is what you want to look at.
>
> - Bobby
>
>
>
> On Tuesday, June 27, 2017, 2:15:09 PM CDT, Kristopher Kane <
> kkane.l...@gmail.com> wrote:
>
>
> I should qualify the path there is the ZooKeeper znode for /storm/errors
>
>
>
> On Tue, J
I am able to reproduce the same behavior of STORM-2329 by using a single
worker HDFS writer that contains clock skew. This isn't the same mechanism
as seen by my users (Mechanism level: Failed to find any Kerberos tgt vs my
simulation Mechanism level: Clock skew too great (37) - PROCESS_TGS) but
I need some clarification on Kafka broker version support across Storm
branches.
storm-kafka-client uses the 'new' Kafka APIs
The master branch README of storm-kafka-client says that it ONLY supports
Kafka version .10 and later.
The 1.x branch README of storm-kafka-client says that it ONLY
Does anyone have any techniques for testing serializers that would only
surface when the serializer is uses in a multi-worker topology?
Kris
The fix appears to be in 2.x and beyond.
On Thu, Oct 13, 2016 at 10:29 AM, Jungtaek Lim <kabh...@gmail.com> wrote:
> Thanks for the great update. Which version of schema-registry resolves the
> issue?
>
> - Jungtaek Lim (HeartSaVioR)
>
> 2016년 10월 13일 (목) 오후 11:13,
/master/external/storm-hdfs/pom.xml#L205
but
will report if I do.
Kris
On Sun, Sep 11, 2016 at 1:31 PM, Kristopher Kane <kkane.l...@gmail.com>
wrote:
> This took a while as I could not get INFO logging to come out of the
> serializer in Kryo. The CachedSc
istry/client/
> CachedSchemaRegistryClient.java#L79
>
> On Tue, Sep 6, 2016 at 7:40 AM Kristopher Kane <kkane.l...@gmail.com>
> wrote:
>
>> Hi everyone.
>>
>> I have a simple topology that uses the Avro serializer (
>> https://github.com/apache/storm/bl
Hi everyone.
I have a simple topology that uses the Avro serializer (
https://github.com/apache/storm/blob/master/external/storm-hdfs/src/main/java/org/apache/storm/hdfs/avro/ConfluentAvroSerializer.java)
and writes to Elasticsearch.
The topology is like this:
Kafka (raw scheme) -> Avro
