How do I create a locking/check-out mechanism in mongo?
I have multiple node.js instances accessing the same mongodb all working on the same tasks. I want to make sure that the same task isn't run at the save time. Is there a "best practices" approach to checking out a task?
This is what I have so far but it's not the best approach because I still seem to have duplicate messages being sent.
What am I doing wrong? How can I do this better?
// Check if there is a locked message.
const cutoff = moment()
.subtract(3, "minute")
.toDate();
let message = await Message.findOneAndUpdate(
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
disable: {$ne: true}, // Message is not disabled
messageSent: {$ne: true}, // Message is not sent
$or: [
{
lockedAt: null // If the message is not locked (null)
},
{
lockedAt: {$exists: false} // If the message is not locked (doesn't exist)
},
{
lockedAt: {$lte: cutoff} // If it was locked more that 3 minutes ago
}
]
},
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
lockedAt: moment().toDate() // Check out the message with the current date
},
{upsert: true, new: true}
);
// If no message doc is returned, that means it's disabled, has already been sent or is being sent.
if (!message) {
return;
}
node.js mongodb mongoose
add a comment |
I have multiple node.js instances accessing the same mongodb all working on the same tasks. I want to make sure that the same task isn't run at the save time. Is there a "best practices" approach to checking out a task?
This is what I have so far but it's not the best approach because I still seem to have duplicate messages being sent.
What am I doing wrong? How can I do this better?
// Check if there is a locked message.
const cutoff = moment()
.subtract(3, "minute")
.toDate();
let message = await Message.findOneAndUpdate(
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
disable: {$ne: true}, // Message is not disabled
messageSent: {$ne: true}, // Message is not sent
$or: [
{
lockedAt: null // If the message is not locked (null)
},
{
lockedAt: {$exists: false} // If the message is not locked (doesn't exist)
},
{
lockedAt: {$lte: cutoff} // If it was locked more that 3 minutes ago
}
]
},
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
lockedAt: moment().toDate() // Check out the message with the current date
},
{upsert: true, new: true}
);
// If no message doc is returned, that means it's disabled, has already been sent or is being sent.
if (!message) {
return;
}
node.js mongodb mongoose
add a comment |
I have multiple node.js instances accessing the same mongodb all working on the same tasks. I want to make sure that the same task isn't run at the save time. Is there a "best practices" approach to checking out a task?
This is what I have so far but it's not the best approach because I still seem to have duplicate messages being sent.
What am I doing wrong? How can I do this better?
// Check if there is a locked message.
const cutoff = moment()
.subtract(3, "minute")
.toDate();
let message = await Message.findOneAndUpdate(
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
disable: {$ne: true}, // Message is not disabled
messageSent: {$ne: true}, // Message is not sent
$or: [
{
lockedAt: null // If the message is not locked (null)
},
{
lockedAt: {$exists: false} // If the message is not locked (doesn't exist)
},
{
lockedAt: {$lte: cutoff} // If it was locked more that 3 minutes ago
}
]
},
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
lockedAt: moment().toDate() // Check out the message with the current date
},
{upsert: true, new: true}
);
// If no message doc is returned, that means it's disabled, has already been sent or is being sent.
if (!message) {
return;
}
node.js mongodb mongoose
I have multiple node.js instances accessing the same mongodb all working on the same tasks. I want to make sure that the same task isn't run at the save time. Is there a "best practices" approach to checking out a task?
This is what I have so far but it's not the best approach because I still seem to have duplicate messages being sent.
What am I doing wrong? How can I do this better?
// Check if there is a locked message.
const cutoff = moment()
.subtract(3, "minute")
.toDate();
let message = await Message.findOneAndUpdate(
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
disable: {$ne: true}, // Message is not disabled
messageSent: {$ne: true}, // Message is not sent
$or: [
{
lockedAt: null // If the message is not locked (null)
},
{
lockedAt: {$exists: false} // If the message is not locked (doesn't exist)
},
{
lockedAt: {$lte: cutoff} // If it was locked more that 3 minutes ago
}
]
},
{
listingID: listing._id,
messageRuleID: messageRule._id,
reservationID: reservation._id,
lockedAt: moment().toDate() // Check out the message with the current date
},
{upsert: true, new: true}
);
// If no message doc is returned, that means it's disabled, has already been sent or is being sent.
if (!message) {
return;
}
node.js mongodb mongoose
node.js mongodb mongoose
edited Nov 26 '18 at 14:51
Tom Krones
asked Nov 26 '18 at 14:36
Tom KronesTom Krones
5,718125190
5,718125190
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53483407%2fhow-do-i-create-a-locking-check-out-mechanism-in-mongo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53483407%2fhow-do-i-create-a-locking-check-out-mechanism-in-mongo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown