A question about consensus among validators and transaction commit in Aptos

[byron1st]

Discord user ID

byron1st

Describe your question in detail.

I have a question about consensus and transaction commit in Aptos.

I am running a private network of 6-8 validators. All validators are set up to provide REST APIs. To avoid flooding one validator with API requests, I let clients randomly select the target validator. Then, I've noticed the following unintended behaviors:

1. the client sends a transaction to Validator1 that changes a specific resource.
2. After the WaitForTransaction finished running, and the transaction was committed.
3. Immediately afterward, the client calls the View function to try to verify that the resource change was made correctly. This time, the client sends the View function request to another randomly selected validator, Validator3.
4. Surprisingly, Validator3 returns the value before the resource change was made, even though the transaction was committed.

My speculation about this phenomenon is as follows: the transaction sent to Validator1 was committed, but the block holding this transaction was not synchronized to Validator3 before the View function was called, preventing the update from being reflected. If my speculation is true, then it appears that not all validators are participating in the consensus, even though there are only 6-8 validators.

Is my speculation correct? If so, what percentage of all validators typically participate in the consensus process? Is there any way to determine which validators have joined the consensus?

Thanks.

What error, if any, are you getting?

No response

What have you tried or looked at? Or how can we reproduce the error?

No response

Which operating system are you using?

macOS

Which SDK or tool are you using? (if any)

REST API

Describe your environment or tooling in detail

No response