Suspending objects within a replication group has long been available in the iCluster engine. In iCluster Web, that capability is available directly where object activity is already being reviewed, so state and action can be handled in one place.
The Idea: Act Where You Are Already Looking
When suspension is needed, the key questions are usually immediate: which objects are in this journal, what state is each object in, and which object should be acted on.
iCluster Web brings those answers together on one page. Starting from the monitored group, the journal is opened, and all journaled objects are shown with status, journal position, reason, and size. The target object can then be selected directly, without re-entering names or path specifiers.
Navigation Path
The full flow is available from the Monitor workflow:
Management → Monitor → expand group → Status card → journal row menu (⋮) → Journal objects → object row menu (⋮) → Suspend object
1. Start from Monitor
Open Management → Monitor.
Groups are shown with key context such as type, status, node pair, latency, and object counters.
Expand the required group from the row chevron (or use Expand all groups) to open the group cards.
2. Open Journal Objects
In the expanded Status card, locate the journal and open its action menu. Select Journal objects.
The Journal objects page opens with breadcrumb context under Monitor and a journal-focused object list.
Two tabs are available:
- Native objects (object-name based)
- Path objects (path-specifier based)
Both views include operational fields used for decisions: status, journal position, reason, and size.
3. Narrow the List
For larger journals, the page supports quick narrowing:
- status switching (for example, all/active/suspended views),
- search/filter controls (native-object attributes or path),
- incremental loading while scrolling.
This keeps investigation and selection responsive even when object counts are high.
4. Suspend the Object
From the selected object row, open the action menu and choose Suspend object.
The dialog is prefilled from the selected row:
- Native object: object, library, and object type are prefilled; backup node and member are confirmed.
- Path object: path is carried from the row; backup node is confirmed.
After Submit, success is confirmed and the list refreshes so updated state can be verified immediately.
5. Reverse When Needed: Activate Object
The same row-level action model is used for reversal.
When an object is suspended, Activate object is offered in place of Suspend object, so the menu reflects current object state.
Status values shown in the list include suspended, pending-suspend, pending-activate, and active states, allowing transition progress to be tracked directly from the table.
Who Can Do What
Viewing and action are intentionally separated:
- Users with cluster access can review journal objects, status, position, reason, and size.
- Suspend and Activate are administration-level operations enforced by the server (superuser/administrator authority required).
- If an account has read-level access only, visibility remains available but action requests are rejected with an explanatory message.
Centralized Operational View
From the Journal objects page, teams can:
- review native and path objects in one workflow,
- inspect state and replication position before acting,
- filter to the exact target quickly,
- suspend objects with prefilled context,
- reactivate when replication should resume.
Bottom Line
Object suspension is usually decided during live monitoring. iCluster Web places that action directly in the same workflow: open the group, open the journal, find the object, and suspend or reactivate without context switching - while the underlying iCluster engine behavior remains intact.
Product Demo
The following video demonstrates how to start, review, and end journal management in iCluster Web.
