Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusing config externalS3.host/port #99

Open
hakeedra opened this issue Jun 26, 2024 · 4 comments
Open

Confusing config externalS3.host/port #99

hakeedra opened this issue Jun 26, 2024 · 4 comments

Comments

@hakeedra
Copy link

hakeedra commented Jun 26, 2024

externalS3.port not used no matter what value is configured.
externalS3.host should contains hostname and port, or else pod throw exception if minio deployed in same namespace.

datacoord error log:
[2024/06/26 06:34:52.708 +00:00] [ERROR] [datacoord/server.go:548] ["chunk manager init failed"] [error="Endpoint url cannot have fully qualified paths."] [stack="github.com/milvus-io/milvus/internal/datacoord.(*Server).newChunkManagerFactory\n\t/go/src/github.com/milvus-io/milvus/internal/datacoord/server.go:548\ngithub.com/milvus-io/milvus/internal/datacoord.(*Server).initDataCoord\n\t/go/src/github.com/milvus-io/milvus/internal/datacoord/server.go:348\ngithub.com/milvus-io/milvus/internal/datacoord.(*Server).Init\n\t/go/src/github.com/milvus-io/milvus/internal/datacoord/server.go:334\ngithub.com/milvus-io/milvus/internal/distributed/datacoord.(*Server).init\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/service.go:129\ngithub.com/milvus-io/milvus/internal/distributed/datacoord.(*Server).Run\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/service.go:256\ngithub.com/milvus-io/milvus/cmd/components.(*DataCoord).Run\n\t/go/src/github.com/milvus-io/milvus/cmd/components/data_coord.go:52\ngithub.com/milvus-io/milvus/cmd/roles.runComponent[...].func1\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:113"] [2024/06/26 06:34:52.708 +00:00] [ERROR] [datacoord/service.go:130] ["dataCoord init error"] [error="Endpoint url cannot have fully qualified paths."] [stack="github.com/milvus-io/milvus/internal/distributed/datacoord.(*Server).init\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/service.go:130\ngithub.com/milvus-io/milvus/internal/distributed/datacoord.(*Server).Run\n\t/go/src/github.com/milvus-io/milvus/internal/distributed/datacoord/service.go:256\ngithub.com/milvus-io/milvus/cmd/components.(*DataCoord).Run\n\t/go/src/github.com/milvus-io/milvus/cmd/components/data_coord.go:52\ngithub.com/milvus-io/milvus/cmd/roles.runComponent[...].func1\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:113"] [2024/06/26 06:34:52.708 +00:00] [ERROR] [components/data_coord.go:53] ["DataCoord starts error"] [error="Endpoint url cannot have fully qualified paths."] [stack="github.com/milvus-io/milvus/cmd/components.(*DataCoord).Run\n\t/go/src/github.com/milvus-io/milvus/cmd/components/data_coord.go:53\ngithub.com/milvus-io/milvus/cmd/roles.runComponent[...].func1\n\t/go/src/github.com/milvus-io/milvus/cmd/roles/roles.go:113"] panic: Endpoint url cannot have fully qualified paths.

configma/milvus/default.yaml
minio: address: minio port: 9000 accessKeyID: admin secretAccessKey: admin.password useSSL: false bucketName: milvus rootPath: / useIAM: false cloudProvider: minio iamEndpoint: region: useVirtualHost: false

pod/configs/milvus.yaml
minio: accessKeyID: admin address: minio bucketName: milvus cloudProvider: minio iamEndpoint: null listObjectsMaxKeys: 0 logLevel: fatal port: 9000 region: null requestTimeoutMs: 10000 rootPath: / secretAccessKey: admin.password ssl: tlsCACert: /path/to/public.crt useIAM: false useSSL: false useVirtualHost: false

@LoveEachDay
Copy link
Collaborator

@hakeedra Known issue, milvus will use environment like MINIO_PORT and MINIO_HOST over the configuration yaml file. Just deploy minio service to another namespace if not installed with milvus.

@hakeedra
Copy link
Author

@LoveEachDay Currently resolved by configuring externalS3.host: minio:9000

@LoveEachDay
Copy link
Collaborator

LoveEachDay commented Jun 26, 2024

@hakeedra You should set externalS3.host to minio instead of minio:9000.

@hakeedra
Copy link
Author

@LoveEachDay First of all, I want to install Minio and Milvus in the same namespace. If I set externalS3.host to minio, it throws an exception. However, if I set it to minio:9000, it works. If a future version fixes this bug, I will revert the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants