sagemaker-python-sdk icon indicating copy to clipboard operation
sagemaker-python-sdk copied to clipboard

Sagemaker local client invoke_endpoint returns different response than non local counterpart

Open gpiotti opened this issue 1 year ago • 0 comments

Sagemaker local client invoke_endpoint method returns a different response than using the boto3 runtime_client, so it makes debugging difficult in local mode, because the same code wouldn't work in production. The missing part is the ResponseMetadata key in the payload it just returns Body and ContentType I would want to access ResponseMetadata, InvokedProductionVariant and other related metadata in local mode

To reproduce

  1. Have a local container running the sagemaker model
  2. Invoke the endpoint with sagemaker local client
sagemaker_session = LocalSession()
sagemaker_session.config = {"local": {"local_code": True}}
sm_client = sagemaker_session.sagemaker_runtime_client
response = sm_client.invoke_endpoint(
    EndpointName="local-endpoint-name",
    ContentType="application/json",
    Body=json.dumps(payload),
)
response["ResponseMetadata"]["HTTPStatusCode"] <- Fails

Expected behavior the local client should return the same response as the non-local client local client

{"Body": "foo", "ContentType": "bar"}

non-local client

{"Body": "foo", "ContentType": "bar", "ResponseMetadata": {"foo": "bar"}}

System information A description of your system. Please provide:

  • SageMaker Python SDK version: 2.108.0
  • Python version: 3.7.10
  • CPU or GPU: CPU
  • Custom Docker image (Y/N): Y

gpiotti avatar Sep 05 '22 23:09 gpiotti