Troubleshooting

I cannot identify the versions of Data Hub and MarkLogic Server installed in my service.

Use REST APIs or Gradle to return the versions of Data Hub and MarkLogic Server installed in your service.

Important: Gradle can only return version information for Data Hub 5.4.x and later versions.

Solutions:

REST APIs

You can use REST APIs to return the versions of Data Hub and MarkLogic Server installed in your service.

In the MarkLogic Data Hub Service Dashboard, click the service name in the Service column.
Create one or more service users.
Use REST APIs to return summary information about your service:
- To return the Data Hub version installed in your service, click the Staging endpoint and enter your service user login credentials. In your browser, use the following REST API:
```
 https://host-name:8010/v1/resources/mlHubversion
```
  Note: The mlHubversion REST API can be used for services running Data Hub 5.0.x and later versions.
  
  For details, see Data Hub Extensions to the REST Client API.
- To return the MarkLogic Server version installed in your service, click the Manage endpoint and enter your service user login credentials. In your browser, use the following REST API:
```
 https://host-name:8002/manage/v2
```
  The value of version is the MarkLogic Server version number.
  
  For details, see GET /manage/v2.

Gradle

You can use the hubVersion Gradle task to return the versions of Data Hub and MarkLogic Server installed in your service. This Gradle task can be used for services running Data Hub 5.4.x and later versions. For details, see Data Hub Gradle Tasks.

I cannot ingest documents using MLCP or DMSDK without losing some documents.

If you use MLCP or DMSDK for ingestion during auto-scaling events, a small number of documents might fail to insert into the database. In most cases, the client automatically retries multiple times to insert the documents into the database. For additional information about the failed documents, you can view the URIs of the failed documents in the logs.

Workaround:

Re-ingest your documents using MLCP, DMSDK, or another client, such as Gradle or Java API.

I cannot create a peered Data Hub Service (DHS) network.

Note: Make sure your peer role is correctly created before you continue with the following instructions. If you cannot create a peered DHS network, MarkLogic recommends first making sure your peer role is correct.

Your AWS Organization's master account might have one or more Service Control Policies (SCPs) enabled that block child accounts from peering with accounts external to your organization.

Workaround:

Temporarily disable SCPs that block external peering or disable other policies that block external peering.
After you successfully set up your peered DHS network, you can enable the previously disabled policies.