Ask Your Question
1

Rest API error:com.streamsets.datacollector.execution.runner.common.PipelineRunnerException: CONTAINER_0102 - Cannot change state from RUNNING to STARTING. Therefore the resource URL does not post and data.

asked 2020-02-24 09:18:43 -0500

anonymous user

Anonymous

updated 2020-02-24 14:35:28 -0500

Hi I have a pipeline that collect data for kafka producer. The pipeline is as follows: httpClient--->javascript Evaluator ---> Kafka Producer

The HTTP Client configuration is as follows:

  • Resource Url : https://example.com/api/Devices/Thres...
  • Mode: Polling
  • Polling Interval (ms) : 50000
  • HTTP Method
  • Max Batch Size (records) : 2000000
  • Batch Wait Time (ms) :2000 Data format Configuration:

  • Data Format :JSON

  • Max Object Length (chars): 2147483647
  • List item

But it is not retrieving data in Resource URL https://example.com/api/Devices/Thres... instead it is showing the following error. Any idea how to solve this problem. Before once I increased the - Max Object Length (chars): 2147483647 the problem was solved but again when I added new devices the same problem popped us. Please any suggestion.

here is the complete trace of the error log:

at com.streamsets.pipeline.http.MDCFilter.doFilter(MDCFilter.java:47)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:690)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:513)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:503)
at com.streamsets.lib.security.http.LimitedMethodServer.handle(LimitedMethodServer.java:41)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
at org.eclipse.jetty.util.thread ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2020-02-24 11:24:18 -0500

metadaddy gravatar image

Cannot change state from RUNNING to STARTING means that you are trying to start a pipeline that is already running. You can check the state of the pipeline with GET /rest/v1/pipeline/{pipelineId}/status.

e.g.

% curl -u admin:admin -H "X-Requested-By:sdc" http://localhost:18630/rest/v1/pipeline/SalesforceCDC9d5ce4c4-d877-4145-8b67-40c23bf9cefe/status
{
  "pipelineId" : "SalesforceCDC9d5ce4c4-d877-4145-8b67-40c23bf9cefe",
  "rev" : "0",
  "user" : "admin",
  "status" : "RUNNING",
  "message" : null,
  "timeStamp" : 1582564847836,
  "attributes" : {
    "IS_REMOTE_PIPELINE" : false,
    "RUNTIME_PARAMETERS" : null,
    "INTERCEPTOR_CONFIGS" : [ ]
  },
  "executionMode" : "STANDALONE",
  "metrics" : null,
  "retryAttempt" : 0,
  "nextRetryTimeStamp" : 0,
  "name" : "SalesforceCDC9d5ce4c4-d877-4145-8b67-40c23bf9cefe"
}

If I try to start it, I'll get the same error as you:

% curl -u admin:admin -H "X-Requested-By:sdc" http://localhost:18630/rest/v1/pipeline/SalesforceCDC9d5ce4c4-d877-4145-8b67-40c23bf9cefe/start -X POST
{
  "RemoteException" : {
    "message" : "com.streamsets.datacollector.execution.runner.common.PipelineRunnerException: CONTAINER_0102 - Cannot change state from RUNNING to STARTING",
    "errorCode" : "CONTAINER_0102",
    "localizedMessage" : "CONTAINER_0102 - Cannot change state from RUNNING to STARTING",
    "exception" : "PipelineRunnerException",
    "javaClassName" : "com.streamsets.datacollector.execution.runner.common.PipelineRunnerException",
    "antennaDoctorMessages" : [ ],
    "stackTrace" : "com.streamsets.datacollector.execution.runner.common.PipelineRunnerException: CONTAINER_0102 - Cannot change state from RUNNING to STARTING\n\tat com.streamsets.datacollector.execution.runner.standalone.StandaloneRunner.checkState(StandaloneRunner.java:682)\n\tat ..."
  }
}
edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2020-02-24 09:18:43 -0500

Seen: 34 times

Last updated: Feb 24