Bumped by Community user

occurred Oct 30 at 14:04

Bumped by Community user

occurred Jun 22 at 21:01

Bumped by Community user

occurred Feb 12 at 4:06

Bumped by Community user

occurred Oct 6, 2023 at 23:04

Bumped by Community user

occurred Jun 3, 2023 at 17:05

Bumped by Community user

occurred Jan 28, 2023 at 15:03

Bumped by Community user

occurred Sep 29, 2022 at 15:00

Bumped by Community user

occurred May 28, 2022 at 1:06

Bumped by Community user

occurred Jan 23, 2022 at 19:03

Bumped by Community user

occurred Sep 25, 2021 at 5:08

Bumped by Community user

occurred May 22, 2021 at 13:04

Bumped by Community user

occurred Jan 19, 2021 at 8:04

Bumped by Community user

occurred Sep 17, 2020 at 13:00

Bumped by Community user

occurred May 19, 2020 at 5:03

Bumped by Community user

occurred Jan 19, 2020 at 20:02

Bumped by Community user

occurred Sep 20, 2019 at 19:01

Bumped by Community user

occurred May 11, 2019 at 22:01

improved formatting

Source Link

edit approved Mar 8, 2019 at 6:24

Mani

814
1
6
10

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F - [conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F -
[conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T13:44:11.594+0530 E STORAGE [conn20] WiredTiger error (12) [1551255251:594637][54524:2000827264], file:collection-17071--5635302636308412295.wt, WT_CURSOR.search: memory allocation of 28696 bytes failed: Not enough space

2019-02-27T13:44:11.594+0530 F - [conn20] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T13:44:11.595+0530 F - [conn20]

***aborting after invariant() failure

2019-02-27T13:44:11.594+0530 E STORAGE [conn20] WiredTiger error (12) [1551255251:594637][54524:2000827264], file:collection-17071--5635302636308412295.wt, WT_CURSOR.search: memory allocation of 28696 bytes failed: Not enough space

2019-02-27T13:44:11.594+0530 F - [conn20] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T13:44:11.595+0530 F - [conn20]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Any idea what might have caused this issue?

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F - [conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T13:44:11.594+0530 E STORAGE [conn20] WiredTiger error (12) [1551255251:594637][54524:2000827264], file:collection-17071--5635302636308412295.wt, WT_CURSOR.search: memory allocation of 28696 bytes failed: Not enough space

2019-02-27T13:44:11.594+0530 F - [conn20] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T13:44:11.595+0530 F - [conn20]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Any idea what might have caused this issue?

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F -
[conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T13:44:11.594+0530 E STORAGE [conn20] WiredTiger error (12) [1551255251:594637][54524:2000827264], file:collection-17071--5635302636308412295.wt, WT_CURSOR.search: memory allocation of 28696 bytes failed: Not enough space

2019-02-27T13:44:11.594+0530 F - [conn20] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T13:44:11.595+0530 F - [conn20]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Any idea what might have caused this issue?

deleted 261 characters in body

Source Link

edited Mar 7, 2019 at 6:38

Chandana

13
1
7

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F - [conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T0827T13:44:5111.322+0530594+0530 E STORAGE [conn9874479] [conn20] WiredTiger error (12) [1551237291[1551255251:322637][2344594637][54524:2000827264], file:collection-1705517071--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096memory allocation of 28696 bytes at offset 69206016failed: Not enough storage is available to process this command.space

: Not enough space 2019 2019-02-27T0827T13:44:5111.322+0530594+0530 F - [conn9874479] [conn20] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019

2019-02-27T0827T13:44:5111.322+0530595+0530 F - [conn9874479] [conn20]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Moreover, when I checked memory after noticing the issue, only 14 GB was being used (out of 32GB). Any idea what might have caused this issue?

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F - [conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T08:44:51.322+0530 E STORAGE [conn9874479] WiredTiger error (12) [1551237291:322637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 69206016: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.322+0530 F - [conn9874479] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.322+0530 F - [conn9874479]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Moreover, when I checked memory after noticing the issue, only 14 GB was being used (out of 32GB). Any idea what might have caused this issue?

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F - [conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T13:44:11.594+0530 E STORAGE [conn20] WiredTiger error (12) [1551255251:594637][54524:2000827264], file:collection-17071--5635302636308412295.wt, WT_CURSOR.search: memory allocation of 28696 bytes failed: Not enough space

2019-02-27T13:44:11.594+0530 F - [conn20] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734

2019-02-27T13:44:11.595+0530 F - [conn20]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Any idea what might have caused this issue?

Source Link

asked Feb 27, 2019 at 10:58

Chandana

13
1
7

MongoDB 3.6 crashed due to invariant() failure

MongoDB crashed twice in 6 hours today due to invariant() failure. We have been using MongoDB 3.6.3 for more than a year now, but this is the first time that we saw this issue. The extract from the log files is given below for reference -

Log from 1st failure:

2019-02-27T08:44:51.411+0530 E STORAGE [conn3385299] WiredTiger error (12) [1551237291:411637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 720363520: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.412+0530 F - [conn3385299] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.412+0530 F - [conn3385299]

***aborting after invariant() failure

Log from 2nd failure:

2019-02-27T08:44:51.322+0530 E STORAGE [conn9874479] WiredTiger error (12) [1551237291:322637][2344:2000827264], file:collection-17055--5635302636308412295.wt, WT_CURSOR.search: C:/MREYE/MongoDB/data\collection-17055--5635302636308412295.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 69206016: Not enough storage is available to process this command.

: Not enough space 2019-02-27T08:44:51.322+0530 F - [conn9874479] Invariant failure: seekRet resulted in status UnknownError: 12: Not enough space at src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp 1734 2019-02-27T08:44:51.322+0530 F - [conn9874479]

***aborting after invariant() failure

Note:

The MongoDB is on C drive and there is sufficient space left (276 GB) on that drive. The MongoDB data folder size itself is only 65 GB. Moreover, when I checked memory after noticing the issue, only 14 GB was being used (out of 32GB). Any idea what might have caused this issue?

mongodb mongodb-3.6

Stack Exchange Network

Return to Question

MongoDB 3.6 crashed due to invariant() failure