Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.0.0
-
Untriaged
-
-
Unknown
Description
- Create 2node cluster kv and eventing
- Create handler which creates times and timer execution will create new timer with same refrence
function OnUpdate(doc,meta) {
|
var expiry = new Date();
|
expiry.setSeconds(expiry.getSeconds() + 150);
|
|
|
var context = {docID : meta.id, random_text : "e6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh0R7Aumoe6cZZGHuh07Aumoe6cZZGHuh07Aumoe6cZZGHuh07Aumoe6"};
|
createTimer(timerCallback, expiry, meta.id, context);
|
}
|
function timerCallback(context) {
|
dst_bucket[context.docID] = context.random_text;
|
var expiry = new Date();
|
expiry.setSeconds(expiry.getSeconds() + 150);
|
createTimer(timerCallback, expiry, context.docID, context);
|
}
|
- create 1 doc in source , i can see 2051 doc in metadata (timer got created)
- seeing 1 doc in destination and timer creation in metadata also but the new timer is not even fired since 5 min
Attachments
Issue Links
- is a backport of
-
MB-39078 Timer not getting fired when created during timer execution
- Closed