Troubleshooting Streaming

This topic covers various issues related to Oracle Cloud Infrastructure Streaming and how you can address them. Details about common API errors that all services return are detailed in API errors.

Troubleshooting Access and Permissions

Request returns a "Processing exception while communicating" message and a -1 error

When you use the Streaming client to send a request, you might see the following error message:

Caused by: com.oracle.bmc.model.BmcException: (-1, null, false) Processing exception while communicating to:
https://streams.<region>.streaming.oci.oraclecloud.com (outbound opc-request-id: <opc_request_id>)
        at com.oracle.bmc.http.internal.RestClient.convertToBmcException(RestClient.java:540)
        at com.oracle.bmc.http.internal.RestClient.get(RestClient.java:96)
        at com.oracle.pic.oss.api.StreamAdminClient.getStream(StreamAdminClient.java:292)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMeth

This error is related to the client. The Streaming service doesn't send it, which means that the request never made it to the service.

Request returns a NotAuthorizedOrNotFound message and a 404 error

When you send a request to Streaming, you might see an error message similar to the following:

com.oracle.bmc.model.BmcException: (404, NotAuthorizedOrNotFound,false)
Unknown stream ocid1.stream.oc1.phx.exampleuniqueID.
(opc-request-id: <opc_request_id>)

A 404 error usually means that the needed resource isn't found or that you don't have access to it. An example is when the stream-push policy is missing, or the stream has been deleted or is not accessible. Ensure that all the permissions are correctly set.

Request returns a "Not Found" message and a 404 error

When you send a request to Streaming, you might see an error message similar to the following:

Response { type: “cors”, url: “https://streams.<region>.streaming.oci.oraclecloud.com/20180418/streams?
compartmentId=ocid1.tenancy.oc1..exampleuniqueID&limit=10&page=&sortBy=TIMECREATED&sortOrder=desc&lifecycleState=“,
redirected: false, status: 404, ok: false, statusText: “Not Found”, headers: Headers, bodyUsed: false }
console.js:35

This error indicates a permission-related issue. Ensure that all the permissions are correctly set.

Request returns a "The following tag namespaces/keys are not authorized or not found" message

This error suggests that there is a tag on the stream that your user is not authorized to use. Remove the tag or authorize the user. See Resource Tags for more information.

Request returns a "bad handshake" message and a 104 error

When you send a request to Streaming, you might see an error message similar to the following:

SSLError(SSLError(\"bad handshake: SysCallError(104, 'ECONNRESET'.))

This error typically means that your system doesn't have the CA that the certificates were signed by. You may need to install the ca-certificates package on your host or pull the CA certificate from the target endpoint and import it into your system trust store by using update-ca-trust command.

Troubleshooting Limits and Throttling

Limits on Streaming Resources describes the service and resource limits that might result in the following scenarios.

Partial failures

Streaming supports partial failures caused by throttling, per partition. When a partial failure occurs, the service returns a 200 status code and indicates the failure in the response payload.

If an entire request is throttled, Streaming returns a 429 status code.

Request returns a "Too many requests message" and a 429 error

When you send a request to Streaming, you might see an error message that includes the following:

(429, Too many requests)

This error is caused by the throttling mechanism in the service. It indicates that too many requests per second per partition are being received.

If this error occurs on the producer side, ensure that the total data write rate of 1 MB per second per partition is not exceeded by:

Lowering the amount of requests per second.
Decreasing message size by batching.

If this error occurs on the consumer side, ensure that:

The cursor uses commitOnGet(true).
You reduce the number of requests, keeping in mind that the maximum data read rate is 5 GET requests per second per partition per consumer group.
The limit is set for each GET request.

Request returns a "Request size is limited to 1 MiB" message and a 400 error

When you send a request to Streaming, you might see an error message similar to the following:

Exception in thread "main" com.oracle.bmc.model.BmcException: (400, InvalidParameter, false) Request size is limited to 1 MiB. (opc-request-id: <opc_request_id>>)
    at com.oracle.bmc.http.internal.ResponseHelper.throwIfNotSuccessful(ResponseHelper.java:120)
    at com.oracle.bmc.http.internal.ResponseConversionFunctionFactory$ValidatingParseResponseFunction.apply(ResponseConversionFunctionFactory.java:86)
    at com.oracle.bmc.http.internal.ResponseConversionFunctionFactory$ValidatingParseResponseFunction.apply(ResponseConversionFunctionFactory.java:82)
    at com.oracle.bmc.streaming.internal.http.PutMessagesConverter$1.apply(PutMessagesConverter.java:68)
    at com.oracle.bmc.streaming.internal.http.PutMessagesConverter$1.apply(PutMessagesConverter.java:54)
    at com.oracle.bmc.streaming.StreamClient.putMessages(StreamClient.java:466)

This error occurs because the PutMessages call sent to the service is too large. The size must be less than or equal to 1 MB.

Stream creation fails with a "You exceed the number of allowed partitions" message

This error occurs when you try to create more partitions than your tenancy is allowed. You can request an increase.

Troubleshooting Production and Consumption

Messages do not appear in the Console after publishing them to a stream

You must click the Refresh button to show the first 100 messages. See Using the Console to show recent messages for more information.

Because streams using private endpoints are not accessible from the internet, their messages do not display in the Console.

Consumers receive a "The cursor is outside the retention period and is now invalid" message and a 400 error

When requesting messages from a stream, a consumer might see an error message like the following:

(400, InvalidParameter, false) The cursor is outside the retention period and is now invalid

This error means that the offsets stored for one or more of your partitions has fallen behind the trim horizon. Some data loss has occurred, and the data that was produced to the stream is no longer available for consumption. Data that is outside the retention period can't be recovered. At this point, the administrator must decide the best course of action, given the use case.

This error can happen if you are not committing offsets regularly, or if your consumer falls behind constantly. For more information, see Getting Messages.

A manual call to the UpdateGroup method is required to reset the cursor for the instances within a consumer group.

Consumers receive a "Trying to commit unreserved partition" message and a 400 error

When requesting messages from a stream, a consumer that is part of a consumer group might see an error message like the following:

(400, InvalidParameter, false) Trying to commit unreserved partition

This error means that the consumer tried to commit an offset for a partition that was not reserved for that particular consumer. This error can happen when the consumer appears to have timed out, partitions are rebalanced to another consumer, and then the consumer tries to commit offsets. The default timeout is 30 seconds for a consumer. Timeouts for a consumer can be extended by sending a heartbeat. See Consuming as a Group for more information.

This error can also occur when pipelining (commitOnGet=false) and no commits occurred for a significant amount of time (more than 30 seconds).

Request fails with an "Unable to parse JSON body" message and a 400 error

When you send a request to Streaming, you might see an error message similar to the following:

(400, Unable to parse JSON body)

This error generally means that the JSON body contains an entry in an invalid format.

Ruby SDK requests fail with an "Unable to parse JSON body" message and a 400 error

When you send a request to Streaming using the Ruby SDK, you might see an error message similar to the following:

Unable to parse JSON body, 'status': 400, 'code': 'InvalidParameter'

The Ruby SDK doesn't do any encoding. You must use Base64 to encode the strings that are sent in the key and value fields. For example:

msgs << OCI::Streaming::Models::PutMessagesDetailsEntry.new(key: Base64.strict_encode64(k), value: Base64.strict_encode64(record.to_json))
 
if msgs.length > 0
    res = @oss_client.put_messages(@stream_ocid, OCI::Streaming::Models::PutMessagesDetails.new(messages: msgs))
end