You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've installed openwhisk on test environment OpenShift Master:v3.7.44 . After deploying everything worked properly was able to run action ./wsk -i action invoke /whisk.system/utils/echo -p message hello -b
After waiting for about 1 hour reran the action and now obtain error: Unable to invoke action 'utils/echo': There was an internal server error. (code 21879). Is there further information on code 21879.
The following are log file images.
The controller logs is polluted with
[2018-09-10T19:51:39.689Z] [ERROR] [#sid_110] [MessageFeed] failed to commit ping consumer offset: org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
The text was updated successfully, but these errors were encountered:
I've installed openwhisk on test environment OpenShift Master:v3.7.44 . After deploying everything worked properly was able to run action ./wsk -i action invoke /whisk.system/utils/echo -p message hello -b
After waiting for about 1 hour reran the action and now obtain error: Unable to invoke action 'utils/echo': There was an internal server error. (code 21879). Is there further information on code 21879.
The following are log file images.
The controller logs is polluted with
[2018-09-10T19:51:39.689Z] [ERROR] [#sid_110] [MessageFeed] failed to commit ping consumer offset: org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
The text was updated successfully, but these errors were encountered: