Dinesh Rivankar
Dinesh Rivankar

Reputation: 43

Hyperledger Fabric : Impact on transaction when we migrate Orderer

Migration of Ordering service from Kafka to Raft. As we understand the Ordering service never signs the transaction in Fabric. Dose this migration will effect anything on old transaction ordered by old ordere?

Also when we query transaction(local peer query), why do we set the orderer flag?

Upvotes: 0

Views: 153

Answers (1)

Narendranath Reddy
Narendranath Reddy

Reputation: 4133

As long as you have successfully migrated consensus type from kafka >> raft

You are allowed to proceed with transactions.

Question1: Ordering service never signs the transaction in Fabric

Endorsing peers alone will sign transactions & orderer signs the blocks

Question2: Dose this migration will effect anything on old transaction ordered by old ordere?

No, If migration is successful then you are OK to proceed

If you would have followed this link and complete without errors https://hyperledger-fabric.readthedocs.io/en/release-1.4/kafka_raft_migration.html

THEN OK, dont worry about previous data, All SAFE.

However, let me know if you need any assistance in migration. Feel free to create another question reg: migration.

If you want to see old blocks after migration check this snippet

// keep the block_reg to unregister with later if needed
block_reg = channel_event_hub.registerBlockEvent((block) => {
    console.log('Successfully received the block event');
    <do something with the block>
}, (error)=> {
    console.log('Failed to receive the block event ::'+error);
    <do something with the error>
},
    {startBlock:23}
);

startBlock:{can be any Block No}

check > https://fabric-sdk-node.github.io/tutorial-channel-events.html

you will get complete block as json format, you will have orderer signature so that you can check which orderer has sealed this block.

Upvotes: 3

Related Questions