1. 20 Sep, 2016 1 commit
    • manish's avatar
      Disable WAL for block storage DB · 0df6a8d1
      manish authored
      
      
      (Rocks) DB WAL adds overheads while using the DB for saving checkpoints
      for block storage. Avoiding writing to WAL translates the write workload
      (appending blocks to the blockfile) into a sequential disk writes.
      
      This commit changes the way checkpoints are saved - checkpoints are
      written to DB as before, however since WAL is disabled, the checkpoint
      stays in-memory only. The in-memory checkpoint is flushed explicitly to
      disk (via DB flush) at the time of new block file creation. The in-memory
      checkpoint would implicitly also be flushed to memory at the time of DB
      shutdown. However, if a crash takes place, the checkpoint available in the
      DB would be behind the actual block file status. In order to handle this
      crash scenario, this commit also adds code to perform a scan of the block
      file beyond the last saved checkpoint and update the checkpoint.
      
      Change-Id: Ie88646b225abaa50b595833f5e7ed8d4facae920
      Signed-off-by: default avatarmanish <manish.sethi@gmail.com>
      0df6a8d1
  2. 17 Sep, 2016 1 commit
    • Srinivasan Muralidharan's avatar
      chaincode life-cycle system chaincode for a chain · a3687a1f
      Srinivasan Muralidharan authored
      
      
      The life-cycle system chaincode (lccc) manages chaincodes for a chain in an
      endorser. The life-cycle is basically the "deploy", "upgrade", "stop"
      and "start" actions. This changeset provides the basic chaincode for
      creating the table of chaincodes and implements just the "deploy" command.
      This work will be developed till the basic endorser functions are fully
      implemented.
      
      This driver for this chaincode will be checked in the next changeset.
      
      NOTE - this change also fixes the limitation where only one system chaincode
      can be running at a time.
      
      This is part of the feature development of FAB-181, FAB-182, FAB-183.
      
      Change-Id: Iff36fee7c5b9a9ce4658910db73304a6bcd7e3d4
      Signed-off-by: default avatarSrinivasan Muralidharan <muralisr@us.ibm.com>
      a3687a1f
  3. 15 Sep, 2016 1 commit
  4. 14 Sep, 2016 1 commit
  5. 12 Sep, 2016 1 commit
  6. 08 Sep, 2016 1 commit
  7. 01 Sep, 2016 1 commit
  8. 31 Aug, 2016 1 commit
  9. 23 Aug, 2016 2 commits
  10. 22 Aug, 2016 3 commits
  11. 20 Aug, 2016 1 commit
  12. 19 Aug, 2016 2 commits
  13. 16 Aug, 2016 1 commit
    • Brad Gorman's avatar
      GitHub Issue #2119 - chaincode unittesting · 23afd056
      Brad Gorman authored
      
      
      Replaced ChaincodeStub with ChaincodeStubInterface to allow
      unit testing of chaincode. MockStub added to emulate a real
      chaincode without the storage or network requirements.
      Unit test examples for chaincode_example02 to 05.
      
      I have another changeset to address tables and certificates.
      
      Change-Id: I37d6115781436e080a70d5c48c1128ee01fef3ba
      Signed-off-by: default avatarBradley Gorman <bgorman@au1.ibm.com>
      23afd056
  14. 12 Aug, 2016 1 commit
    • Gabor Hosszu's avatar
      Fix failing utils unit test · d9596b4c
      Gabor Hosszu authored
      
      
      This commit fixes a test:
      - fixes function names (no UUID but TxID)
      - a SHA256 hash is 256 long, not 36 like the old
        UUID was
      - fixes datatype in function that generates ID
        using custom algorithm
      
      Change-Id: I63e096c41034278be5aa8651de3b4352ee7b378c
      Signed-off-by: default avatarGabor Hosszu <gabor@digitalasset.com>
      d9596b4c
  15. 11 Aug, 2016 1 commit
  16. 10 Aug, 2016 3 commits
  17. 08 Aug, 2016 3 commits
  18. 06 Aug, 2016 2 commits
  19. 04 Aug, 2016 1 commit
  20. 03 Aug, 2016 1 commit
    • Srinivasan Muralidharan's avatar
      re-enable sending of chaincode events · 6daedfd6
      Srinivasan Muralidharan authored
      
      
      Chaincode events were originally stored in TransactionResults
      in NonHashData(see fabric.proto). TransactionResults was removed as
      part of removing error transactions from ledger which broke
      sending of chaincode events. This is fixed in the patch which
      stores chaincode events directly in NonHashData. Sample is also
      enhanced.
      
      Change-Id: Ifee8facb2e4760e878f15716af0e48346536c476
      Signed-off-by: default avatarSrinivasan Muralidharan <muralisr@us.ibm.com>
      6daedfd6
  21. 02 Aug, 2016 1 commit
    • sheehan's avatar
      Recompile proto files. · 967b72c1
      sheehan authored
      
      
      The proto build script was broken with the introduction of Java chaincode.
      PR #2162 resolved this and simplified the script.
      Due to the script simplification, there were a few changes in the .pb.go
      files after they were recompiled.
      It was also necessary to change the package name of dah.proto
      to avoid compile errors after compiling with the updated script.
      
      Change-Id: Ie009c0b790db859e356645dd204082641ee7eab5
      Signed-off-by: default avatarSheehan Anderson <sheehan@us.ibm.com>
      967b72c1
  22. 01 Aug, 2016 1 commit
    • grapebaba's avatar
      Refactor db package · 9544025c
      grapebaba authored
      
      
      Currently db will open when GetDBHandle method is invoked first time,
      so GetDBHandle method needs to use mutex.
      This patch makes db open and close in its lifecycle methods Start and
      Stop, invokes Start only when peer starts and invokes Stop when peer
      stops.
      After that, methods in db do not need to support concurrency.
      
      Change-Id: Id8612f2a846c5d626bd42c5cd4ae482076f6a975
      Signed-off-by: default avatargrapebaba <281165273@qq.com>
      9544025c
  23. 31 Jul, 2016 2 commits
  24. 30 Jul, 2016 1 commit
  25. 28 Jul, 2016 1 commit
  26. 26 Jul, 2016 1 commit