From 4936f733d1cdd83d4ac209d6fa9b786c416ae4b7 Mon Sep 17 00:00:00 2001 From: chrislu Date: Sun, 23 Nov 2025 22:54:21 -0800 Subject: [PATCH] debug: add WARN logging to SeaweedOutputStream base constructor CRITICAL: None of our higher-level logging is appearing! - NO SeaweedFileSystemStore.createFile logs - NO SeaweedHadoopOutputStream constructor logs - NO FSDataOutputStream.getPos() override logs But we DO see: - WARN SeaweedOutputStream: PARQUET FILE WRITTEN (from close()) Adding WARN log to base SeaweedOutputStream constructor will tell us: 1. IF streams are being created through our code at all 2. If YES, we can trace the call stack 3. If NO, streams are being created through a completely different mechanism (maybe Hadoop is caching/reusing FileSystem instances with old code) --- .../src/main/java/seaweedfs/client/SeaweedOutputStream.java | 2 ++ 1 file changed, 2 insertions(+) diff --git a/other/java/client/src/main/java/seaweedfs/client/SeaweedOutputStream.java b/other/java/client/src/main/java/seaweedfs/client/SeaweedOutputStream.java index 2693dc098..bd035162c 100644 --- a/other/java/client/src/main/java/seaweedfs/client/SeaweedOutputStream.java +++ b/other/java/client/src/main/java/seaweedfs/client/SeaweedOutputStream.java @@ -47,6 +47,8 @@ public class SeaweedOutputStream extends OutputStream { public SeaweedOutputStream(FilerClient filerClient, final String path, FilerProto.Entry.Builder entry, final long position, final int bufferSize, final String replication) { + LOG.warn("[DEBUG-2024] SeaweedOutputStream BASE constructor called: path={} position={} bufferSize={}", + path, position, bufferSize); this.filerClient = filerClient; this.replication = replication; this.path = path;