Does pravega container works for controller's REST API?
See original GitHub issueProblem description I started a pravega container as standalone mode and try send REST API to it, but failed.
Problem location
I started pravega container with this command
docker run -it -e HOST_IP=10.62.130.162 -p 9090:9090 -p 12345:12345 -p 9091:9091 -p 10000:10000 pravega/pravega:latest standalone
Then I send a REST for test but failed.
[root@TestMachine ~]# curl http://10.62.130.162:9090/scops
HTTP/2 client preface string missing or corrupt. Hex dump for received bytes: 474554202f73636f707320485454502f312e310d0a557365
there is also same error printed in container log
Dec 13, 2017 5:29:02 AM io.grpc.netty.NettyServerTransport notifyTerminated
SEVERE: Transport failed
io.netty.handler.codec.http2.Http2Exception: HTTP/2 client preface string missing or corrupt. Hex dump for received bytes: 474554202f73636f707320485454502f312e310d0a557365
at io.netty.handler.codec.http2.Http2Exception.connectionError(Http2Exception.java:85)
at io.netty.handler.codec.http2.Http2ConnectionHandler$PrefaceDecoder.readClientPrefaceString(Http2ConnectionHandler.java:277)
at io.netty.handler.codec.http2.Http2ConnectionHandler$PrefaceDecoder.decode(Http2ConnectionHandler.java:217)
at io.netty.handler.codec.http2.Http2ConnectionHandler.decode(Http2ConnectionHandler.java:401)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:411)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:248)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:349)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:341)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:349)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:129)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:642)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:565)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:479)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:441)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
at java.lang.Thread.run(Thread.java:745)
I am not sure this is a bug for pravega container or my command syntax is incorrect?
Suggestions for an improvement
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Controller REST API - Exploring Pravega
Overview¶. List of admin REST APIs for the Pravega Controller service. ... If not specified only user created streams will be returned, string ......
Read more >Controller Service - Exploring Pravega
Each controller instance is capable of working independently and uses a shared persistent store as the source ... We use swagger to describe...
Read more >Controller Service - Exploring Pravega
The Controller is responsible for managing the Segment Store cluster. Controller manages the lifecycle of Segment Store nodes as they are added to/removed...
Read more >Client APIs - Exploring Pravega
The client library encapsulates the Wire Protocol that is used to convey requests and responses between Pravega clients and the Pravega service. Note...
Read more >Running Locally - Exploring Pravega
Controller REST APIs, however, are accessible from remote hosts/machines. ... The below command will download and run Pravega from the container image on ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
sorry for late response, @shrids your branch works fine! [root@TestMachine ~]# curl http://10.62.130.162:9091/v1/scopes {“scopes”:[{“scopeName”:“_system”}]}
Could you retry with the following steps once you are inside Pravega directory? This would ensure you are using the changes done in the pull request.