opensearch-project/OpenSearch

[BUG] warning log entries (stderr) from lucene on startup

Open

#21.323 aberto em 22 de abr. de 2026

Ver no GitHub
 (6 comments) (0 reactions) (0 assignees)Java (1.505 forks)batch import
Searchbuggood first issuelucene

Métricas do repositório

Stars
 (8.123 stars)
Métricas de merge de PR
 (Mesclagem média 5d 9h) (266 fundiu PRs em 30d)

Description

Describe the bug

starting a fresh cluster leads to the following log entries:

{"type": "server", "timestamp": "2026-04-22T13:53:25,584+0000", "level": "WARN", "component": "stderr", "cluster.name": "test-opensearch", "node.name": "test-opensearch-0", "message": "Apr 22, 2026 1:53:25 PM org.apache.lucene.internal.vectorization.PanamaVectorizationProvider <init>" }
{"type": "server", "timestamp": "2026-04-22T13:53:25,585+0000", "level": "WARN", "component": "stderr", "cluster.name": "test-opensearch", "node.name": "test-opensearch-0", "message": "INFO: Java vector incubator API enabled; uses preferredBitSize=256; FMA enabled" }

note that these are written to stderr rather than going through any logging framework.

Related component

No response

To Reproduce

start a fresh cluster (i used the minimal distribution) and check the log

Expected behavior

no such WARN log entries which are not actual warnings (or at least do not state what would be wrong and are not actionable)

Additional Details

Plugins n/a

Screenshots n/a

Host/Environment (please complete the following information):

  • OS: linux
  • Version OpenSearch 3.6.0

Additional context they also seem to be coming from lucene rather than OpenSearch; nevertheless i'm reporting this here since you're more familiar with how you integrate lucene and whether/how this can/should be fixed downstream.

Guia do colaborador