LogEntry
One entry in the replicated Raft log.
Parameters
1-based, monotonically increasing position in the log. The log is contiguous — there are no gaps between consecutive entries.
The leader's term when this entry was appended. Term numbers increase monotonically across the cluster's lifetime.
Opaque application bytes. The Raft layer treats this as an uninterpreted blob; the application gives command meaning after the entry appears on RaftNode.committed. An application may legitimately propose an empty command — emptiness alone does not mark an entry internal (see isNoOp).
true only for the internal §5.4.2 election no-op a new leader appends so prior-term entries can advance commitIndex. No-ops are real log entries (replicated and persisted) but are not application data, so they are withheld from RaftNode.committed. Application-proposed entries always have isNoOp == false, even when their command is empty.
Non-null only for internal membership-change entries (§6 joint consensus). Like isNoOp, config entries are replicated and persisted but withheld from RaftNode.committed — they carry cluster membership, not application data. A null value means this is a normal application entry.
The Raft §8 client-serial dedup identity stamped by the proposer. Non-null for stamped application entries; null for internal no-op/config entries and for legacy entries decoded before this field existed.