Quickstart Tutorial Fails with Extension "druid-s3-extensions" enabled

Affected Version

0.22.0

Description

Steps to reproduce:

• Download a fresh 0.22.0 installation.
• In conf/druid/single-server/micro-quickstart/_common/common.runtime.properties in druid.extensions.loadList add "druid-s3-extensions"
• Start the quickstart: ./bin/start-micro-quickstart
• Follow the steps to ingest the wiki-ticker test data from the quickstart: https://druid.apache.org/docs/latest/tutorials/index.html#step-4-load-data
• The job reports FAILED. I’ve attached the logs to this issue (index_parallel_wiki-ticker_hjmbmoen_2021-12-08T12:22:42.895Z.log)

The first exception is this one: java.lang.reflect.InaccessibleObjectException: Unable to make public long[] com.sun.management.internal.HotSpotThreadImpl.getThreadAllocatedBytes(long[]) accessible: module jdk.management does not "exports com.sun.management.internal" to unnamed module @79dc5318 but the task continues after that, until: WARN [main] com.amazonaws.util.EC2MetadataUtils - Unable to retrieve the requested metadata (/latest/dynamic/instance-identity/document). Failed to connect to service endpoint: com.amazonaws.SdkClientException: Failed to connect to service endpoint:

I would expect the task to finish successfully.

[adwk67]

Having looked at this in a bit more detail, it seems that the s3-extension requires - at a minimum - a value for druid.s3.endpoint.url in the runtime properties. What is not so clear from the documentation is that this cannot be provided via the console (in contrast to other things like bucket names and access/storage keys). Maybe a comment to this affect could be added to the s3-extension docs.

[maltesander]

I could reproduce that problem for druid 0.22.1. with:

openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07)
OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)

The quickstart tutorial does not work if the s3-extension is loaded but not configured.

The quickstart tutorial does work with loaded s3-extension and proper s3 credentials.

Is that behavior expected?