Thanks a lot, Dr Brett. Please forgive my problem. I am also a layman with linux.

#consensus #fabric-questions #fabric #hyperledger-fabric

You have a space between `--config=` and the file name. So it's parsing the file name as a flag, not as an input to a flag. Brett Logan Software Engineer, IBM Blockchain Phone: 1-984-242-6890 E-mail:

#consensus #fabric-questions #fabric #hyperledger-fabric

Thank you for your kind reply, Dr Dave. However, I think there are still differences between first-network in v2.1 and test-network in v2.2. When I check the files in v2.2, I find crypto-config-org1.y

#consensus #fabric-questions #fabric #hyperledger-fabric

If you want to see an example of two peers per org, look at the old Build Your First Network tutorial and sample in v2.1: https://hyperledger-fabric.readthedocs.io/en/release-2.1/build_network.html ht

#consensus #fabric-questions #fabric #hyperledger-fabric

I am using 2.0 and I assume 2.2 did not change this aspect - but you need to look at the policies in configtx.yaml. That defines the consensus via policies. You ask about endorsement, and that is defi

#consensus #fabric-questions #fabric #hyperledger-fabric

Dear everyone, I start to learn hyperledger fabric v2.2 and find that there is only one peer in each org. And the examples including test-network and commercial papers are all in this construction. I

#consensus #fabric-questions #fabric #hyperledger-fabric

If you send a steady flow of updates for the same key, you will always have some transactions in flight (endorsement or ordering phase) while earlier transactions are committing on peers. Since the la

#hyperledger-fabric #fabric-chaincode #consensus #raft

ِThanks Prasnth for your reply. So, you think it is a racing condition. Just to confirm with you. So, what the best way to update a value bases on its previous value? I need an example that does not i

#hyperledger-fabric #fabric-chaincode #consensus #raft

Hi Ali, Yes. MVCC - Multi Version Concurrency Control. It occurs exactly when like you mentioned. You need to design the chaincode in such a way to avoid frequent same key update as much as possible.

#hyperledger-fabric #fabric-chaincode #consensus #raft

Hi everyone, I have this wiered MVCC-conflict issue. It appears occasionally as I benchmark my Java chaincode. I tried everything I possibly could to prevent its occurance. Now, I am going to list the

#hyperledger-fabric #fabric-chaincode #consensus #raft

I am using the fabric 1.4.6. I am unable to use pluggable transaction endorsement and validation. There is no samples available. I also tried http://github.com/hyperledger/fabric-chaincode-go/pkg/stat

#fabric-chaincode #fabric #consensus

Hi, Please find the following logs attached: 2-orderer-logs-leader-stopped: logs of the two online orderers working-orderer-logs: partial logs of all the orderers Note: I have two hosts and one of the

#raft #consensus

Can you supply logs of all orderers? From: mshantharam@... To: fabric@... Date: 03/28/2020 07:52 AM Subject: [EXTERNAL] [Hyperledger Fabric] Raft orderers not able to elect a le

#raft #consensus

Hi, I have a hyperledger network (1.4.3) with 3 orderers in raft configuration and 3 peers. This works fine when all component are up and running. However when one orderer, the leader, is stopped, I s

#raft #consensus

Excellent, thanks! I should have piped up on this earlier when I saw the call for mass-closure of old issues. Brian

#consensus #fabric-orderer

To clarify, as Jason mentioned the Jira FAB-33 got caught up in a recent mass cleanup of stale issues that hadn't been touched in a long time. Any issue that was automatically closed in error can be r

#consensus #fabric-orderer

You really should use a different status for deferred feature requests than "Closed", because "decided not to implement this ever" is a closer inference from "Closed" than "maybe someday". Jira is dep

#consensus #fabric-orderer

I've seen some similar confusion to this on Rocketchat as well. FAB-33 was closed along with hundreds of other items in an overall cleanup of JIRA. Its closure does not indicate any mothballing or aba

#consensus #fabric-orderer

We are leading a standardization effort within SunSpec.org to utilize blockchain for securing the distributed power grid in the US. https://sunspec.org/sunspec-alliance-advances-security-for-distribut

#consensus #fabric-orderer

We are not using CLI. We are creating channel using Node SDK and creating infrastructure using shell script. We are using Raft consensus with 5 orderer and Raft cluster is working fine. Orderers elect

#fabric-sdk-node #docker #raft #consensus #cal-notice