Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Worker does not get jobs if job payload in size ~65480-65510 bytes #55

Open
dycode opened this issue Jan 17, 2017 · 5 comments
Open

Worker does not get jobs if job payload in size ~65480-65510 bytes #55

dycode opened this issue Jan 17, 2017 · 5 comments
Labels

Comments

@dycode
Copy link

dycode commented Jan 17, 2017

When payload size is around 65480-65510 bytes worker does not get jobs from gearman. Example:

var gearmanode = require('gearmanode');
var client = gearmanode.client({ port: 4730 });

var x = '';
for (var i = 0; i < 65700; i++) {
    x += 'a';

    if (x.length > 65480)
        client.submitJob('testsLength', x, { background: true, unique: x.length });
}


var worker = gearmanode.worker({ port: 4730 });

worker.addFunction('testsLength', (job) => {
    console.log('Length: ' + job.payload.toString().length);
    job.workComplete('completed');
});

After running this code, you will see that not all jobs are completed. My tests shows that only jobs with sizes in ~65480-65510 are not received to worker. I can reproduce this in several computers.

  • Gearman v1.1.12
  • Node version v5.2 and v7.0<= (have not tried other versions)
  • Gearmanode v0.2.0
@veny veny added the bug label Feb 9, 2017
@veny
Copy link
Owner

veny commented Feb 9, 2017

  • I can reproduce it
  • there is not a simple reason/problem visible at once
  • more analysis needed

@martynas19942
Copy link

I have this problem too, please fix it. Maybe some one have quick solution?

@donatas-dycode
Copy link

@veny I can also reproduce it and have the same issue. Maybe some fix commming up soon?

@AndrejLukasevic
Copy link

Same here.

@paulius-zubavicius
Copy link

Hi, it seems I got the same. Workarounds it is not a solution :( How long it could take? Please help

martynas19942 added a commit to martynas19942/GearmaNode that referenced this issue Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants