Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/reference/command/mergeChunks.txt
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ satisfied.
Return Messages
---------------

On success, :dbcommand:`mergeChunks` returns to following document:
On success, :dbcommand:`mergeChunks` returns this document:

.. code-block:: javascript

Expand Down
3 changes: 2 additions & 1 deletion source/reference/config-database.txt
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,8 @@ to support sharding:
},
"lastmod" : Timestamp(1000, 2),
"lastmodEpoch" : ObjectId("<...>")
}
},
"owningShard" : "<value>"
}
}

Expand Down
16 changes: 15 additions & 1 deletion source/release-notes/5.0.txt
Original file line number Diff line number Diff line change
Expand Up @@ -501,6 +501,20 @@ Starting in MongoDB 5.0, when using the :dbcommand:`movePrimary` command
to remove a shard from a :ref:`sharded cluster <sharded-cluster>`,
writes to the original shard will generate an error message.

Split and Merge Chunk Changelogs Show Owning Shard
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Starting in MongoDB 5.0, documents in the :data:`config.changelog`
collection for
:manual:`split </tutorial/split-chunks-in-sharded-cluster/>` and
:manual:`merge </tutorial/merge-chunks-in-sharded-cluster/>` operations
contain an ``owningShard`` field. The ``owningShard`` field shows the
``shardId`` of the shard that owns the chunks that were split or
merged.

The ``owningShard`` field helps identify shards where split or merge
operations frequently occur.

.. _5.0-rel-notes-shell:

Shell Changes
Expand Down Expand Up @@ -674,7 +688,7 @@ memory usage for the :dbcommand:`validate` command.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Starting in MongoDB 5.0, you can use the
:parameter:`findChunksOnConfigTimeoutMS` parameter to change the timout
:parameter:`findChunksOnConfigTimeoutMS` parameter to change the timeout
for find operations on :data:`~config.chunks`.

Database Profiler ``filter`` Option
Expand Down
4 changes: 3 additions & 1 deletion source/tutorial/split-chunks-in-sharded-cluster.txt
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,9 @@ document as the lower bound in the new chunk:

sh.splitAt( "records.people", { "zipcode": "63109" } )

.. note:: :method:`~sh.splitAt()` does not necessarily split the chunk
.. note::

:method:`~sh.splitAt()` does not necessarily split the chunk
into two equally sized chunks. The split occurs at the location of
the document matching the query, regardless of where that document is
in the chunk.
Expand Down