[Bug]: job not running in kubernetes Pod

[prasanna3000]

Version

4.11.4

Platform

NodeJS

What happened?

I am trying to run a task using bullmq, its working as expected in local but when the code is deployed to kubernetes pod jobs gets added but doesn't seem to perform anything after that.

I am using nodejs: v16.20.2

ANy help would be appreciated.

How to reproduce.

const { Worker, Queue } = require('bullmq');

// Create a BullMQ queue
const queue = new Queue('math');

// Define a task that adds two numbers
const addNumbers = (job) => {
  const { num1, num2 } = job.data;
  const result = num1 + num2;
  return Promise.resolve(result);
};

// Create a Worker to process jobs
const worker = new Worker('math', addNumbers);

// Add a delayed job to the queue
const jobData = { num1: 5, num2: 3 };
const delayInMilliseconds = 5000; // 5 seconds

// Add job to the queue
queue
  .add('add', jobData, { delay: delayInMilliseconds })
  .then((job) => {
    console.log(`Job ID ${job.id} added to the queue.`);
  })
  .catch((error) => {
    console.error(`Error adding job to the queue: ${error.message}`);
  });

// Event listener for completed jobs
queue.on('completed', (job) => {
  console.log(`Job ID ${job.id} completed with result: ${job.returnvalue}`);
});

// Event listener for job processing
queue.on('active', (job) => {
  console.log(`Job ID ${job.id} is being processed.`);
});

// Event listener for job added
queue.on('added', (job) => {
  console.log(`Job ID ${job.id} was added to the queue.`);
});

// Event listener for failed jobs in the queue
queue.on('failed', (job, error) => {
  console.error(`Job ID ${job.id} failed with error: ${error.message}`);
});

// Event listener for failed worker jobs
worker.on('failed', (job, error) => {
  console.error(`Worker for Job ID ${job.id} failed with error: ${error.message}`);
});

Relevant log output

it just logs the job Id <number> is added and nothing happens after that.

Code of Conduct

• I agree to follow this project's Code of Conduct

[manast]

I will move this to a discussion as it is not a bug, most likely a configuration issue.