opensearch-project/OpenSearch

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

Open

#21323 opened on Apr 22, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (8,123 stars) (1,505 forks)batch import
Searchbuggood first issue

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.

Contributor guide

Tech stack
java
Domain
backendobservability
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Investigate how Lucene's PanamaVectorizationProvider logs are output to stderr. The fix may involve configuring Lucene's logging to use OpenSearch's logging framework, or filtering out these specific messages. Look at OpenSearch's logging configuration files and the Lucene initialization code in the server module.