-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
I seem to be unable to connect to Vertica 25.3 using this driver whereas the legacy driver works fine.
Problem
vertica-nodejs driver hangs for 15+ seconds during connection initialization and is ultimately unable to connect, while the legacy vertica driver (wvanbergen/node-vertica) connects in ~113ms to the same database with identical credentials.
I see that Vertica 24.0+ has default timeout limits, I tried setting ALTER DATABASE protobi_db SET IdleTimeoutInitializingConnectionsMs = 0; and ALTER DATABASE protobi_db SET IdleTimeoutInitializingConnectionsMs = 30000 to no avail.
Side-by-Side Comparison
✓ Legacy driver (wvanbergen/node-vertica) - WORKS:
const Vertica = require('vertica');
Vertica.connect({
host: 'db-test.mydomain.com',
port: 5433,
user: 'test_user',
password: '**********',
database: 'my_db'
}, function(err, connection) {
// ✓ CONNECTED in 113ms
connection.query('SELECT version() AS version', function(err, result) {
console.log(result.rows[0][0]);
// Vertica Analytic Database v25.3.0-0
});
});
✗ Official driver (vertica-nodejs) - HANGS:
const { Client } = require('vertica-nodejs');
const client = new Client({
host: 'db-test.mydomain.com',
port: 5433,
user: 'test_user',
password: '**********',
database: 'my_db'
});
await client.connect();
// ✗ Hangs for 15+ seconds, never completes
Environment
- vertica-nodejs: v1.0.3
- Node.js: v20.19.5
- Vertica Server: v25.3.0-0
- IdleTimeoutInitializingConnectionsMs: 0 (disabled - no server-side timeout)
Impact
Connection initialization fails, what might I be missing?
Notes
- Server timeout has been disabled (IdleTimeoutInitializingConnectionsMs = 0) or set high (30000)
- Driver appears to hang indefinitely, not hitting any timeout
- Tested with explicit tls_mode: 'disable' - same behaviorMetadata
Metadata
Assignees
Labels
No labels