nsqd: arbitrary 1 hour limit for REQ timeout

[AlekSi]

May it be increased?

[mreiferson]

Chosen arbitrarily 😁

I would be amenable to a pull request that made it configurable.

[tj]

personally I wouldn't mind seeing the upper limits removed completely, but I can see how they would be handy for typos :D

[mreiferson]

I like the idea of things being bounded (where possible), but configurable. This was just an oversight and I'm fine with making it configurable.

I think it's always better if the user chooses a higher limit for something while packaged with a sane but opinionated default.

[mreiferson]

see #352

[AlekSi]

@mreiferson We (I and @AlphaB) would be very grateful if you make a next patch release with this fix.

[mreiferson]

@AlekSi definitely, we're figuring out what we want in the next release... soon 😁

[AlekSi]

@mreiferson I mean, if you are going to make a big release, please make a small one with this one small sweet fix before, it will make our life a lot easier.

[mreiferson]

@AlekSi duly noted. I'm not sure I even want to know why you want to requeue things for more than an hour though! 😄

[AlekSi]

As workaround for #293 (support deferred PUB).

[liaojianqi]

@mreiferson Execuse me, but would you mind to explain why one hour is a "a sane default"?

[jehiah]

@liaojianqi the use-case nsq targets is a "A realtime distributed messaging platform".

p.s. please use forums other than 5 year old closed issues to discuss details of nsq.