beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <>
Subject [jira] [Commented] (BEAM-2321) gRPC configuration failure using DataflowRunner and Bigtable
Date Thu, 18 May 2017 22:23:04 GMT


Daniel Halperin commented on BEAM-2321:

Please post full output of Maven dependency:list

> gRPC configuration failure using DataflowRunner and Bigtable
> ------------------------------------------------------------
>                 Key: BEAM-2321
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>    Affects Versions: 2.0.0
>            Reporter: Nigel Kilmer
>            Assignee: Daniel Halperin
> I'm attempting to run a pipeline that uses the DataflowRunner and writes to Bigtable
(v0.9.6.2). This exception is thrown (looks like it's when the BigtableSession is being created):
> java.lang.IllegalArgumentException: Jetty ALPN/NPN has not been properly configured.
> 	at io.grpc.netty.GrpcSslContexts.selectApplicationProtocolConfig(
> 	at io.grpc.netty.GrpcSslContexts.configure(
> 	at io.grpc.netty.GrpcSslContexts.configure(
> 	at io.grpc.netty.GrpcSslContexts.forClient(
> 	at
> 	at$000(
> 	at$
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> I can run the same pipeline without issue using the DirectRunner instead, and it was
also working for me using the 0.7.0 snapshot of Beam last week. I've already checked with
the cloud-bigtable-client project; they said that it should be working since I have a dependency
on netty_tcnative configured. The fact that the same pipeline works with the DirectRunner
and not with the DataflowRunner makes me think it's a DataflowRunner bug.
> My pipeline is pretty simple; it looks like this:
> Pipeline p = Pipeline.create(gcpOptions);
> p.apply(PubsubIO.readProtos(TestProto.class)
>     .fromSubscription(pubsubSubscription))
>   .apply(ParDo.of(new BigtableMutationTransform()))
>   .apply(BigtableIO.write().withBigtableOptions(bigtableOptionsBuilder).withTableId("table_id"));
> Let me know if you need more context.

This message was sent by Atlassian JIRA

View raw message