Cypher count() returns values for non-existing nodes
As title says.
MATCH (n:Person) RETURN count(n)
returns
│"count(n)"│
│1481 │
But
MATCH (n:Person) RETURN n
returns
(no changes, no records)
I used the same query for multiple times without error, and this happened just now for no apparent reason.
This is driving me nuts - I don't think I've ever seen this problem.
I'm using neo4j 3.3.4.
p.s. I've just moved the retention log files to the other drive to make some free spaces - could this be the reason?
neo4j cypher
edited Nov 14 '18 at 12:18
Zico
1,75411620
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
add a comment |
As title says.
MATCH (n:Person) RETURN count(n)
returns
│"count(n)"│
│1481 │
But
MATCH (n:Person) RETURN n
returns
(no changes, no records)
I used the same query for multiple times without error, and this happened just now for no apparent reason.
This is driving me nuts - I don't think I've ever seen this problem.
I'm using neo4j 3.3.4.
p.s. I've just moved the retention log files to the other drive to make some free spaces - could this be the reason?
neo4j cypher
edited Nov 14 '18 at 12:18
Zico
1,75411620
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
add a comment |
As title says.
MATCH (n:Person) RETURN count(n)
returns
│"count(n)"│
│1481 │
But
MATCH (n:Person) RETURN n
returns
(no changes, no records)
I used the same query for multiple times without error, and this happened just now for no apparent reason.
This is driving me nuts - I don't think I've ever seen this problem.
I'm using neo4j 3.3.4.
p.s. I've just moved the retention log files to the other drive to make some free spaces - could this be the reason?
neo4j cypher
edited Nov 14 '18 at 12:18
Zico
1,75411620
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
As title says.
MATCH (n:Person) RETURN count(n)
returns
│"count(n)"│
│1481 │
But
MATCH (n:Person) RETURN n
returns
(no changes, no records)
I used the same query for multiple times without error, and this happened just now for no apparent reason.
This is driving me nuts - I don't think I've ever seen this problem.
I'm using neo4j 3.3.4.
p.s. I've just moved the retention log files to the other drive to make some free spaces - could this be the reason?
neo4j cypher
neo4j cypher
edited Nov 14 '18 at 12:18
Zico
1,75411620
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
edited Nov 14 '18 at 12:18
Zico
1,75411620
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
edited Nov 14 '18 at 12:18
Zico
1,75411620
edited Nov 14 '18 at 12:18
Zico
1,75411620
edited Nov 14 '18 at 12:18
Zico
1,75411620
1,75411620
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
asked Nov 14 '18 at 5:13
Jung RaphaelJung Raphael
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you mean the transaction log files, then that's likely the case. You should not ever touch the transaction logs yourself, you may have induced corruption in your graph.
Here's the documentation on transaction logs, including how to set your configuration properties to handle rotation and retention of the logs.
You may want to use the consistency checker to confirm the consistency of the database.
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
add a comment |
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%2f53293567%2fcypher-count-returns-values-for-non-existing-nodes%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you mean the transaction log files, then that's likely the case. You should not ever touch the transaction logs yourself, you may have induced corruption in your graph.
Here's the documentation on transaction logs, including how to set your configuration properties to handle rotation and retention of the logs.
You may want to use the consistency checker to confirm the consistency of the database.
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
add a comment |
If you mean the transaction log files, then that's likely the case. You should not ever touch the transaction logs yourself, you may have induced corruption in your graph.
Here's the documentation on transaction logs, including how to set your configuration properties to handle rotation and retention of the logs.
You may want to use the consistency checker to confirm the consistency of the database.
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
add a comment |
If you mean the transaction log files, then that's likely the case. You should not ever touch the transaction logs yourself, you may have induced corruption in your graph.
Here's the documentation on transaction logs, including how to set your configuration properties to handle rotation and retention of the logs.
You may want to use the consistency checker to confirm the consistency of the database.
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
If you mean the transaction log files, then that's likely the case. You should not ever touch the transaction logs yourself, you may have induced corruption in your graph.
Here's the documentation on transaction logs, including how to set your configuration properties to handle rotation and retention of the logs.
You may want to use the consistency checker to confirm the consistency of the database.
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
answered Nov 14 '18 at 12:34
InverseFalconInverseFalcon
19.1k21830
19.1k21830
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
add a comment |
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
Thought that'd be the cause but that page didn't help at all - dbms.tx_log.rotation.retention_policy=false didn't stop neo4j from making more of those transaction log files, and checkpoint was set to be set every 900 seconds but transaction logs over a whole week didn't have any checkpoint; hence I cannot remove any of the recent transaction log files (otherwise neo4j will say there aren't any checkpoint and refuses to open itself)
– Jung Raphael
Nov 14 '18 at 13:52
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
I recovered the transaction logs but to no avail - the bug persists.
– Jung Raphael
Nov 14 '18 at 14:57
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
Unfortunately, "recovering" the logs is unlikely to help, since those stale logs would likely no longer be in sync with the current logs or the state of the DB.
– cybersam
Nov 14 '18 at 21:45
add a comment |
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%2f53293567%2fcypher-count-returns-values-for-non-existing-nodes%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
