Trying to connect to Redshift but getting 'Unable ...
# all-things-deployment
m
Trying to connect to Redshift but getting 'Unable to emit metadata to DataHub GMS'. What would be the cause for this?
d
Hi - Could you try setting sink.config.max_threads: 1 in your config and try it again? this thread might be helpful https://datahubspace.slack.com/archives/CUMUWQU66/p1684170546906109?thread_ts=1682332234.663259&cid=CUMUWQU66
m
Thanks @delightful-ram-75848. Will try this @brash-plumber-28960 @bitter-spoon-14931 FYI
b
@delightful-ram-75848 where do we find the "sink.config.max_threads: 1" is it in datahub deployment file or anywhere else? It's bit new for us
d
How are you deploying your datahub instance? is it quickstart or helm chart?
m
@delightful-ram-75848 using helm chart
@delightful-ram-75848 Trust you are well! Sorry but would it be possible to let us know where this setting needs to be made. Just FYI, we are ingesting metadata from Redshift
a
m
@delightful-ram-75848 Thanks. Sorry but where can we find this YAML recipe. Very new to Datahub
b
Hi @delightful-ram-75848 we have added the max_thread=1 in YAML file and updated. But still we see that intermittently when we run ingestion source on Redshift; error as follows; { "error": "Unable to emit metadata to DataHub GMS: javax.persistence.PersistenceException: Error when batch flush on sql: update metadata_aspect_v2 set metadata=?, createdOn=?, createdBy=?, createdFor=?, systemmetadata=? where urn=? and aspect=? and version=?", "info": { "exceptionClass": "com.linkedin.restli.server.RestLiServiceException", "message": "javax.persistence.PersistenceException: Error when batch flush on sql: update metadata_aspect_v2 set metadata=?, createdOn=?, createdBy=?, createdFor=?, systemmetadata=? where urn=? and aspect=? and version=?", "status": 500, "id": "urnlidataset:(urnlidataPlatform:redshift,dev.aso_schema.${google_keyword},PROD)" } }