使用Express-Cassandra创建表时遭遇OperationTimedOutError求助

Hey there, let's tackle this index creation timeout issue you're hitting with Express-Cassandra and Cassandra 3.9 on CentOS 6.0. I've run into similar quirks before, so here are some actionable fixes to try out:

Express-Cassandra lets you adjust timeout values to give index creation more breathing room. Update your model initialization code with extended timeouts in clientOptions:

const models = require('express-cassandra');
models.setDirectory(__dirname + '/models').bind(
    {
        clientOptions: {
            contactPoints: ['127.0.0.1'],
            protocolOptions: { port: 9042 },
            keyspace: 'your_keyspace',
            queryOptions: {
                consistency: models.consistencies.one,
                timeout: 60000 // Bump to 60 seconds (adjust based on your needs)
            },
            socketOptions: {
                connectTimeout: 60000, // Longer connection window
                readTimeout: 60000     // Extra time for index creation queries
            }
        },
        ormOptions: {
            createKeyspace: true,
            createTable: true
        }
    },
    function(err) {
        if(err) console.error('Model sync error:', err);
        else console.log('All models synced successfully');
    }
);

Index creation can drag on if your table is large or Cassandra is under-resourced—giving it more time often resolves the NoHostAvailableError during startup.

If timeouts still persist, bypass Express-Cassandra's index creation step by making the indexes directly in Cassandra first. Fire up cqlsh and run:

CREATE INDEX your_index_name ON your_target_table (your_column_name);

Then set createTable: false in your Express-Cassandra ormOptions so it doesn't attempt to recreate the index on app startup. This avoids the race condition where the ORM tries to create indexes before Cassandra is fully ready to process the request.

CentOS 6.0 is pretty long in the tooth, so let's make sure your Cassandra instance is running smoothly:

• Run nodetool status in the terminal—your node should show up as UN (Up/Normal). If it's DN (Down/Normal), Cassandra hasn't finished starting up yet.
• Check Cassandra's system log (usually at /var/log/cassandra/system.log) for errors related to memory pressure, disk I/O, or index creation failures. These are common culprits for timeouts.
• Ensure Cassandra has enough RAM allocated. For Cassandra 3.9, the minimum recommended heap size is 4GB—you can adjust this in /etc/cassandra/cassandra-env.sh.

Your Node.js (8.9.1) and Express-Cassandra (2.1.1) versions are quite outdated. While updates require testing, newer releases often fix timeout-related bugs:

• If possible, upgrade Node.js to a supported LTS version (like 14.x or 16.x) that's compatible with newer Express-Cassandra builds.
• Check the Express-Cassandra changelog—versions 2.2.x and above include fixes for index creation timeouts and connection stability.

If all else fails, wrap your model initialization in a retry loop to avoid manual restarts:

function initModels() {
    models.setDirectory(__dirname + '/models').bind(
        // Insert your client/orm options here
        {},
        function(err) {
            if(err && err.message.includes('NoHostAvailableError')) {
                console.log('Model init timed out—retrying in 5 seconds...');
                setTimeout(initModels, 5000);
            } else if(err) {
                console.error('Fatal model init error:', err);
            } else {
                console.log('Successfully initialized all models!');
            }
        }
    );
}

initModels();

This will automatically retry the initialization process whenever a timeout occurs, saving you the hassle of manual restarts.

内容的提问来源于stack exchange，提问作者James Malvi