influxdb icon indicating copy to clipboard operation
influxdb copied to clipboard

[v3] InfluxDB 3.5 error: `File name too long`

Open caiqinwei26-byte opened this issue 2 months ago • 3 comments

When restarting InfluxDB 3.5, the following error occurs. After deleting the wal folder, it can start successfully. What is the specific cause?

{ code: 36, kind: InvalidFilename, message: "File name too long" }, path: "/var/lib/influxdb3/data/my-node-0/dbs/airship___airship_loan_failInfo_pv-421/; uncategorized SQLException for SQL %5B%5D; SQL state %5BHY000%5D; error code %5B1105%5D; dial tcp4 127.0.0.1:9999: connect: connection refused; nested exception is java.sql.SQLException: dial tcp4 127.0.0.1:9999: connect: connection refused, retryable%5C=null%7D%7D-2/2025-10-30/20-00/0003247624.parquet#1" } }), sleeping and retrying...\n","stream":"stdout","time":"2025-10-31T02:34:10.413486655Z"}

caiqinwei26-byte avatar Oct 31 '25 08:10 caiqinwei26-byte

@caiqinwei26-byte -- can you provide the surrounding logs from influxdb 3.5?

It is telling you the error: "File name too long". Are you on windows?

In version 3.6, we removed the db name and table name from the path naming format. So airship___airship_loan_failInfo_pv won't appear in 3.6 and newer. That will shorten all your paths.

I recommend upgrading.

philjb avatar Nov 04 '25 19:11 philjb

linux When upgrading to InfluxDB 3.6, will my historical data be affected, or do I need to rewrite the data?

caiqinwei26-byte avatar Nov 10 '25 12:11 caiqinwei26-byte

Existing data at existing paths will continue to work in 3.6 as they did in 3.5. No migration or rewrite/reingest is needed for the path format change. New data in 3.6 will get the new path scheme. Old data will continue to work as the catalog contains full paths.

philjb avatar Nov 10 '25 16:11 philjb