# Revision history [back]

The MN determines the schedule when they call CNRegister.register() for their node. The schedule is visible for any given node in their node registry entry, which can be viewed from the getNodeCapabilities() service. See, for example:

The MN determines the schedule when they call CNRegister.register() for their node. The schedule is visible for any given node in their node registry entry, which can be viewed from the getNodeCapabilities() service. See, for example:

The MN determines sets the schedule when they call CNRegister.register() CNRegister.register() for their node. The schedule can be updated using CNRegister.updateNodeCapabilities(). The schedule is visible for any given node in their node registry entry, which can be viewed from the getNodeCapabilities() CNCore.listNodes() service. See, for example:You can see the current list of nodes and their sync schedules with a curl command like this:

curl  https://cn.dataone.org/cn/v1/node


The schedule lines will be embedded in that output, such as:

<schedule hour="*" mday="*" min="0/3" mon="*" sec="10" wday="?" year="*"/>


which says to sync once every 3 minutes on the 10 second mark. Documentation of the schedule format is in the Quartz Scheduler documentation.