diff --git a/404.html b/404.html index b0b3cc1bc..a5b612a0b 100644 --- a/404.html +++ b/404.html @@ -13,13 +13,13 @@ gtag('config', 'G-SMSDTMGLTV'); - +

404

Looks like we've got some broken links.
Take me home.
- + diff --git a/_Footer.html b/_Footer.html index f13f25eae..b3c069986 100644 --- a/_Footer.html +++ b/_Footer.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    - +

    See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    + diff --git a/about/index.html b/about/index.html index 68d48f08b..280214141 100644 --- a/about/index.html +++ b/about/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # Mission, Vision, Value

    # Contacts

    # Resources

    - +

    # Mission, Vision, Value

    # Contacts

    # Resources

    + diff --git a/assets/js/15.c263d455.js b/assets/js/15.2739a67e.js similarity index 85% rename from assets/js/15.c263d455.js rename to assets/js/15.2739a67e.js index 27740fd6c..6f225d475 100644 --- a/assets/js/15.c263d455.js +++ b/assets/js/15.2739a67e.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[15],{331:function(t,s,e){t.exports=e.p+"assets/img/one-pager-venus.ba147919.png"},433:function(t,s,e){"use strict";e.r(s);var n=e(17),r=Object(n.a)({},(function(){var t=this.$createElement,s=this._self._c||t;return s("ContentSlotsDistributor",{attrs:{"slot-key":this.$parent.slotKey}},[s("p",[s("img",{attrs:{src:e(331),alt:"venus-cluster"}})])])}),[],!1,null,null,null);s.default=r.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[15],{331:function(t,s,e){t.exports=e.p+"assets/img/one-pager-venus.ba147919.png"},431:function(t,s,e){"use strict";e.r(s);var n=e(17),r=Object(n.a)({},(function(){var t=this.$createElement,s=this._self._c||t;return s("ContentSlotsDistributor",{attrs:{"slot-key":this.$parent.slotKey}},[s("p",[s("img",{attrs:{src:e(331),alt:"venus-cluster"}})])])}),[],!1,null,null,null);s.default=r.exports}}]); \ No newline at end of file diff --git a/assets/js/16.c99ecbd6.js b/assets/js/16.d869f1e9.js similarity index 92% rename from assets/js/16.c99ecbd6.js rename to assets/js/16.d869f1e9.js index 18803b3b1..180aa9581 100644 --- a/assets/js/16.c99ecbd6.js +++ b/assets/js/16.d869f1e9.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[16],{332:function(t,e,n){t.exports=n.p+"assets/img/sophon-banner.6a83f125.jpg"},431:function(t,e,n){"use strict";n.r(e);var s=n(17),r=Object(s.a)({},(function(){var t=this,e=t.$createElement,s=t._self._c||e;return s("ContentSlotsDistributor",{attrs:{"slot-key":t.$parent.slotKey}},[s("p",[s("img",{attrs:{src:n(332),alt:"sophon"}})]),t._v(" "),s("h3",{attrs:{id:"智子"}},[s("a",{staticClass:"header-anchor",attrs:{href:"#智子"}},[t._v("#")]),t._v(" 智子")]),t._v(" "),s("p",[t._v("智子，原 Venus 链服务，是一个 Filecoin 超级节点解决方案。请在"),s("a",{attrs:{href:"https://sophon.venus-fil.io/zh/",target:"_blank",rel:"noopener noreferrer"}},[t._v("此"),s("OutboundLink")],1),t._v("了解更多关于智子的信息。")])])}),[],!1,null,null,null);e.default=r.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[16],{332:function(t,e,n){t.exports=n.p+"assets/img/sophon-banner.6a83f125.jpg"},432:function(t,e,n){"use strict";n.r(e);var s=n(17),r=Object(s.a)({},(function(){var t=this,e=t.$createElement,s=t._self._c||e;return s("ContentSlotsDistributor",{attrs:{"slot-key":t.$parent.slotKey}},[s("p",[s("img",{attrs:{src:n(332),alt:"sophon"}})]),t._v(" "),s("h3",{attrs:{id:"智子"}},[s("a",{staticClass:"header-anchor",attrs:{href:"#智子"}},[t._v("#")]),t._v(" 智子")]),t._v(" "),s("p",[t._v("智子，原 Venus 链服务，是一个 Filecoin 超级节点解决方案。请在"),s("a",{attrs:{href:"https://sophon.venus-fil.io/zh/",target:"_blank",rel:"noopener noreferrer"}},[t._v("此"),s("OutboundLink")],1),t._v("了解更多关于智子的信息。")])])}),[],!1,null,null,null);e.default=r.exports}}]); \ No newline at end of file diff --git a/assets/js/36.9f267b4f.js b/assets/js/36.16ebd43f.js similarity index 99% rename from assets/js/36.9f267b4f.js rename to assets/js/36.16ebd43f.js index def4c43cd..be7c97ea4 100644 --- a/assets/js/36.9f267b4f.js +++ b/assets/js/36.16ebd43f.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[36],{421:function(e,t,a){"use strict";a.r(t);var v=a(17),r=Object(v.a)({},(function(){var e=this,t=e.$createElement,a=e._self._c||t;return a("ContentSlotsDistributor",{attrs:{"slot-key":e.$parent.slotKey}},[a("h1",{attrs:{id:"venus-stack-nv22-upgrade-guide-wip"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus-stack-nv22-upgrade-guide-wip"}},[e._v("#")]),e._v(" Venus Stack nv22 Upgrade Guide (WIP)")]),e._v(" "),a("h2",{attrs:{id:"precautions"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#precautions"}},[e._v("#")]),e._v(" Precautions")]),e._v(" "),a("ol",[a("li",[e._v("Upgrade all Venus products / components")]),e._v(" "),a("li",[e._v("Use the "),a("code",[e._v("curl")]),e._v(" command to call the "),a("code",[e._v("Version")]),e._v(" interface to check the version number after upgrading. Refer to the guide "),a("a",{attrs:{href:"https://github.com/filecoin-project/venus/issues/5132",target:"_blank",rel:"noopener noreferrer"}},[e._v("here"),a("OutboundLink")],1),e._v(" for details.")]),e._v(" "),a("li",[e._v("Check if pre/pro messages are on-chained")]),e._v(" "),a("li",[e._v("Check if windowPost messages are on-chained")]),e._v(" "),a("li",[e._v("Check if block producing is working correctly")]),e._v(" "),a("li",[e._v("Check if the gas fee related settings are in effect")])]),e._v(" "),a("h2",{attrs:{id:"products-components-to-be-upgraded"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#products-components-to-be-upgraded"}},[e._v("#")]),e._v(" Products / Components to be Upgraded")]),e._v(" "),a("table",[a("thead",[a("tr",[a("th",[e._v("Component name")]),e._v(" "),a("th",[e._v("tag")]),e._v(" "),a("th",[e._v("commit")])])]),e._v(" "),a("tbody",[a("tr",[a("td",[e._v("sophon-auth")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("a1e964b")])]),e._v(" "),a("tr",[a("td",[e._v("venus")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("aabda75")])]),e._v(" "),a("tr",[a("td",[e._v("sophon-co")]),e._v(" "),a("td",[e._v("v0.8.0")]),e._v(" "),a("td",[e._v("0e48712")])]),e._v(" "),a("tr",[a("td",[e._v("sophon-messager")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("1e4f0d5")])]),e._v(" "),a("tr",[a("td",[e._v("soohon-gateway")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("541891a")])]),e._v(" "),a("tr",[a("td",[e._v("venus-wallet")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("6b3de34")])]),e._v(" "),a("tr",[a("td",[e._v("sophon-miner")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("8dd6c68")])]),e._v(" "),a("tr",[a("td",[e._v("droplet")]),e._v(" "),a("td",[e._v("v2.11.0")]),e._v(" "),a("td",[e._v("44481dd")])]),e._v(" "),a("tr",[a("td",[e._v("damocles-manager")]),e._v(" "),a("td",[e._v("v0.10.0-rc1")]),e._v(" "),a("td",[e._v("2f6c5f9")])]),e._v(" "),a("tr",[a("td",[e._v("damocles-worker")]),e._v(" "),a("td",[e._v("v0.10.0-rc1")]),e._v(" "),a("td",[e._v("2f6c5f9")])])])]),e._v(" "),a("h3",{attrs:{id:"upgrade-sequence"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#upgrade-sequence"}},[e._v("#")]),e._v(" Upgrade Sequence")]),e._v(" "),a("ol",[a("li",[e._v("sophon-auth")]),e._v(" "),a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("soohon-co")]),e._v(" "),a("li",[e._v("soohon-gateway")]),e._v(" "),a("li",[e._v("sophon-messager")]),e._v(" "),a("li",[e._v("sophon-miner")]),e._v(" "),a("li",[e._v("droplet")]),e._v(" "),a("li",[e._v("venus-wallet")]),e._v(" "),a("li",[e._v("damocles-manager")]),e._v(" "),a("li",[e._v("damocles-worker")])]),e._v(" "),a("h3",{attrs:{id:"sophon-auth"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-auth"}},[e._v("#")]),e._v(" sophon-auth")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("Aquiring auth services from other components")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("Is authentication working normally after startup?")])]),e._v(" "),a("h3",{attrs:{id:"venus"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus"}},[e._v("#")]),e._v(" Venus")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("sophon-auth")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("p",[e._v("Compile: First "),a("code",[e._v("make dist-clean")]),e._v(" and then "),a("code",[e._v("make")]),e._v(", this can prevent problems caused by failure to upgrade "),a("code",[e._v("filecoin-ffi")]),e._v(" properly.")]),e._v(" "),a("ol",[a("li",[a("p",[e._v("Check if the vk file is complete after upgrading")])]),e._v(" "),a("li",[a("p",[e._v("After the upgrade, execute the command "),a("code",[e._v("./venus state network-info")]),e._v(", and then check whether the UpgradeDragonHeight is normal through the log:")]),e._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[e._v("#cali\nUpgradeDragonHeight: 1427974\n#mainnet\nUpgradeDragonHeight: 3817920\n")])])])]),e._v(" "),a("li",[a("p",[e._v("After the upgrade, you need to check if the blocks are synchronized normally.")])]),e._v(" "),a("li",[a("p",[e._v("Check the mainnet v13 actors code and make sure it is the same as the output below")]),e._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[e._v("./venus state actor-cids --network-version 22\n\n# The order may be different\nNetwork Version: 22\nActor Version: 13\nManifest CID: bafy2bzacecdhvfmtirtojwhw2tyciu4jkbpsbk5g53oe24br27oy62sn4dc4e\nActor CID\naccount bafk2bzacedxnbtlsqdk76fsfmnhyvsblwyfducerwwtp3mqtx2wbrvs5idl52\ncron bafk2bzacebbopddyn5csb3fsuhh2an4ttd23x6qnwixgohlirj5ahtcudphyc\ndatacap bafk2bzaceah42tfnhd7xnztawgf46gbvc3m2gudoxshlba2ucmmo2vy67t7ci\neam bafk2bzaceb23bhvvcjsth7cn7vp3gbaphrutsaz7v6hkls3ogotzs4bnhm4mk\nethaccount bafk2bzaceautge6zhuy6jbj3uldwoxwhpywuon6z3xfvmdbzpbdribc6zzmei\nevm bafk2bzacedq6v2lyuhgywhlllwmudfj2zufzcauxcsvvd34m2ek5xr55mvh2q\ninit bafk2bzacedr4xacm3fts4vilyeiacjr2hpmwzclyzulbdo24lrfxbtau2wbai\nmultisig bafk2bzacecr5zqarfqak42xqcfeulsxlavcltawsx2fvc7zsjtby6ti4b3wqc\npaymentchannel bafk2bzacebntdhfmyc24e7tm52ggx5tnw4i3hrr3jmllsepv3mibez4hywsa2\nplaceholder bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro\nreward bafk2bzacedq4q2kwkruu4xm7rkyygumlbw2yt4nimna2ivea4qarvtkohnuwu\nstoragemarket bafk2bzacebjtoltdviyznpj34hh5qp6u257jnnbjole5rhqfixm7ug3epvrfu\nstorageminer bafk2bzacebf4rrqyk7gcfggggul6nfpzay7f2ordnkwm7z2wcf4mq6r7i77t2\nstoragepower bafk2bzacecjy4dkulvxppg3ocbmeixe2wgg6yxoyjxrm4ko2fm3uhpvfvam6e\nsystem bafk2bzacecyf523quuq2kdjfdvyty446z2ounmamtgtgeqnr3ynlu5cqrlt6e\nverifiedregistry bafk2bzacedkxehp7y7iyukbcje3wbpqcvufisos6exatkanyrbotoecdkrbta\n")])])])]),e._v(" "),a("li",[a("p",[e._v("If you are not troubleshooting the system, it is not recommended to set the rust log level to "),a("code",[e._v("trace")]),e._v(" because more logs will be printed.")])]),e._v(" "),a("li",[a("p",[e._v("After the upgrade, you can use the command "),a("code",[e._v("./venus state get-actor t01000")]),e._v(" to confirm whether the upgrade is successful.")])]),e._v(" "),a("li",[a("p",[e._v("actor migration")]),e._v(" "),a("p",[a("strong",[e._v("After testing, the pre-migration time is about 30 minutes, and the main migration time is about 100 seconds")])]),e._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[e._v("The pre-migration height is 120 heights before the upgrade height:\npre-migration start: STARTING pre-migration end: COMPLETED pre-migration\nmigration starts: STARTING migration ends: COMPLETED migration\n")])])])]),e._v(" "),a("li",[a("p",[e._v("If "),a("code",[e._v("~/.venus")]),e._v(" exists and you need to import a snapshot, you need to delete the "),a("code",[e._v("~/.venus/version")]),e._v(" file first and then import the snapshot.")]),e._v(" "),a("ul",[a("li",[e._v("Mainnet: "),a("code",[e._v("./venus daemon --import-snapshot snapshot.car")])]),e._v(" "),a("li",[e._v("calibnet: "),a("code",[e._v("./venus daemon --import-snapshot snapshot.car --network calibrationnet")])])])])]),e._v(" "),a("h3",{attrs:{id:"sophon-gateway"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-gateway"}},[e._v("#")]),e._v(" sophon-gateway")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("sophon-auth")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("When compiling, you need to first "),a("code",[e._v("make dist-clean")]),e._v(" and then "),a("code",[e._v("make")])])]),e._v(" "),a("h3",{attrs:{id:"sophon-messager"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-messager"}},[e._v("#")]),e._v(" sophon-messager")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("sophon-auth")]),e._v(" "),a("li",[e._v("sophon-gateway")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("After the upgrade, you need to observe whether the messages can be received normally and whether the messages can be on-chained normally.")])]),e._v(" "),a("h3",{attrs:{id:"sophon-miner"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-miner"}},[e._v("#")]),e._v(" sophon-miner")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("auth")]),e._v(" "),a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("gateway")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("h3",{attrs:{id:"droplet"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#droplet"}},[e._v("#")]),e._v(" droplet")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("Direct data onboarding support; Documentation "),a("a",{attrs:{href:"https://github.com/ipfs-force-community/droplet/blob/master/docs/zh/direct-on-boarding.md",target:"_blank",rel:"noopener noreferrer"}},[e._v("here"),a("OutboundLink")],1)])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("auth")]),e._v(" "),a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("gateway")]),e._v(" "),a("li",[e._v("messager")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("Check if deals and retrieval can be issued normally after the upgrade?")])]),e._v(" "),a("h3",{attrs:{id:"venus-wallet"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus-wallet"}},[e._v("#")]),e._v(" venus-wallet")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("gateway")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("After the upgrade, observe whether the signing is normal and whether the message can be on-chained normally.")])]),e._v(" "),a("h3",{attrs:{id:"damocles-manager"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#damocles-manager"}},[e._v("#")]),e._v(" damocles-manager")]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("Sophon service")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("When compiling, you need to first "),a("code",[e._v("make dist-clean")]),e._v(" and then "),a("code",[e._v("make")])])]),e._v(" "),a("h3",{attrs:{id:"damocles-worker"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#damocles-worker"}},[e._v("#")]),e._v(" damocles-worker")]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("damocles-manager")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("p",[e._v("Upgrade result verification steps:")]),e._v(" "),a("ol",[a("li",[e._v("Check if the program starts normally")]),e._v(" "),a("li",[e._v("Check if pre / pro messages are uploaded normally")]),e._v(" "),a("li",[e._v("Check if block producing is normal")]),e._v(" "),a("li",[e._v("Check if windowPost is normal")]),e._v(" "),a("li",[e._v("Check if storage power grows normally")]),e._v(" "),a("li",[e._v("Check if verified deal retrieval is normal")]),e._v(" "),a("li",[e._v("Check if various gas, sector life cycle, and aggregation settings in the database are normal.")])]),e._v(" "),a("h3",{attrs:{id:"database-changes"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#database-changes"}},[e._v("#")]),e._v(" Database changes")]),e._v(" "),a("ol",[a("li",[e._v("The droplet adds the "),a("code",[e._v("direct_deals")]),e._v(" table to store DD\nO deals.")])])])}),[],!1,null,null,null);t.default=r.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[36],{421:function(e,t,a){"use strict";a.r(t);var v=a(17),r=Object(v.a)({},(function(){var e=this,t=e.$createElement,a=e._self._c||t;return a("ContentSlotsDistributor",{attrs:{"slot-key":e.$parent.slotKey}},[a("h1",{attrs:{id:"venus-stack-nv22-upgrade-guide-wip"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus-stack-nv22-upgrade-guide-wip"}},[e._v("#")]),e._v(" Venus Stack nv22 Upgrade Guide (WIP)")]),e._v(" "),a("h2",{attrs:{id:"precautions"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#precautions"}},[e._v("#")]),e._v(" Precautions")]),e._v(" "),a("ol",[a("li",[e._v("Upgrade all Venus products / components")]),e._v(" "),a("li",[e._v("Use the "),a("code",[e._v("curl")]),e._v(" command to call the "),a("code",[e._v("Version")]),e._v(" interface to check the version number after upgrading. Refer to the guide "),a("a",{attrs:{href:"https://github.com/filecoin-project/venus/issues/5132",target:"_blank",rel:"noopener noreferrer"}},[e._v("here"),a("OutboundLink")],1),e._v(" for details.")]),e._v(" "),a("li",[e._v("Check if pre/pro messages are on-chained")]),e._v(" "),a("li",[e._v("Check if windowPost messages are on-chained")]),e._v(" "),a("li",[e._v("Check if block producing is working correctly")]),e._v(" "),a("li",[e._v("Check if the gas fee related settings are in effect")])]),e._v(" "),a("h2",{attrs:{id:"products-components-to-be-upgraded"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#products-components-to-be-upgraded"}},[e._v("#")]),e._v(" Products / Components to be Upgraded")]),e._v(" "),a("table",[a("thead",[a("tr",[a("th",[e._v("Component name")]),e._v(" "),a("th",[e._v("tag")]),e._v(" "),a("th",[e._v("commit")])])]),e._v(" "),a("tbody",[a("tr",[a("td",[e._v("sophon-auth")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("a1e964b")])]),e._v(" "),a("tr",[a("td",[e._v("venus")]),e._v(" "),a("td",[e._v("v1.15.1")]),e._v(" "),a("td",[e._v("81c99f3")])]),e._v(" "),a("tr",[a("td",[e._v("sophon-co")]),e._v(" "),a("td",[e._v("v0.8.0")]),e._v(" "),a("td",[e._v("0e48712")])]),e._v(" "),a("tr",[a("td",[e._v("sophon-messager")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("1e4f0d5")])]),e._v(" "),a("tr",[a("td",[e._v("soohon-gateway")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("541891a")])]),e._v(" "),a("tr",[a("td",[e._v("venus-wallet")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("6b3de34")])]),e._v(" "),a("tr",[a("td",[e._v("sophon-miner")]),e._v(" "),a("td",[e._v("v1.15.0")]),e._v(" "),a("td",[e._v("8dd6c68")])]),e._v(" "),a("tr",[a("td",[e._v("droplet")]),e._v(" "),a("td",[e._v("v2.11.0")]),e._v(" "),a("td",[e._v("44481dd")])]),e._v(" "),a("tr",[a("td",[e._v("damocles-manager")]),e._v(" "),a("td",[e._v("v0.10.0-rc1")]),e._v(" "),a("td",[e._v("2f6c5f9")])]),e._v(" "),a("tr",[a("td",[e._v("damocles-worker")]),e._v(" "),a("td",[e._v("v0.10.0-rc1")]),e._v(" "),a("td",[e._v("2f6c5f9")])])])]),e._v(" "),a("h3",{attrs:{id:"upgrade-sequence"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#upgrade-sequence"}},[e._v("#")]),e._v(" Upgrade Sequence")]),e._v(" "),a("ol",[a("li",[e._v("sophon-auth")]),e._v(" "),a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("soohon-co")]),e._v(" "),a("li",[e._v("soohon-gateway")]),e._v(" "),a("li",[e._v("sophon-messager")]),e._v(" "),a("li",[e._v("sophon-miner")]),e._v(" "),a("li",[e._v("droplet")]),e._v(" "),a("li",[e._v("venus-wallet")]),e._v(" "),a("li",[e._v("damocles-manager")]),e._v(" "),a("li",[e._v("damocles-worker")])]),e._v(" "),a("h3",{attrs:{id:"sophon-auth"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-auth"}},[e._v("#")]),e._v(" sophon-auth")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("Aquiring auth services from other components")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("Is authentication working normally after startup?")])]),e._v(" "),a("h3",{attrs:{id:"venus"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus"}},[e._v("#")]),e._v(" Venus")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("sophon-auth")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("p",[e._v("Compile: First "),a("code",[e._v("make dist-clean")]),e._v(" and then "),a("code",[e._v("make")]),e._v(", this can prevent problems caused by failure to upgrade "),a("code",[e._v("filecoin-ffi")]),e._v(" properly.")]),e._v(" "),a("ol",[a("li",[a("p",[e._v("Check if the vk file is complete after upgrading")])]),e._v(" "),a("li",[a("p",[e._v("After the upgrade, execute the command "),a("code",[e._v("./venus state network-info")]),e._v(", and then check whether the UpgradeDragonHeight is normal through the log:")]),e._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[e._v("#cali\nUpgradeDragonHeight: 1427974\n#mainnet\nUpgradeDragonHeight: 3855360\n")])])])]),e._v(" "),a("li",[a("p",[e._v("After the upgrade, you need to check if the blocks are synchronized normally.")])]),e._v(" "),a("li",[a("p",[e._v("Check the mainnet v13 actors code and make sure it is the same as the output below")]),e._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[e._v("./venus state actor-cids --network-version 22\n\n# The order may be different\nNetwork Version: 22\nActor Version: 13\nManifest CID: bafy2bzacecdhvfmtirtojwhw2tyciu4jkbpsbk5g53oe24br27oy62sn4dc4e\nActor CID\naccount bafk2bzacedxnbtlsqdk76fsfmnhyvsblwyfducerwwtp3mqtx2wbrvs5idl52\ncron bafk2bzacebbopddyn5csb3fsuhh2an4ttd23x6qnwixgohlirj5ahtcudphyc\ndatacap bafk2bzaceah42tfnhd7xnztawgf46gbvc3m2gudoxshlba2ucmmo2vy67t7ci\neam bafk2bzaceb23bhvvcjsth7cn7vp3gbaphrutsaz7v6hkls3ogotzs4bnhm4mk\nethaccount bafk2bzaceautge6zhuy6jbj3uldwoxwhpywuon6z3xfvmdbzpbdribc6zzmei\nevm bafk2bzacedq6v2lyuhgywhlllwmudfj2zufzcauxcsvvd34m2ek5xr55mvh2q\ninit bafk2bzacedr4xacm3fts4vilyeiacjr2hpmwzclyzulbdo24lrfxbtau2wbai\nmultisig bafk2bzacecr5zqarfqak42xqcfeulsxlavcltawsx2fvc7zsjtby6ti4b3wqc\npaymentchannel bafk2bzacebntdhfmyc24e7tm52ggx5tnw4i3hrr3jmllsepv3mibez4hywsa2\nplaceholder bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro\nreward bafk2bzacedq4q2kwkruu4xm7rkyygumlbw2yt4nimna2ivea4qarvtkohnuwu\nstoragemarket bafk2bzacebjtoltdviyznpj34hh5qp6u257jnnbjole5rhqfixm7ug3epvrfu\nstorageminer bafk2bzacebf4rrqyk7gcfggggul6nfpzay7f2ordnkwm7z2wcf4mq6r7i77t2\nstoragepower bafk2bzacecjy4dkulvxppg3ocbmeixe2wgg6yxoyjxrm4ko2fm3uhpvfvam6e\nsystem bafk2bzacecyf523quuq2kdjfdvyty446z2ounmamtgtgeqnr3ynlu5cqrlt6e\nverifiedregistry bafk2bzacedkxehp7y7iyukbcje3wbpqcvufisos6exatkanyrbotoecdkrbta\n")])])])]),e._v(" "),a("li",[a("p",[e._v("If you are not troubleshooting the system, it is not recommended to set the rust log level to "),a("code",[e._v("trace")]),e._v(" because more logs will be printed.")])]),e._v(" "),a("li",[a("p",[e._v("After the upgrade, you can use the command "),a("code",[e._v("./venus state get-actor t01000")]),e._v(" to confirm whether the upgrade is successful.")])]),e._v(" "),a("li",[a("p",[e._v("actor migration")]),e._v(" "),a("p",[a("strong",[e._v("After testing, the pre-migration time is about 30 minutes, and the main migration time is about 100 seconds")])]),e._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[e._v("The pre-migration height is 120 heights before the upgrade height:\npre-migration start: STARTING pre-migration end: COMPLETED pre-migration\nmigration starts: STARTING migration ends: COMPLETED migration\n")])])])]),e._v(" "),a("li",[a("p",[e._v("If "),a("code",[e._v("~/.venus")]),e._v(" exists and you need to import a snapshot, you need to delete the "),a("code",[e._v("~/.venus/version")]),e._v(" file first and then import the snapshot.")]),e._v(" "),a("ul",[a("li",[e._v("Mainnet: "),a("code",[e._v("./venus daemon --import-snapshot snapshot.car")])]),e._v(" "),a("li",[e._v("calibnet: "),a("code",[e._v("./venus daemon --import-snapshot snapshot.car --network calibrationnet")])])])])]),e._v(" "),a("h3",{attrs:{id:"sophon-gateway"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-gateway"}},[e._v("#")]),e._v(" sophon-gateway")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("sophon-auth")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("When compiling, you need to first "),a("code",[e._v("make dist-clean")]),e._v(" and then "),a("code",[e._v("make")])])]),e._v(" "),a("h3",{attrs:{id:"sophon-messager"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-messager"}},[e._v("#")]),e._v(" sophon-messager")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("sophon-auth")]),e._v(" "),a("li",[e._v("sophon-gateway")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("After the upgrade, you need to observe whether the messages can be received normally and whether the messages can be on-chained normally.")])]),e._v(" "),a("h3",{attrs:{id:"sophon-miner"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#sophon-miner"}},[e._v("#")]),e._v(" sophon-miner")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("auth")]),e._v(" "),a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("gateway")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("h3",{attrs:{id:"droplet"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#droplet"}},[e._v("#")]),e._v(" droplet")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("Direct data onboarding support; Documentation "),a("a",{attrs:{href:"https://github.com/ipfs-force-community/droplet/blob/master/docs/zh/direct-on-boarding.md",target:"_blank",rel:"noopener noreferrer"}},[e._v("here"),a("OutboundLink")],1)])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("auth")]),e._v(" "),a("li",[e._v("venus")]),e._v(" "),a("li",[e._v("gateway")]),e._v(" "),a("li",[e._v("messager")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("Check if deals and retrieval can be issued normally after the upgrade?")])]),e._v(" "),a("h3",{attrs:{id:"venus-wallet"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus-wallet"}},[e._v("#")]),e._v(" venus-wallet")]),e._v(" "),a("p",[e._v("Affected functions:")]),e._v(" "),a("ul",[a("li",[e._v("None")])]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("gateway")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("After the upgrade, observe whether the signing is normal and whether the message can be on-chained normally.")])]),e._v(" "),a("h3",{attrs:{id:"damocles-manager"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#damocles-manager"}},[e._v("#")]),e._v(" damocles-manager")]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("Sophon service")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("ul",[a("li",[e._v("When compiling, you need to first "),a("code",[e._v("make dist-clean")]),e._v(" and then "),a("code",[e._v("make")])])]),e._v(" "),a("h3",{attrs:{id:"damocles-worker"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#damocles-worker"}},[e._v("#")]),e._v(" damocles-worker")]),e._v(" "),a("p",[e._v("Upgrade Dependency:")]),e._v(" "),a("ul",[a("li",[e._v("damocles-manager")])]),e._v(" "),a("p",[e._v("Precautions:")]),e._v(" "),a("p",[e._v("Upgrade result verification steps:")]),e._v(" "),a("ol",[a("li",[e._v("Check if the program starts normally")]),e._v(" "),a("li",[e._v("Check if pre / pro messages are uploaded normally")]),e._v(" "),a("li",[e._v("Check if block producing is normal")]),e._v(" "),a("li",[e._v("Check if windowPost is normal")]),e._v(" "),a("li",[e._v("Check if storage power grows normally")]),e._v(" "),a("li",[e._v("Check if verified deal retrieval is normal")]),e._v(" "),a("li",[e._v("Check if various gas, sector life cycle, and aggregation settings in the database are normal.")])]),e._v(" "),a("h3",{attrs:{id:"database-changes"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#database-changes"}},[e._v("#")]),e._v(" Database changes")]),e._v(" "),a("ol",[a("li",[e._v("The droplet adds the "),a("code",[e._v("direct_deals")]),e._v(" table to store DD\nO deals.")])])])}),[],!1,null,null,null);t.default=r.exports}}]); \ No newline at end of file diff --git a/assets/js/39.547ee956.js b/assets/js/39.918ef1f6.js similarity index 97% rename from assets/js/39.547ee956.js rename to assets/js/39.918ef1f6.js index 78d13b2a7..c959334dc 100644 --- a/assets/js/39.547ee956.js +++ b/assets/js/39.918ef1f6.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[39],{425:function(v,_,l){"use strict";l.r(_);var i=l(17),s=Object(i.a)({},(function(){var v=this,_=v.$createElement,l=v._self._c||_;return l("ContentSlotsDistributor",{attrs:{"slot-key":v.$parent.slotKey}},[l("h2",{attrs:{id:"原则"}},[l("a",{staticClass:"header-anchor",attrs:{href:"#原则"}},[v._v("#")]),v._v(" 原则")]),v._v(" "),l("p",[v._v("  基于目前的需要，先从重构 guide 和 modules 模块，让两块联动，形成比较易读的 venus 集群部署介绍。")]),v._v(" "),l("ul",[l("li",[l("p",[v._v("modules 模块存储各组件的简介，将不相干的文档移到对应位置")])]),v._v(" "),l("li",[l("p",[v._v("guide 和 modules 对于组件介绍存在很多重复的，只保留一份")])]),v._v(" "),l("li",[l("p",[v._v("modules 模块组件介绍老旧，超链接到项目的介绍文档，避免项目内更新后 doc 中不及时及重复劳动")])]),v._v(" "),l("li",[l("p",[v._v("guide 将组件介绍，编译构建，部署文档独立")])]),v._v(" "),l("li",[l("p",[v._v("guide 模块增加 QA 模块，将 venus discussion 的问题以超链接方式统一到 QA 模块")])]),v._v(" "),l("li",[l("p",[v._v("部署模块尽量少一些设计的介绍，简明扼要，每个指定的操作尽量不涉及不相干的，以免造成误解")])])]),v._v(" "),l("h2",{attrs:{id:"todo-list"}},[l("a",{staticClass:"header-anchor",attrs:{href:"#todo-list"}},[v._v("#")]),v._v(" TODO list")]),v._v(" "),l("ul",[l("li",[l("p",[v._v("[ ] modules 模块")]),v._v(" "),l("ul",[l("li",[v._v("[ ] 引导页内容更新")]),v._v(" "),l("li",[v._v("[ ] 不相关文档移走")]),v._v(" "),l("li",[v._v("[ ] 文档命名一致")]),v._v(" "),l("li",[v._v("[ ] 组件介绍匹配项目进度")]),v._v(" "),l("li",[v._v("[x] 编译构建独立到一个文档")]),v._v(" "),l("li",[v._v("[ ] 组件文档移除从项目中搬过来的内容，用超链接")]),v._v(" "),l("li",[v._v("[ ] market 和 cluster 模块的技术文档移到 modules 模块，")])])]),v._v(" "),l("li",[l("p",[v._v("[ ] guide 模块")]),v._v(" "),l("ul",[l("li",[v._v("[ ] 将部署用到的基础知识单独形成文档")]),v._v(" "),l("li",[v._v("[x] 编译构建超链接到对应文档")]),v._v(" "),l("li",[v._v("[x] 增加部分组件的验证：怎么判断部署成功")]),v._v(" "),l("li",[v._v("[ ] 目录结构调整\n"),l("ul",[l("li",[v._v("[ ] market 和 cluster 归属到链服务部署和独立组件部署文档")]),v._v(" "),l("li",[v._v("[ ] .fil_withdraw_and_send.md.swp 文件删除")]),v._v(" "),l("li",[v._v("[ ] sealer 文档放到单独的目录")])])]),v._v(" "),l("li",[v._v("[ ] Troubleshooting-&-FAQ.md 用超链接方式管理 venus discussion")])])]),v._v(" "),l("li",[l("p",[v._v("[ ] 移除没有价值或过时的文档")])]),v._v(" "),l("li",[l("p",[v._v("[ ] 在很多模块中重复的内容整合")])]),v._v(" "),l("li",[l("p",[v._v("[ ] 每个项目搬过来的内容使用超链接")])])])])}),[],!1,null,null,null);_.default=s.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[39],{424:function(v,_,l){"use strict";l.r(_);var i=l(17),s=Object(i.a)({},(function(){var v=this,_=v.$createElement,l=v._self._c||_;return l("ContentSlotsDistributor",{attrs:{"slot-key":v.$parent.slotKey}},[l("h2",{attrs:{id:"原则"}},[l("a",{staticClass:"header-anchor",attrs:{href:"#原则"}},[v._v("#")]),v._v(" 原则")]),v._v(" "),l("p",[v._v("  基于目前的需要，先从重构 guide 和 modules 模块，让两块联动，形成比较易读的 venus 集群部署介绍。")]),v._v(" "),l("ul",[l("li",[l("p",[v._v("modules 模块存储各组件的简介，将不相干的文档移到对应位置")])]),v._v(" "),l("li",[l("p",[v._v("guide 和 modules 对于组件介绍存在很多重复的，只保留一份")])]),v._v(" "),l("li",[l("p",[v._v("modules 模块组件介绍老旧，超链接到项目的介绍文档，避免项目内更新后 doc 中不及时及重复劳动")])]),v._v(" "),l("li",[l("p",[v._v("guide 将组件介绍，编译构建，部署文档独立")])]),v._v(" "),l("li",[l("p",[v._v("guide 模块增加 QA 模块，将 venus discussion 的问题以超链接方式统一到 QA 模块")])]),v._v(" "),l("li",[l("p",[v._v("部署模块尽量少一些设计的介绍，简明扼要，每个指定的操作尽量不涉及不相干的，以免造成误解")])])]),v._v(" "),l("h2",{attrs:{id:"todo-list"}},[l("a",{staticClass:"header-anchor",attrs:{href:"#todo-list"}},[v._v("#")]),v._v(" TODO list")]),v._v(" "),l("ul",[l("li",[l("p",[v._v("[ ] modules 模块")]),v._v(" "),l("ul",[l("li",[v._v("[ ] 引导页内容更新")]),v._v(" "),l("li",[v._v("[ ] 不相关文档移走")]),v._v(" "),l("li",[v._v("[ ] 文档命名一致")]),v._v(" "),l("li",[v._v("[ ] 组件介绍匹配项目进度")]),v._v(" "),l("li",[v._v("[x] 编译构建独立到一个文档")]),v._v(" "),l("li",[v._v("[ ] 组件文档移除从项目中搬过来的内容，用超链接")]),v._v(" "),l("li",[v._v("[ ] market 和 cluster 模块的技术文档移到 modules 模块，")])])]),v._v(" "),l("li",[l("p",[v._v("[ ] guide 模块")]),v._v(" "),l("ul",[l("li",[v._v("[ ] 将部署用到的基础知识单独形成文档")]),v._v(" "),l("li",[v._v("[x] 编译构建超链接到对应文档")]),v._v(" "),l("li",[v._v("[x] 增加部分组件的验证：怎么判断部署成功")]),v._v(" "),l("li",[v._v("[ ] 目录结构调整\n"),l("ul",[l("li",[v._v("[ ] market 和 cluster 归属到链服务部署和独立组件部署文档")]),v._v(" "),l("li",[v._v("[ ] .fil_withdraw_and_send.md.swp 文件删除")]),v._v(" "),l("li",[v._v("[ ] sealer 文档放到单独的目录")])])]),v._v(" "),l("li",[v._v("[ ] Troubleshooting-&-FAQ.md 用超链接方式管理 venus discussion")])])]),v._v(" "),l("li",[l("p",[v._v("[ ] 移除没有价值或过时的文档")])]),v._v(" "),l("li",[l("p",[v._v("[ ] 在很多模块中重复的内容整合")])]),v._v(" "),l("li",[l("p",[v._v("[ ] 每个项目搬过来的内容使用超链接")])])])])}),[],!1,null,null,null);_.default=s.exports}}]); \ No newline at end of file diff --git a/assets/js/40.6e81209f.js b/assets/js/40.f404f97c.js similarity index 97% rename from assets/js/40.6e81209f.js rename to assets/js/40.f404f97c.js index 544ac2796..c00065bce 100644 --- a/assets/js/40.6e81209f.js +++ b/assets/js/40.f404f97c.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[40],{424:function(e,t,r){"use strict";r.r(t);var n=r(17),a=Object(n.a)({},(function(){var e=this,t=e.$createElement,r=e._self._c||t;return r("ContentSlotsDistributor",{attrs:{"slot-key":e.$parent.slotKey}},[r("h2",{attrs:{id:"使命-愿景-价值观"}},[r("a",{staticClass:"header-anchor",attrs:{href:"#使命-愿景-价值观"}},[e._v("#")]),e._v(" 使命，愿景，价值观")]),e._v(" "),r("ul",[r("li",[e._v("❗️使命：建设 Filecoin 基础设施和工具，支持生态繁荣发展")]),e._v(" "),r("li",[e._v("🌏 愿景：人人都能参与 Filecoin 生态")]),e._v(" "),r("li",[e._v("☯️ 价值观：开放并且去信任")])]),e._v(" "),r("h2",{attrs:{id:"联系方式"}},[r("a",{staticClass:"header-anchor",attrs:{href:"#联系方式"}},[e._v("#")]),e._v(" 联系方式")]),e._v(" "),r("ul",[r("li",[e._v("Slack:"),r("a",{attrs:{href:"https://filecoinproject.slack.com/archives/CEHHJNJS3",target:"_blank",rel:"noopener noreferrer"}},[e._v("#fil-venus"),r("OutboundLink")],1),e._v(", Slack:"),r("a",{attrs:{href:"https://filecoinproject.slack.com/archives/C028PCH8L31",target:"_blank",rel:"noopener noreferrer"}},[e._v("#fil-venus-cn"),r("OutboundLink")],1),e._v(", "),r("a",{attrs:{href:"mailto:venus@ipfsforce.com"}},[e._v("venus@ipfsforce.com")])])]),e._v(" "),r("h2",{attrs:{id:"其他资源"}},[r("a",{staticClass:"header-anchor",attrs:{href:"#其他资源"}},[e._v("#")]),e._v(" 其他资源")]),e._v(" "),r("ul",[r("li",[e._v("venus-docs: "),r("a",{attrs:{href:"venus.filecoin.io"}},[e._v("venus.filecoin.io")])]),e._v(" "),r("li",[e._v("VenusHub: "),r("a",{attrs:{href:"venushub.io"}},[e._v("venushub.io")])]),e._v(" "),r("li",[e._v("Github: "),r("a",{attrs:{href:"https://github.com/filecoin-project/venus",target:"_blank",rel:"noopener noreferrer"}},[e._v("venus"),r("OutboundLink")],1)]),e._v(" "),r("li",[e._v("Social Media: "),r("a",{attrs:{href:"https://twitter.com/venus_filecoin",target:"_blank",rel:"noopener noreferrer"}},[e._v("Twitter"),r("OutboundLink")],1),e._v(", "),r("a",{attrs:{href:"https://mp.weixin.qq.com/s/p4_ch03QeMMXxPyakr_8XQ",target:"_blank",rel:"noopener noreferrer"}},[e._v("Wechat"),r("OutboundLink")],1)]),e._v(" "),r("li",[e._v("安全审计报告："),r("a",{attrs:{href:"https://leastauthority.com/static/publications/LeastAuthority_Filecoin_Foundation_Venus_Final_Audit_Report.pdf",target:"_blank",rel:"noopener noreferrer"}},[e._v("link"),r("OutboundLink")],1)])])])}),[],!1,null,null,null);t.default=a.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[40],{425:function(e,t,r){"use strict";r.r(t);var n=r(17),a=Object(n.a)({},(function(){var e=this,t=e.$createElement,r=e._self._c||t;return r("ContentSlotsDistributor",{attrs:{"slot-key":e.$parent.slotKey}},[r("h2",{attrs:{id:"使命-愿景-价值观"}},[r("a",{staticClass:"header-anchor",attrs:{href:"#使命-愿景-价值观"}},[e._v("#")]),e._v(" 使命，愿景，价值观")]),e._v(" "),r("ul",[r("li",[e._v("❗️使命：建设 Filecoin 基础设施和工具，支持生态繁荣发展")]),e._v(" "),r("li",[e._v("🌏 愿景：人人都能参与 Filecoin 生态")]),e._v(" "),r("li",[e._v("☯️ 价值观：开放并且去信任")])]),e._v(" "),r("h2",{attrs:{id:"联系方式"}},[r("a",{staticClass:"header-anchor",attrs:{href:"#联系方式"}},[e._v("#")]),e._v(" 联系方式")]),e._v(" "),r("ul",[r("li",[e._v("Slack:"),r("a",{attrs:{href:"https://filecoinproject.slack.com/archives/CEHHJNJS3",target:"_blank",rel:"noopener noreferrer"}},[e._v("#fil-venus"),r("OutboundLink")],1),e._v(", Slack:"),r("a",{attrs:{href:"https://filecoinproject.slack.com/archives/C028PCH8L31",target:"_blank",rel:"noopener noreferrer"}},[e._v("#fil-venus-cn"),r("OutboundLink")],1),e._v(", "),r("a",{attrs:{href:"mailto:venus@ipfsforce.com"}},[e._v("venus@ipfsforce.com")])])]),e._v(" "),r("h2",{attrs:{id:"其他资源"}},[r("a",{staticClass:"header-anchor",attrs:{href:"#其他资源"}},[e._v("#")]),e._v(" 其他资源")]),e._v(" "),r("ul",[r("li",[e._v("venus-docs: "),r("a",{attrs:{href:"venus.filecoin.io"}},[e._v("venus.filecoin.io")])]),e._v(" "),r("li",[e._v("VenusHub: "),r("a",{attrs:{href:"venushub.io"}},[e._v("venushub.io")])]),e._v(" "),r("li",[e._v("Github: "),r("a",{attrs:{href:"https://github.com/filecoin-project/venus",target:"_blank",rel:"noopener noreferrer"}},[e._v("venus"),r("OutboundLink")],1)]),e._v(" "),r("li",[e._v("Social Media: "),r("a",{attrs:{href:"https://twitter.com/venus_filecoin",target:"_blank",rel:"noopener noreferrer"}},[e._v("Twitter"),r("OutboundLink")],1),e._v(", "),r("a",{attrs:{href:"https://mp.weixin.qq.com/s/p4_ch03QeMMXxPyakr_8XQ",target:"_blank",rel:"noopener noreferrer"}},[e._v("Wechat"),r("OutboundLink")],1)]),e._v(" "),r("li",[e._v("安全审计报告："),r("a",{attrs:{href:"https://leastauthority.com/static/publications/LeastAuthority_Filecoin_Foundation_Venus_Final_Audit_Report.pdf",target:"_blank",rel:"noopener noreferrer"}},[e._v("link"),r("OutboundLink")],1)])])])}),[],!1,null,null,null);t.default=a.exports}}]); \ No newline at end of file diff --git a/assets/js/43.48f0a14d.js b/assets/js/43.5464da8f.js similarity index 99% rename from assets/js/43.48f0a14d.js rename to assets/js/43.5464da8f.js index 69f1b0aa0..941ffc6cc 100644 --- a/assets/js/43.48f0a14d.js +++ b/assets/js/43.5464da8f.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[43],{432:function(t,s,a){"use strict";a.r(s);var e=a(17),r=Object(e.a)({},(function(){var t=this,s=t.$createElement,a=t._self._c||s;return a("ContentSlotsDistributor",{attrs:{"slot-key":t.$parent.slotKey}},[a("h1",{attrs:{id:"venus-集群最大化利用资源增长算力方案"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus-集群最大化利用资源增长算力方案"}},[t._v("#")]),t._v(" Venus-集群最大化利用资源增长算力方案")]),t._v(" "),a("p",[t._v("   在 Filecoin 的网络中，算力大小至关重要，与矿工的收入息息相关。算力的增长与维持需要软硬件资源较多，每个扇区的密封需要 P1、P2、C1，C2 等\n诸多过程，并且每个过程所依赖的资源各不相同，如：P1 偏向多核 CPU，P4 可用 GPU 优化等。故如何找出能最大化利用现有资源提升算力的方案是一个复杂的过程。这篇文章为如何找出最优方案提供一些思路。")]),t._v(" "),a("h2",{attrs:{id:"总体思路"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#总体思路"}},[t._v("#")]),t._v(" 总体思路")]),t._v(" "),a("blockquote",[a("p",[t._v("本文方案是通过各个阶段的任务耗时来推算如何均衡的分配各阶段任务的机器数量占比")])]),t._v(" "),a("ul",[a("li",[t._v("根据实际场景，将所有加速配置都打开，做几个 sector，统计每个阶段任务耗时。每个阶段对硬件资源的的依赖如下：\n"),a("ul",[a("li",[t._v("P1：cpu 及磁盘 io")])]),t._v(" "),a("ul",[a("li",[t._v("P2：cpu，gpu，带宽及磁盘 io")]),t._v(" "),a("li",[t._v("C1-C2：cpu，gpu，带宽及磁盘 io")])])])]),t._v(" "),a("blockquote",[a("p",[t._v("这里多做几个是为了统计出较稳定的耗时，此阶段需保持加速设置及软硬件资源始终不变。")])]),t._v(" "),a("ul",[a("li",[a("p",[t._v("维持任务数平衡，即每个机器都有任何时刻都有任务可做，理论上每个阶段任务数与耗时成反比；")])]),t._v(" "),a("li",[a("p",[t._v("扇区任务由 pledge 命令控制，配合最大并发密封扇区数（MaxSealingSectors）管理集群中 sector 并发数量；")])]),t._v(" "),a("li",[a("p",[t._v("每个 worker 可以指定可接受的任务类型。")])])]),t._v(" "),a("h2",{attrs:{id:"任务耗时统计"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#任务耗时统计"}},[t._v("#")]),t._v(" 任务耗时统计")]),t._v(" "),a("p",[t._v("   worker 可以领取的任务类型有：")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v('TTAddPiece TaskType = "seal/v0/addpiece"\nTTPreCommit1 TaskType = "seal/v0/precommit/1"\nTTPreCommit2 TaskType = "seal/v0/precommit/2"\nTTCommit1 TaskType = "seal/v0/commit/1" // NOTE: We use this to transfer the sector into miner-local storage for now; Don\'t use on workers!\nTTCommit2 TaskType = "seal/v0/commit/2"\n\nTTFinalize TaskType = "seal/v0/finalize"\n\nTTFetch TaskType = "seal/v0/fetch"\nTTUnseal TaskType = "seal/v0/unseal"\n\n')])])]),a("p",[t._v("   每个任务都分为两个阶段：prepare 阶段和 worker 阶段，在日志中表现为：")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v("# seal/v0/fetch\n2021-08-03T14:00:07.925+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 7 prepare for seal/v0/fetch ...\n2021-08-03T14:05:36.772+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 7 prepare for seal/v0/fetch end ...\n\n2021-08-03T14:05:36.772+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 7 work for seal/v0/fetch ...\n2021-08-03T14:05:36.774+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 7 work for seal/v0/fetch end ...\n\n# seal/v0/addpiece\n2021-08-03T13:38:37.977+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 8 prepare for seal/v0/addpiece ...\n2021-08-03T13:38:37.978+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 8 prepare for seal/v0/addpiece end ...\n\n2021-08-03T13:38:37.978+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 8 work for seal/v0/addpiece ...\n2021-08-03T13:44:26.295+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 8 work for seal/v0/addpiece end ...\n\n# seal/v0/commit/2\n2021-08-03T13:26:02.119+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 7 prepare for seal/v0/commit/2 ...\n2021-08-03T13:26:02.119+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 7 prepare for seal/v0/commit/2 end ...\n\n2021-08-03T13:26:02.119+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 7 work for seal/v0/commit/2 ...\n2021-08-03T13:49:46.180+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 7 work for seal/v0/commit/2 end ...\n\n# seal/v0/finalize\n2021-08-03T13:54:17.414+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 7 prepare for seal/v0/finalize ...\n2021-08-03T13:59:30.471+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 7 prepare for seal/v0/finalize end ...\n\n2021-08-03T13:59:30.471+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 7 work for seal/v0/finalize ...\n2021-08-03T14:00:07.915+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 7 work for seal/v0/finalize end ...\n\n")])])]),a("p",[t._v("   可以看出有些任务在 prepare 阶段比较耗时，有些在 work 阶段比较耗时，一般来说需要网路传输，带宽资源的在 prepare 比较耗时，如 fetch，finalize 等；而需要计算的任务在 work 阶段比较耗时，如 AP，P1，P2，C2 等。")]),t._v(" "),a("p",[t._v("   为了便于计算，这里将任务阶段进行合并，主要分为：AP，P1，P2，C2 阶段，将这四个阶段之前的仍无耗时统一归为相应阶段的耗时，如 T（P1）=P1 耗时+P1 前的 fetch 耗时。这里 waitseed 怎么归类，在后面的时间逻辑中有没有考虑进去")]),t._v(" "),a("h2",{attrs:{id:"速率因子"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#速率因子"}},[t._v("#")]),t._v(" 速率因子")]),t._v(" "),a("h3",{attrs:{id:"临时存储设备"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#临时存储设备"}},[t._v("#")]),t._v(" 临时存储设备")]),t._v(" "),a("p",[t._v("  Filecoin 在封装算力是会产生一些临时文件，在任务的进行中存在很多随机存取，这就要求磁盘吞吐量不能太差，否则会导致磁盘 IO 过高，计算资源等待磁盘读取处于闲置状态。")]),t._v(" "),a("ul",[a("li",[t._v("如何挑选适合的设备")])]),t._v(" "),a("p",[t._v("  如何寻找适合的设备，其实就是需要多少的磁盘吞吐量，可以通过一个简单的计算公式得到它。")]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[t._v("文件大小 * 线程并行数量 / 运行时间 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 平均每秒钟传输速度\n \n因为每个阶段的吞吐不同，拆分计算可以让得到的数据更精准\n \nP1 读取 + P1 写入 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" P1 阶段所需的吞吐量，其他阶段相同，把所有阶段所需的吞吐加起来就得到了所需的吞吐量，当然需要一些性能上的冗余\n")])])]),a("p",[t._v("  通常情况下绝大多数的矿工都会使用 SSD 或者 NVME，当有多块硬盘时我们可以通过"),a("code",[t._v("venus-worker storage attach --seal ")]),t._v("命令或者启动多个 worker 来设置多个路径，但这并不是一个比较好的方法，路径过于分散会导致后续的维护相对复杂，无法充分利用，通过创建 raid 方式可以获得更好的性能和空间利用率，并且便于后续的维护。")]),t._v(" "),a("ul",[a("li",[t._v("软 raid 创建")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token function"}},[t._v("mdadm")]),t._v(" -C /dev/md1 -l "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v(" -n "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("2")]),t._v(" /dev/sdb1 /dev/sdc1\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("mdadm")]),t._v(" -C /dev/md2 -l "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("5")]),t._v(" -n "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("6")]),t._v(" /dev/sd"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("[")]),t._v("b-g"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("]")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v("\n-C $创建软件RAID\n-l $指定RAID级别 "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v("表示raid1 其他同理 \n-n $指定磁盘个数\n-x $指定备用设备个数\n-A $重组之前的设备\n")])])]),a("p",[t._v("​\t有关 mdadm 用法、MD 和各种级别的 RAID 的更多信息，请参阅：http://raid.wiki.kernel.org/")]),t._v(" "),a("p",[t._v("​\t获取最新版本的 mdadm 应始终可以从如下链接获取：http://www.kernel.org/pub/linux/utils/raid/mdadm/")]),t._v(" "),a("p",[t._v("​\t硬 raid 创建时请查看您的 raid 卡型号和说明进行操作")]),t._v(" "),a("h3",{attrs:{id:"永久存储设备"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#永久存储设备"}},[t._v("#")]),t._v(" 永久存储设备")]),t._v(" "),a("p",[t._v("   永久存储设备的访问机制和可能遇到的问题：")]),t._v(" "),a("ol",[a("li",[t._v("在每个任务阶段产生的文件有些是要永久存储的，用于 wdPoSt 或 winningPoSt，在每个 sector 完成阶段需要传输到永久存储目录，这个过程需要带宽资源，并且要保证磁盘 io；")]),t._v(" "),a("li",[t._v("wdPoSt 大量的随机读取非常小的文件，这可能会导致读取过慢而影响时空证明导致算力惩罚；")]),t._v(" "),a("li",[t._v("当存储过于集中时，少量的机器损坏会导致所有的数据丢失；")]),t._v(" "),a("li",[t._v("当磁盘过多时，并且盘符没有固定，启动时可能导致盘符移动；")]),t._v(" "),a("li",[t._v("如果是 raid，尽量选择 raid5 或者 raid6，raid10 这种冗余性更高的方式；")]),t._v(" "),a("li",[t._v("需要监控磁盘空间利用率并报警。")])]),t._v(" "),a("h3",{attrs:{id:"网络传输"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#网络传输"}},[t._v("#")]),t._v(" 网络传输")]),t._v(" "),a("p",[t._v("   网络传输会有两个部分：")]),t._v(" "),a("ul",[a("li",[a("p",[t._v("临时数据的网络传输，某个阶段的任务需要上个阶段的数据时会用 http 协议请求所需文件，需要保证传输时间小于计算时间。")]),t._v(" "),a("p",[t._v("举例：\n传输往往和计算是同步进行的")]),t._v(" "),a("p",[t._v("传输时间 > 计算时间 资源闲置，计算资源等待网络资源，拉长整个扇区封装的声明周期，就是降产")]),t._v(" "),a("p",[t._v("传输时间 < 计算时间 计算资源充分利用")]),t._v(" "),a("ul",[a("li",[a("p",[t._v("观察计算资源是否出现闲置")])]),t._v(" "),a("li",[a("p",[t._v("计算网络传输速度能否满足计算时间")]),t._v(" "),a("p",[t._v("Precommit2 如果计算耗时 25 分钟，读取 440G 左右文件，写入 100G 左右文件"),a("br"),t._v("\n(440G * 1024 / 25 / 60) + (100G * 1024 / 25 / 60) = 单个线程所需的吞吐量")])]),t._v(" "),a("li",[a("p",[t._v("多台机器同步阶段的文件传输")]),t._v(" "),a("p",[t._v("我们有 A，B，C 三个机器分别负责 P1，P2，Commit")]),t._v(" "),a("p",[t._v("当 A 机器开始 P1 时会向 B 机器的 P2 传输 32G 左右的 Unsealed")]),t._v(" "),a("p",[t._v("当 B 机器开始 P2 时，A 机器的 P1 生成的 440G 左右所有文件会传输到 B 的机器上")]),t._v(" "),a("p",[t._v("Commit 又分为 C1 和 C2.当 C 机器运行 C1 时需要 P1 和 P2 的所有文件，计算的结果通过内存直接传递给 C2，所以并不会在落盘新的文件")])])])]),t._v(" "),a("li",[a("p",[t._v("最终数据传输，我们要知道当最终的存储也会成为我们的产量瓶颈（貌似和下面的不符合）")]),t._v(" "),a("ol",[a("li",[a("p",[t._v("假设计算资源的产量是每天产出 6T 的算力，但如果存储的网络传输最大每天只能传输 5T，那么这就会导致产量的下降")])]),t._v(" "),a("li",[a("p",[t._v("如果我们使用了 NFS 这样的网络文件系统，当网络断开链接是，NFS 往往是会直接卡死的，所以可能需要设置 NFS 的超时机制")])])])])]),t._v(" "),a("h3",{attrs:{id:"worker-的指令集加速"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#worker-的指令集加速"}},[t._v("#")]),t._v(" worker 的指令集加速")]),t._v(" "),a("p",[t._v("   P1 阶段时，使用 SHA 指令集和不使用指令集会有巨大的差距，目前大多数矿工都采用 AMD 型号的 CPU 原因就是 SHA 指令集的关系，研究发现，使用 SHA 指令集基本可以跑进 250 分钟以内，但不使用 SHA 指令集能够跑进 420 分钟已经非常艰难了")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v("确保编译时使用RUSTFLAGS=\"-C target-cpu=native -g\" FFI_BUILD_FROM_SOURCE=\"1\" 源码编译filecoin-ffi库，如果cpu支持则启用SHA扩展，这会大幅提高扇区封装速度，源码编译（make deps）时特征如下:\n\n+ trap '{ rm -f $__build_output_log_tmp; }' EXIT\n+ local '__rust_flags=--print native-static-libs -C target-feature=+sse2'\n+ RUSTFLAGS='--print native-static-libs -C target-feature=+sse2'\n+ cargo +nightly-2021-04-24 build --release --no-default-features --features multicore-sdr --features pairing,gpu\n+ tee /tmp/tmp.IYtnd3xka9\n Compiling autocfg v1.0.1\n Compiling libc v0.2.97\n Compiling cfg-if v1.0.0\n Compiling proc-macro2 v1.0.27\n Compiling unicode-xid v0.2.2\n Compiling syn v1.0.73\n Compiling lazy_static v1.4.0\n Compiling cc v1.0.68\n Compiling typenum v1.13.0\n Compiling serde_derive v1.0.126\n Compiling serde v1.0.126\n")])])]),a("h3",{attrs:{id:"核数限制"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#核数限制"}},[t._v("#")]),t._v(" 核数限制")]),t._v(" "),a("p",[t._v("​\t当想要把 CPU 的资源利用的更高时，需要非常合理的规划 CPU 的使用，比如有一个 64 核的 CPU，我们要想 PreCommit2 和 Commit 分别分到 32 核，这样两种任务相互不受影响，也不会导致某一个占用大量的计算资源导致另一个卡住的情况，此时我们就需要利用到核数限制")]),t._v(" "),a("ul",[a("li",[t._v("通过"),a("code",[t._v("taskset")]),t._v("限核")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 当我们想要启动某个进程时，可以通过 taskset -c 0-31 这种方式来进行限核操作")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 例如")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("TRUST_PARAMS")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("nohup")]),t._v(" taskset -c "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("-32 ./venus-worker run "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v("\n--miner-addr"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("/ip4/sealer-ip/tcp/sealer-port"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v("\n--miner-token"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("token"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v(" \n--listen"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0.0")]),t._v(".0.0:345"),a("span",{pre:!0,attrs:{class:"token operator"}},[a("span",{pre:!0,attrs:{class:"token file-descriptor important"}},[t._v("8")]),t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("flags"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">>")]),t._v(" worker.log "),a("span",{pre:!0,attrs:{class:"token operator"}},[a("span",{pre:!0,attrs:{class:"token file-descriptor important"}},[t._v("2")]),t._v(">")]),a("span",{pre:!0,attrs:{class:"token file-descriptor important"}},[t._v("&1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("&")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 扩展使用 taskset -c 0-9,19-29,39-49 进行跳跃式限核")]),t._v("\n")])])]),a("p",[t._v("这种方式的弊端就在于不方便在程序运行时对核数进行实时调整")]),t._v(" "),a("ul",[a("li",[t._v("通过 Cgrep 限核")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 好的目录划分会帮助对多个进程的管理")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("sudo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("mkdir")]),t._v(" -p /sys/fs/cgroup/cpuset/Pre1-worker\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 设置能够使用的核数范围")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("sudo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("echo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("-31 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" /sys/fs/cgroup/cpuset/Pre1-worker/cpuset.cpus\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 加入进程的PID")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("sudo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("echo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("PID"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" /sys/fs/cgroup/cpuset/Pre1-worker/cgroup.procs\n")])])]),a("p",[t._v("Cgrep 是在进程启动之后加入到配置文件的，并且支持实时的修改核数限制，当然也可以尝试使用 docker 限核，但 docker 的限核也是通过 Cgrep 来实现，至于 Cgrep 其他的用法我们基本都用不到，就不一一说明了")]),t._v(" "),a("h2",{attrs:{id:"worker-运行方式和资源消耗"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#worker-运行方式和资源消耗"}},[t._v("#")]),t._v(" worker 运行方式和资源消耗")]),t._v(" "),a("h3",{attrs:{id:"p1-阶段"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#p1-阶段"}},[t._v("#")]),t._v(" P1 阶段")]),t._v(" "),a("ul",[a("li",[t._v("P1 阶段的加速因子")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_MAXIMIZE_CACHING")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 控制cache文件缓存到内存中，起到加速作用，会占用56G内存")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_USE_MULTICORE_SDR")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 控制P1阶段是否使用多核运行，他会占用单个CPU组，所以每个CPU缓存组只会运行一个任务")]),t._v("\n")])])]),a("p",[a("code",[t._v("P1")]),t._v("阶段有两种选择，可以选择更快的速度或者更少的 CPU，需要根据实际资源决定。")]),t._v(" "),a("ul",[a("li",[t._v("P1 的内存资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 内存中会存储56G的cache文件")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 加上2层layer文件，32G的矿工每层文件32G，64G每层文件64G")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 以32G矿工为例，如果我们同时运行了10个任务")]),t._v("\n \n56G cahce 文件 + "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("32")]),t._v(" *2 * 并行线程数 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 696G Mem\n")])])]),a("ul",[a("li",[t._v("P1 的磁盘资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 11层layer文件 ")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 64G的tree-d文件")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 32G的unsealed文件")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("11")]),t._v(" * 32G + "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("64")]),t._v(" + "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("32")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 440G\n")])])]),a("h3",{attrs:{id:"p2-阶段"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#p2-阶段"}},[t._v("#")]),t._v(" P2 阶段")]),t._v(" "),a("ul",[a("li",[t._v("P2 的加速因子有两个")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_USE_GPU_COLUMN_BUILDER")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 使用GPU运算tree-r-last阶段")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_USE_GPU_TREE_BUILDER")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 使用GPU运算tree-c阶段")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 任何环境变量都不增加的情况下使用CPU运算")]),t._v("\n")])])]),a("p",[t._v("从实验结果来看使用 GPU 运算要明显比 CPU 快得多，而 CPU 运算时的核数，主频跟时间是成线性比例的，CPU 核数越多速度越快，主频越高越快，反之亦然。")]),t._v(" "),a("ul",[a("li",[t._v("P2 内存资源")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[t._v("--precommit2 "),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("enable")]),t._v(" precommit2 "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("32G sectors: all cores, 96GiB Memory"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("default: "),a("span",{pre:!0,attrs:{class:"token boolean"}},[t._v("true")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 在命令行中可以看到运行一个需要96GiB的内存，如果并行2个就是2倍")]),t._v("\n")])])]),a("ul",[a("li",[t._v("P2 的磁盘资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 32G")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 8个tree-c文件，每个 4.6G左右")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 8个tree-r-last,每个9.2M")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# t_aux，4K，p_aux，4K")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 32G的sealed文件")]),t._v("\n \n----------------------\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 64G")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 16个tree-c文件，每个 4.6G左右")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 16个tree-r-last,每个9.2M")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# t_aux，4K，p_aux，4K")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 64G的sealed文件")]),t._v("\n")])])]),a("h3",{attrs:{id:"commit"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#commit"}},[t._v("#")]),t._v(" Commit")]),t._v(" "),a("ul",[a("li",[t._v("Commit 中的 C1 的磁盘资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# C1需要前面2个阶段产生的所有文件")]),t._v("\n\nP1 440G + P2 79G "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 519G \n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 每个C1的任务需要消耗487G左右的空间")]),t._v("\n")])])]),a("p",[t._v("C1 并没有太多的 CPU 消耗，并且时间极短")]),t._v(" "),a("ul",[a("li",[t._v("Commit 中的 C2 的运行方式，CPU 和 GPU")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("BELLMAN_NO_GPU")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 禁用GPU")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("BELLMAN_CUSTOM_GPU")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"GeForce RTX 3090:10496"')]),t._v(" \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 指定GPU的cuda核心数，当GPU型号比较冷门无法识别时可使用")]),t._v("\n")])])]),a("ul",[a("li",[t._v("C2 的内存资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("enable")]),t._v(" commit "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("32G sectors: all cores or GPUs, 128GiB Memory + 64GiB swap"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("default: "),a("span",{pre:!0,attrs:{class:"token boolean"}},[t._v("true")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 命令行中指出总共需要 128G + 64 G = 192G的内存")]),t._v("\n")])])]),a("h2",{attrs:{id:"产量优化"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#产量优化"}},[t._v("#")]),t._v(" 产量优化")]),t._v(" "),a("h3",{attrs:{id:"产量的计算公式"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#产量的计算公式"}},[t._v("#")]),t._v(" 产量的计算公式")]),t._v(" "),a("p",[t._v("  每个阶段的效率：")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v(" 产出数量 / 时间 = 效率\n \n # 得到效率之后，我们就可以很轻松的算出产量\n \n 效率/h/个数 * 24h * 32G = 日产量\n")])])]),a("p",[t._v("例如我们有 1 台机器")]),t._v(" "),a("p",[t._v("P1:240 分钟")]),t._v(" "),a("p",[t._v("P2:30 分钟")]),t._v(" "),a("p",[t._v("Commit：35 分钟")]),t._v(" "),a("p",[t._v("此时我们可以简单一个计算公式的表格")]),t._v(" "),a("table",[a("thead",[a("tr",[a("th",[t._v("运行阶段")]),t._v(" "),a("th",[t._v("时间/m")]),t._v(" "),a("th",[t._v("并行线程数")]),t._v(" "),a("th",[t._v("效率/时间h/个数")]),t._v(" "),a("th",[t._v("计算公式")])])]),t._v(" "),a("tbody",[a("tr",[a("td",[t._v("P1")]),t._v(" "),a("td",[t._v("240")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("0.25")]),t._v(" "),a("td",[t._v("= 1 / (240 /60)")])]),t._v(" "),a("tr",[a("td",[t._v("P2")]),t._v(" "),a("td",[t._v("30")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("2")]),t._v(" "),a("td",[t._v("= 1 / (30 /60)")])]),t._v(" "),a("tr",[a("td",[t._v("Commit")]),t._v(" "),a("td",[t._v("35")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("1.7142857143")]),t._v(" "),a("td",[t._v("= 1 / (35 /60)")])])])]),t._v(" "),a("h4",{attrs:{id:"如何找到每个阶段的最佳运行数量和配置"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#如何找到每个阶段的最佳运行数量和配置"}},[t._v("#")]),t._v(" 如何找到每个阶段的最佳运行数量和配置")]),t._v(" "),a("p",[t._v("   从上面的表格中我们明显看出 P1 的效率明显不足，而此时 P2 和 Commit 机器必定会闲置，如何处理呢？产出的时间无法调整，那么我们就可以调整并行的线程数，当然我们可以新增一些计算内存的公式来指导我们对内存的消耗")]),t._v(" "),a("table",[a("thead",[a("tr",[a("th",[t._v("运行阶段")]),t._v(" "),a("th",[t._v("时间/m")]),t._v(" "),a("th",[t._v("并行线程数")]),t._v(" "),a("th",[t._v("效率/时间h/个数")]),t._v(" "),a("th",[t._v("计算公式")]),t._v(" "),a("th",[t._v("日产量/G")]),t._v(" "),a("th",[t._v("公式")]),t._v(" "),a("th",[t._v("mem/G")])])]),t._v(" "),a("tbody",[a("tr",[a("td",[t._v("P1")]),t._v(" "),a("td",[t._v("240")]),t._v(" "),a("td",[t._v("7")]),t._v(" "),a("td",[t._v("1.75")]),t._v(" "),a("td",[t._v("= 7 / (240 /60)")]),t._v(" "),a("td",[t._v("1344")]),t._v(" "),a("td",[t._v("=7*64+56")]),t._v(" "),a("td",[t._v("504")])]),t._v(" "),a("tr",[a("td",[t._v("P2")]),t._v(" "),a("td",[t._v("30")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("2")]),t._v(" "),a("td",[t._v("= 1 / (30 /60)")]),t._v(" "),a("td",[t._v("1536")]),t._v(" "),a("td",[t._v("=1*96")]),t._v(" "),a("td",[t._v("96")])]),t._v(" "),a("tr",[a("td",[t._v("Commit")]),t._v(" "),a("td",[t._v("35")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("1.7142857143")]),t._v(" "),a("td",[t._v("= 1 / (35 /60)")]),t._v(" "),a("td",[t._v("1316.571429")]),t._v(" "),a("td",[t._v("=1*128+64")]),t._v(" "),a("td",[t._v("192")])])])]),t._v(" "),a("p",[t._v("现在三个阶段的效率已经非常接近了，但是此时我们仍然存在一些问题：")]),t._v(" "),a("ol",[a("li",[t._v("Commit 效率低于 P1，这会导致大量的任务阻塞到 Commit 阶段")]),t._v(" "),a("li",[t._v("当某个阶段的效率过高时就会出现闲置")]),t._v(" "),a("li",[t._v("我们需要微调资源的分布来尽可能的保证每个阶段的效率无限相等")])]),t._v(" "),a("h4",{attrs:{id:"集群方案运行的的可能性"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#集群方案运行的的可能性"}},[t._v("#")]),t._v(" 集群方案运行的的可能性")]),t._v(" "),a("p",[t._v("​\t\t当我们有多台机器时，我们就要决定某些机器运行哪些阶段，在这之前我们再来看下不同阶段的特性：")]),t._v(" "),a("ol",[a("li",[t._v("P1 : 极度消耗内存，可以单核，多核，并行运行，临时存储需要伴随着并行数量的增多而增多")]),t._v(" "),a("li",[t._v("P2 : 轻度消耗内存，CPU，GPU 都可以运行，如果拆分，需要传输大量的文件")]),t._v(" "),a("li",[t._v("Commit: 中度消耗内存，CPU，GPU 都可以运行，如果拆分，需要传输所有临时文件")])]),t._v(" "),a("p",[t._v("如果我们此时只考虑这些因素，那么我们的组合方式有多少种呢？而这些不同的组合方式一定会带来不通的产量，虽然每个矿工的机器都有所不同，但我们的目标是一样的：")]),t._v(" "),a("ol",[a("li",[t._v("更高的产量组合运行方式")]),t._v(" "),a("li",[t._v("各个阶段更加均衡的分布")])]),t._v(" "),a("p",[t._v("我们可能无法做到完美，但无限接近也是最好的结果")]),t._v(" "),a("h4",{attrs:{id:"如何寻找最佳的下发任务数-始终保持机器满负荷运行"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#如何寻找最佳的下发任务数-始终保持机器满负荷运行"}},[t._v("#")]),t._v(" 如何寻找最佳的下发任务数，始终保持机器满负荷运行")]),t._v(" "),a("p",[t._v("  当我们找到最佳的组合方式之后我们需要考虑的就是如何才能保证这些机器 24 小时都是不间断运行的呢？我们不希望任何一个阶段的出现闲置")]),t._v(" "),a("p",[t._v("当我们发现 P1 需要并行 7 个时，那么我们如果保证 P1 的任务量是充足的，那么后续的两个阶段在不考虑其他问题的情况下，也一定是充足的，所以我们需要保证始终维持 P1 时刻都有 7 个任务")]),t._v(" "),a("div",{staticClass:"language-toml extra-class"},[a("pre",{pre:!0,attrs:{class:"language-toml"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 在 venus-sealer 的配置文件中我们可以设置最大的任务数，这可以帮我我们避免任务数下发过多")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("DataDir")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"~/.venussealer"')]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("[")]),a("span",{pre:!0,attrs:{class:"token table class-name"}},[t._v("API")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("]")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("ListenAddress")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"/ip4/0.0.0.0/tcp/2345/http"')]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("RemoteListenAddress")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"192.168.200.6:2345"')]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("Timeout")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"30s"')]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("[")]),a("span",{pre:!0,attrs:{class:"token table class-name"}},[t._v("Sealing")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("]")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("MaxWaitDealsSectors")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("MaxSealingSectors")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("7")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 修改为 7")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("MaxSealingSectorsForDeals")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("\n")])])]),a("p",[t._v("此时我们可以通过一个简单的定时脚本就可以做到，始终维持最佳的任务量了")]),t._v(" "),a("h2",{attrs:{id:"损失和止损"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#损失和止损"}},[t._v("#")]),t._v(" 损失和止损")]),t._v(" "),a("p",[t._v("  如果一个任务执行错误之后又被反复的重试，这就像我们有 7 个通道进行算力的封装，但是此时有一通道阻塞或者损坏，这就会降低我们 1 / 7 的产量，所以及时的处理错误也是非常重要的")]),t._v(" "),a("ul",[a("li",[a("p",[t._v("何种情况下应该立刻抛弃任务")]),t._v(" "),a("ol",[a("li",[t._v("ticket 过期")]),t._v(" "),a("li",[t._v("Commit 过期")]),t._v(" "),a("li",[t._v("依赖文件损坏重试多次都未成功时;")])])]),t._v(" "),a("li",[a("p",[t._v("移除无法完成的 sector")])])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[t._v("venus-sealer sectors remove --really-do-it "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("sectorNum"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v("\n")])])]),a("p",[t._v("如遇到无法彻底删除请查询："),a("a",{attrs:{href:"https://github.com/filguard/lotus-ops/blob/master/documents/questions.md#1-%E9%A1%BD%E5%9B%BA%E6%89%87%E5%8C%BA%E5%A6%82%E4%BD%95%E5%88%A0%E9%99%A4",target:"_blank",rel:"noopener noreferrer"}},[t._v("顽固扇区如何删除"),a("OutboundLink")],1)])])}),[],!1,null,null,null);s.default=r.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[43],{433:function(t,s,a){"use strict";a.r(s);var e=a(17),r=Object(e.a)({},(function(){var t=this,s=t.$createElement,a=t._self._c||s;return a("ContentSlotsDistributor",{attrs:{"slot-key":t.$parent.slotKey}},[a("h1",{attrs:{id:"venus-集群最大化利用资源增长算力方案"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#venus-集群最大化利用资源增长算力方案"}},[t._v("#")]),t._v(" Venus-集群最大化利用资源增长算力方案")]),t._v(" "),a("p",[t._v("   在 Filecoin 的网络中，算力大小至关重要，与矿工的收入息息相关。算力的增长与维持需要软硬件资源较多，每个扇区的密封需要 P1、P2、C1，C2 等\n诸多过程，并且每个过程所依赖的资源各不相同，如：P1 偏向多核 CPU，P4 可用 GPU 优化等。故如何找出能最大化利用现有资源提升算力的方案是一个复杂的过程。这篇文章为如何找出最优方案提供一些思路。")]),t._v(" "),a("h2",{attrs:{id:"总体思路"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#总体思路"}},[t._v("#")]),t._v(" 总体思路")]),t._v(" "),a("blockquote",[a("p",[t._v("本文方案是通过各个阶段的任务耗时来推算如何均衡的分配各阶段任务的机器数量占比")])]),t._v(" "),a("ul",[a("li",[t._v("根据实际场景，将所有加速配置都打开，做几个 sector，统计每个阶段任务耗时。每个阶段对硬件资源的的依赖如下：\n"),a("ul",[a("li",[t._v("P1：cpu 及磁盘 io")])]),t._v(" "),a("ul",[a("li",[t._v("P2：cpu，gpu，带宽及磁盘 io")]),t._v(" "),a("li",[t._v("C1-C2：cpu，gpu，带宽及磁盘 io")])])])]),t._v(" "),a("blockquote",[a("p",[t._v("这里多做几个是为了统计出较稳定的耗时，此阶段需保持加速设置及软硬件资源始终不变。")])]),t._v(" "),a("ul",[a("li",[a("p",[t._v("维持任务数平衡，即每个机器都有任何时刻都有任务可做，理论上每个阶段任务数与耗时成反比；")])]),t._v(" "),a("li",[a("p",[t._v("扇区任务由 pledge 命令控制，配合最大并发密封扇区数（MaxSealingSectors）管理集群中 sector 并发数量；")])]),t._v(" "),a("li",[a("p",[t._v("每个 worker 可以指定可接受的任务类型。")])])]),t._v(" "),a("h2",{attrs:{id:"任务耗时统计"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#任务耗时统计"}},[t._v("#")]),t._v(" 任务耗时统计")]),t._v(" "),a("p",[t._v("   worker 可以领取的任务类型有：")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v('TTAddPiece TaskType = "seal/v0/addpiece"\nTTPreCommit1 TaskType = "seal/v0/precommit/1"\nTTPreCommit2 TaskType = "seal/v0/precommit/2"\nTTCommit1 TaskType = "seal/v0/commit/1" // NOTE: We use this to transfer the sector into miner-local storage for now; Don\'t use on workers!\nTTCommit2 TaskType = "seal/v0/commit/2"\n\nTTFinalize TaskType = "seal/v0/finalize"\n\nTTFetch TaskType = "seal/v0/fetch"\nTTUnseal TaskType = "seal/v0/unseal"\n\n')])])]),a("p",[t._v("   每个任务都分为两个阶段：prepare 阶段和 worker 阶段，在日志中表现为：")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v("# seal/v0/fetch\n2021-08-03T14:00:07.925+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 7 prepare for seal/v0/fetch ...\n2021-08-03T14:05:36.772+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 7 prepare for seal/v0/fetch end ...\n\n2021-08-03T14:05:36.772+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 7 work for seal/v0/fetch ...\n2021-08-03T14:05:36.774+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 7 work for seal/v0/fetch end ...\n\n# seal/v0/addpiece\n2021-08-03T13:38:37.977+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 8 prepare for seal/v0/addpiece ...\n2021-08-03T13:38:37.978+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 8 prepare for seal/v0/addpiece end ...\n\n2021-08-03T13:38:37.978+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 8 work for seal/v0/addpiece ...\n2021-08-03T13:44:26.295+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 8 work for seal/v0/addpiece end ...\n\n# seal/v0/commit/2\n2021-08-03T13:26:02.119+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 7 prepare for seal/v0/commit/2 ...\n2021-08-03T13:26:02.119+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 7 prepare for seal/v0/commit/2 end ...\n\n2021-08-03T13:26:02.119+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 7 work for seal/v0/commit/2 ...\n2021-08-03T13:49:46.180+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 7 work for seal/v0/commit/2 end ...\n\n# seal/v0/finalize\n2021-08-03T13:54:17.414+0800 INFO advmgr sector-storage/sched_worker.go:401 Sector 7 prepare for seal/v0/finalize ...\n2021-08-03T13:59:30.471+0800 INFO advmgr sector-storage/sched_worker.go:403 Sector 7 prepare for seal/v0/finalize end ...\n\n2021-08-03T13:59:30.471+0800 INFO advmgr sector-storage/sched_worker.go:442 Sector 7 work for seal/v0/finalize ...\n2021-08-03T14:00:07.915+0800 INFO advmgr sector-storage/sched_worker.go:444 Sector 7 work for seal/v0/finalize end ...\n\n")])])]),a("p",[t._v("   可以看出有些任务在 prepare 阶段比较耗时，有些在 work 阶段比较耗时，一般来说需要网路传输，带宽资源的在 prepare 比较耗时，如 fetch，finalize 等；而需要计算的任务在 work 阶段比较耗时，如 AP，P1，P2，C2 等。")]),t._v(" "),a("p",[t._v("   为了便于计算，这里将任务阶段进行合并，主要分为：AP，P1，P2，C2 阶段，将这四个阶段之前的仍无耗时统一归为相应阶段的耗时，如 T（P1）=P1 耗时+P1 前的 fetch 耗时。这里 waitseed 怎么归类，在后面的时间逻辑中有没有考虑进去")]),t._v(" "),a("h2",{attrs:{id:"速率因子"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#速率因子"}},[t._v("#")]),t._v(" 速率因子")]),t._v(" "),a("h3",{attrs:{id:"临时存储设备"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#临时存储设备"}},[t._v("#")]),t._v(" 临时存储设备")]),t._v(" "),a("p",[t._v("  Filecoin 在封装算力是会产生一些临时文件，在任务的进行中存在很多随机存取，这就要求磁盘吞吐量不能太差，否则会导致磁盘 IO 过高，计算资源等待磁盘读取处于闲置状态。")]),t._v(" "),a("ul",[a("li",[t._v("如何挑选适合的设备")])]),t._v(" "),a("p",[t._v("  如何寻找适合的设备，其实就是需要多少的磁盘吞吐量，可以通过一个简单的计算公式得到它。")]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[t._v("文件大小 * 线程并行数量 / 运行时间 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 平均每秒钟传输速度\n \n因为每个阶段的吞吐不同，拆分计算可以让得到的数据更精准\n \nP1 读取 + P1 写入 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" P1 阶段所需的吞吐量，其他阶段相同，把所有阶段所需的吞吐加起来就得到了所需的吞吐量，当然需要一些性能上的冗余\n")])])]),a("p",[t._v("  通常情况下绝大多数的矿工都会使用 SSD 或者 NVME，当有多块硬盘时我们可以通过"),a("code",[t._v("venus-worker storage attach --seal ")]),t._v("命令或者启动多个 worker 来设置多个路径，但这并不是一个比较好的方法，路径过于分散会导致后续的维护相对复杂，无法充分利用，通过创建 raid 方式可以获得更好的性能和空间利用率，并且便于后续的维护。")]),t._v(" "),a("ul",[a("li",[t._v("软 raid 创建")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token function"}},[t._v("mdadm")]),t._v(" -C /dev/md1 -l "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v(" -n "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("2")]),t._v(" /dev/sdb1 /dev/sdc1\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("mdadm")]),t._v(" -C /dev/md2 -l "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("5")]),t._v(" -n "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("6")]),t._v(" /dev/sd"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("[")]),t._v("b-g"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("]")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v("\n-C $创建软件RAID\n-l $指定RAID级别 "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v("表示raid1 其他同理 \n-n $指定磁盘个数\n-x $指定备用设备个数\n-A $重组之前的设备\n")])])]),a("p",[t._v("​\t有关 mdadm 用法、MD 和各种级别的 RAID 的更多信息，请参阅：http://raid.wiki.kernel.org/")]),t._v(" "),a("p",[t._v("​\t获取最新版本的 mdadm 应始终可以从如下链接获取：http://www.kernel.org/pub/linux/utils/raid/mdadm/")]),t._v(" "),a("p",[t._v("​\t硬 raid 创建时请查看您的 raid 卡型号和说明进行操作")]),t._v(" "),a("h3",{attrs:{id:"永久存储设备"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#永久存储设备"}},[t._v("#")]),t._v(" 永久存储设备")]),t._v(" "),a("p",[t._v("   永久存储设备的访问机制和可能遇到的问题：")]),t._v(" "),a("ol",[a("li",[t._v("在每个任务阶段产生的文件有些是要永久存储的，用于 wdPoSt 或 winningPoSt，在每个 sector 完成阶段需要传输到永久存储目录，这个过程需要带宽资源，并且要保证磁盘 io；")]),t._v(" "),a("li",[t._v("wdPoSt 大量的随机读取非常小的文件，这可能会导致读取过慢而影响时空证明导致算力惩罚；")]),t._v(" "),a("li",[t._v("当存储过于集中时，少量的机器损坏会导致所有的数据丢失；")]),t._v(" "),a("li",[t._v("当磁盘过多时，并且盘符没有固定，启动时可能导致盘符移动；")]),t._v(" "),a("li",[t._v("如果是 raid，尽量选择 raid5 或者 raid6，raid10 这种冗余性更高的方式；")]),t._v(" "),a("li",[t._v("需要监控磁盘空间利用率并报警。")])]),t._v(" "),a("h3",{attrs:{id:"网络传输"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#网络传输"}},[t._v("#")]),t._v(" 网络传输")]),t._v(" "),a("p",[t._v("   网络传输会有两个部分：")]),t._v(" "),a("ul",[a("li",[a("p",[t._v("临时数据的网络传输，某个阶段的任务需要上个阶段的数据时会用 http 协议请求所需文件，需要保证传输时间小于计算时间。")]),t._v(" "),a("p",[t._v("举例：\n传输往往和计算是同步进行的")]),t._v(" "),a("p",[t._v("传输时间 > 计算时间 资源闲置，计算资源等待网络资源，拉长整个扇区封装的声明周期，就是降产")]),t._v(" "),a("p",[t._v("传输时间 < 计算时间 计算资源充分利用")]),t._v(" "),a("ul",[a("li",[a("p",[t._v("观察计算资源是否出现闲置")])]),t._v(" "),a("li",[a("p",[t._v("计算网络传输速度能否满足计算时间")]),t._v(" "),a("p",[t._v("Precommit2 如果计算耗时 25 分钟，读取 440G 左右文件，写入 100G 左右文件"),a("br"),t._v("\n(440G * 1024 / 25 / 60) + (100G * 1024 / 25 / 60) = 单个线程所需的吞吐量")])]),t._v(" "),a("li",[a("p",[t._v("多台机器同步阶段的文件传输")]),t._v(" "),a("p",[t._v("我们有 A，B，C 三个机器分别负责 P1，P2，Commit")]),t._v(" "),a("p",[t._v("当 A 机器开始 P1 时会向 B 机器的 P2 传输 32G 左右的 Unsealed")]),t._v(" "),a("p",[t._v("当 B 机器开始 P2 时，A 机器的 P1 生成的 440G 左右所有文件会传输到 B 的机器上")]),t._v(" "),a("p",[t._v("Commit 又分为 C1 和 C2.当 C 机器运行 C1 时需要 P1 和 P2 的所有文件，计算的结果通过内存直接传递给 C2，所以并不会在落盘新的文件")])])])]),t._v(" "),a("li",[a("p",[t._v("最终数据传输，我们要知道当最终的存储也会成为我们的产量瓶颈（貌似和下面的不符合）")]),t._v(" "),a("ol",[a("li",[a("p",[t._v("假设计算资源的产量是每天产出 6T 的算力，但如果存储的网络传输最大每天只能传输 5T，那么这就会导致产量的下降")])]),t._v(" "),a("li",[a("p",[t._v("如果我们使用了 NFS 这样的网络文件系统，当网络断开链接是，NFS 往往是会直接卡死的，所以可能需要设置 NFS 的超时机制")])])])])]),t._v(" "),a("h3",{attrs:{id:"worker-的指令集加速"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#worker-的指令集加速"}},[t._v("#")]),t._v(" worker 的指令集加速")]),t._v(" "),a("p",[t._v("   P1 阶段时，使用 SHA 指令集和不使用指令集会有巨大的差距，目前大多数矿工都采用 AMD 型号的 CPU 原因就是 SHA 指令集的关系，研究发现，使用 SHA 指令集基本可以跑进 250 分钟以内，但不使用 SHA 指令集能够跑进 420 分钟已经非常艰难了")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v("确保编译时使用RUSTFLAGS=\"-C target-cpu=native -g\" FFI_BUILD_FROM_SOURCE=\"1\" 源码编译filecoin-ffi库，如果cpu支持则启用SHA扩展，这会大幅提高扇区封装速度，源码编译（make deps）时特征如下:\n\n+ trap '{ rm -f $__build_output_log_tmp; }' EXIT\n+ local '__rust_flags=--print native-static-libs -C target-feature=+sse2'\n+ RUSTFLAGS='--print native-static-libs -C target-feature=+sse2'\n+ cargo +nightly-2021-04-24 build --release --no-default-features --features multicore-sdr --features pairing,gpu\n+ tee /tmp/tmp.IYtnd3xka9\n Compiling autocfg v1.0.1\n Compiling libc v0.2.97\n Compiling cfg-if v1.0.0\n Compiling proc-macro2 v1.0.27\n Compiling unicode-xid v0.2.2\n Compiling syn v1.0.73\n Compiling lazy_static v1.4.0\n Compiling cc v1.0.68\n Compiling typenum v1.13.0\n Compiling serde_derive v1.0.126\n Compiling serde v1.0.126\n")])])]),a("h3",{attrs:{id:"核数限制"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#核数限制"}},[t._v("#")]),t._v(" 核数限制")]),t._v(" "),a("p",[t._v("​\t当想要把 CPU 的资源利用的更高时，需要非常合理的规划 CPU 的使用，比如有一个 64 核的 CPU，我们要想 PreCommit2 和 Commit 分别分到 32 核，这样两种任务相互不受影响，也不会导致某一个占用大量的计算资源导致另一个卡住的情况，此时我们就需要利用到核数限制")]),t._v(" "),a("ul",[a("li",[t._v("通过"),a("code",[t._v("taskset")]),t._v("限核")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 当我们想要启动某个进程时，可以通过 taskset -c 0-31 这种方式来进行限核操作")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 例如")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("TRUST_PARAMS")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("nohup")]),t._v(" taskset -c "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("-32 ./venus-worker run "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v("\n--miner-addr"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("/ip4/sealer-ip/tcp/sealer-port"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v("\n--miner-token"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("token"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v(" \n--listen"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0.0")]),t._v(".0.0:345"),a("span",{pre:!0,attrs:{class:"token operator"}},[a("span",{pre:!0,attrs:{class:"token file-descriptor important"}},[t._v("8")]),t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("flags"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">>")]),t._v(" worker.log "),a("span",{pre:!0,attrs:{class:"token operator"}},[a("span",{pre:!0,attrs:{class:"token file-descriptor important"}},[t._v("2")]),t._v(">")]),a("span",{pre:!0,attrs:{class:"token file-descriptor important"}},[t._v("&1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("&")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("\\")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 扩展使用 taskset -c 0-9,19-29,39-49 进行跳跃式限核")]),t._v("\n")])])]),a("p",[t._v("这种方式的弊端就在于不方便在程序运行时对核数进行实时调整")]),t._v(" "),a("ul",[a("li",[t._v("通过 Cgrep 限核")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 好的目录划分会帮助对多个进程的管理")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("sudo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("mkdir")]),t._v(" -p /sys/fs/cgroup/cpuset/Pre1-worker\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 设置能够使用的核数范围")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("sudo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("echo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("-31 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" /sys/fs/cgroup/cpuset/Pre1-worker/cpuset.cpus\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 加入进程的PID")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token function"}},[t._v("sudo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("echo")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("PID"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v(" /sys/fs/cgroup/cpuset/Pre1-worker/cgroup.procs\n")])])]),a("p",[t._v("Cgrep 是在进程启动之后加入到配置文件的，并且支持实时的修改核数限制，当然也可以尝试使用 docker 限核，但 docker 的限核也是通过 Cgrep 来实现，至于 Cgrep 其他的用法我们基本都用不到，就不一一说明了")]),t._v(" "),a("h2",{attrs:{id:"worker-运行方式和资源消耗"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#worker-运行方式和资源消耗"}},[t._v("#")]),t._v(" worker 运行方式和资源消耗")]),t._v(" "),a("h3",{attrs:{id:"p1-阶段"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#p1-阶段"}},[t._v("#")]),t._v(" P1 阶段")]),t._v(" "),a("ul",[a("li",[t._v("P1 阶段的加速因子")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_MAXIMIZE_CACHING")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 控制cache文件缓存到内存中，起到加速作用，会占用56G内存")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_USE_MULTICORE_SDR")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 控制P1阶段是否使用多核运行，他会占用单个CPU组，所以每个CPU缓存组只会运行一个任务")]),t._v("\n")])])]),a("p",[a("code",[t._v("P1")]),t._v("阶段有两种选择，可以选择更快的速度或者更少的 CPU，需要根据实际资源决定。")]),t._v(" "),a("ul",[a("li",[t._v("P1 的内存资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 内存中会存储56G的cache文件")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 加上2层layer文件，32G的矿工每层文件32G，64G每层文件64G")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 以32G矿工为例，如果我们同时运行了10个任务")]),t._v("\n \n56G cahce 文件 + "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("32")]),t._v(" *2 * 并行线程数 "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 696G Mem\n")])])]),a("ul",[a("li",[t._v("P1 的磁盘资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 11层layer文件 ")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 64G的tree-d文件")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 32G的unsealed文件")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("11")]),t._v(" * 32G + "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("64")]),t._v(" + "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("32")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 440G\n")])])]),a("h3",{attrs:{id:"p2-阶段"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#p2-阶段"}},[t._v("#")]),t._v(" P2 阶段")]),t._v(" "),a("ul",[a("li",[t._v("P2 的加速因子有两个")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_USE_GPU_COLUMN_BUILDER")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 使用GPU运算tree-r-last阶段")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("export")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("FIL_PROOFS_USE_GPU_TREE_BUILDER")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 使用GPU运算tree-c阶段")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 任何环境变量都不增加的情况下使用CPU运算")]),t._v("\n")])])]),a("p",[t._v("从实验结果来看使用 GPU 运算要明显比 CPU 快得多，而 CPU 运算时的核数，主频跟时间是成线性比例的，CPU 核数越多速度越快，主频越高越快，反之亦然。")]),t._v(" "),a("ul",[a("li",[t._v("P2 内存资源")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[t._v("--precommit2 "),a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("enable")]),t._v(" precommit2 "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("32G sectors: all cores, 96GiB Memory"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("default: "),a("span",{pre:!0,attrs:{class:"token boolean"}},[t._v("true")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 在命令行中可以看到运行一个需要96GiB的内存，如果并行2个就是2倍")]),t._v("\n")])])]),a("ul",[a("li",[t._v("P2 的磁盘资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 32G")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 8个tree-c文件，每个 4.6G左右")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 8个tree-r-last,每个9.2M")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# t_aux，4K，p_aux，4K")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 32G的sealed文件")]),t._v("\n \n----------------------\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 64G")]),t._v("\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 16个tree-c文件，每个 4.6G左右")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 16个tree-r-last,每个9.2M")]),t._v("\n \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# t_aux，4K，p_aux，4K")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 64G的sealed文件")]),t._v("\n")])])]),a("h3",{attrs:{id:"commit"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#commit"}},[t._v("#")]),t._v(" Commit")]),t._v(" "),a("ul",[a("li",[t._v("Commit 中的 C1 的磁盘资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# C1需要前面2个阶段产生的所有文件")]),t._v("\n\nP1 440G + P2 79G "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),t._v(" 519G \n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 每个C1的任务需要消耗487G左右的空间")]),t._v("\n")])])]),a("p",[t._v("C1 并没有太多的 CPU 消耗，并且时间极短")]),t._v(" "),a("ul",[a("li",[t._v("Commit 中的 C2 的运行方式，CPU 和 GPU")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("BELLMAN_NO_GPU")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("1")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 禁用GPU")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token assign-left variable"}},[t._v("BELLMAN_CUSTOM_GPU")]),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("=")]),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"GeForce RTX 3090:10496"')]),t._v(" \n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 指定GPU的cuda核心数，当GPU型号比较冷门无法识别时可使用")]),t._v("\n")])])]),a("ul",[a("li",[t._v("C2 的内存资源消耗")])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[a("span",{pre:!0,attrs:{class:"token builtin class-name"}},[t._v("enable")]),t._v(" commit "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("32G sectors: all cores or GPUs, 128GiB Memory + 64GiB swap"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("(")]),t._v("default: "),a("span",{pre:!0,attrs:{class:"token boolean"}},[t._v("true")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v(")")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 命令行中指出总共需要 128G + 64 G = 192G的内存")]),t._v("\n")])])]),a("h2",{attrs:{id:"产量优化"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#产量优化"}},[t._v("#")]),t._v(" 产量优化")]),t._v(" "),a("h3",{attrs:{id:"产量的计算公式"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#产量的计算公式"}},[t._v("#")]),t._v(" 产量的计算公式")]),t._v(" "),a("p",[t._v("  每个阶段的效率：")]),t._v(" "),a("div",{staticClass:"language- extra-class"},[a("pre",{pre:!0,attrs:{class:"language-text"}},[a("code",[t._v(" 产出数量 / 时间 = 效率\n \n # 得到效率之后，我们就可以很轻松的算出产量\n \n 效率/h/个数 * 24h * 32G = 日产量\n")])])]),a("p",[t._v("例如我们有 1 台机器")]),t._v(" "),a("p",[t._v("P1:240 分钟")]),t._v(" "),a("p",[t._v("P2:30 分钟")]),t._v(" "),a("p",[t._v("Commit：35 分钟")]),t._v(" "),a("p",[t._v("此时我们可以简单一个计算公式的表格")]),t._v(" "),a("table",[a("thead",[a("tr",[a("th",[t._v("运行阶段")]),t._v(" "),a("th",[t._v("时间/m")]),t._v(" "),a("th",[t._v("并行线程数")]),t._v(" "),a("th",[t._v("效率/时间h/个数")]),t._v(" "),a("th",[t._v("计算公式")])])]),t._v(" "),a("tbody",[a("tr",[a("td",[t._v("P1")]),t._v(" "),a("td",[t._v("240")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("0.25")]),t._v(" "),a("td",[t._v("= 1 / (240 /60)")])]),t._v(" "),a("tr",[a("td",[t._v("P2")]),t._v(" "),a("td",[t._v("30")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("2")]),t._v(" "),a("td",[t._v("= 1 / (30 /60)")])]),t._v(" "),a("tr",[a("td",[t._v("Commit")]),t._v(" "),a("td",[t._v("35")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("1.7142857143")]),t._v(" "),a("td",[t._v("= 1 / (35 /60)")])])])]),t._v(" "),a("h4",{attrs:{id:"如何找到每个阶段的最佳运行数量和配置"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#如何找到每个阶段的最佳运行数量和配置"}},[t._v("#")]),t._v(" 如何找到每个阶段的最佳运行数量和配置")]),t._v(" "),a("p",[t._v("   从上面的表格中我们明显看出 P1 的效率明显不足，而此时 P2 和 Commit 机器必定会闲置，如何处理呢？产出的时间无法调整，那么我们就可以调整并行的线程数，当然我们可以新增一些计算内存的公式来指导我们对内存的消耗")]),t._v(" "),a("table",[a("thead",[a("tr",[a("th",[t._v("运行阶段")]),t._v(" "),a("th",[t._v("时间/m")]),t._v(" "),a("th",[t._v("并行线程数")]),t._v(" "),a("th",[t._v("效率/时间h/个数")]),t._v(" "),a("th",[t._v("计算公式")]),t._v(" "),a("th",[t._v("日产量/G")]),t._v(" "),a("th",[t._v("公式")]),t._v(" "),a("th",[t._v("mem/G")])])]),t._v(" "),a("tbody",[a("tr",[a("td",[t._v("P1")]),t._v(" "),a("td",[t._v("240")]),t._v(" "),a("td",[t._v("7")]),t._v(" "),a("td",[t._v("1.75")]),t._v(" "),a("td",[t._v("= 7 / (240 /60)")]),t._v(" "),a("td",[t._v("1344")]),t._v(" "),a("td",[t._v("=7*64+56")]),t._v(" "),a("td",[t._v("504")])]),t._v(" "),a("tr",[a("td",[t._v("P2")]),t._v(" "),a("td",[t._v("30")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("2")]),t._v(" "),a("td",[t._v("= 1 / (30 /60)")]),t._v(" "),a("td",[t._v("1536")]),t._v(" "),a("td",[t._v("=1*96")]),t._v(" "),a("td",[t._v("96")])]),t._v(" "),a("tr",[a("td",[t._v("Commit")]),t._v(" "),a("td",[t._v("35")]),t._v(" "),a("td",[t._v("1")]),t._v(" "),a("td",[t._v("1.7142857143")]),t._v(" "),a("td",[t._v("= 1 / (35 /60)")]),t._v(" "),a("td",[t._v("1316.571429")]),t._v(" "),a("td",[t._v("=1*128+64")]),t._v(" "),a("td",[t._v("192")])])])]),t._v(" "),a("p",[t._v("现在三个阶段的效率已经非常接近了，但是此时我们仍然存在一些问题：")]),t._v(" "),a("ol",[a("li",[t._v("Commit 效率低于 P1，这会导致大量的任务阻塞到 Commit 阶段")]),t._v(" "),a("li",[t._v("当某个阶段的效率过高时就会出现闲置")]),t._v(" "),a("li",[t._v("我们需要微调资源的分布来尽可能的保证每个阶段的效率无限相等")])]),t._v(" "),a("h4",{attrs:{id:"集群方案运行的的可能性"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#集群方案运行的的可能性"}},[t._v("#")]),t._v(" 集群方案运行的的可能性")]),t._v(" "),a("p",[t._v("​\t\t当我们有多台机器时，我们就要决定某些机器运行哪些阶段，在这之前我们再来看下不同阶段的特性：")]),t._v(" "),a("ol",[a("li",[t._v("P1 : 极度消耗内存，可以单核，多核，并行运行，临时存储需要伴随着并行数量的增多而增多")]),t._v(" "),a("li",[t._v("P2 : 轻度消耗内存，CPU，GPU 都可以运行，如果拆分，需要传输大量的文件")]),t._v(" "),a("li",[t._v("Commit: 中度消耗内存，CPU，GPU 都可以运行，如果拆分，需要传输所有临时文件")])]),t._v(" "),a("p",[t._v("如果我们此时只考虑这些因素，那么我们的组合方式有多少种呢？而这些不同的组合方式一定会带来不通的产量，虽然每个矿工的机器都有所不同，但我们的目标是一样的：")]),t._v(" "),a("ol",[a("li",[t._v("更高的产量组合运行方式")]),t._v(" "),a("li",[t._v("各个阶段更加均衡的分布")])]),t._v(" "),a("p",[t._v("我们可能无法做到完美，但无限接近也是最好的结果")]),t._v(" "),a("h4",{attrs:{id:"如何寻找最佳的下发任务数-始终保持机器满负荷运行"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#如何寻找最佳的下发任务数-始终保持机器满负荷运行"}},[t._v("#")]),t._v(" 如何寻找最佳的下发任务数，始终保持机器满负荷运行")]),t._v(" "),a("p",[t._v("  当我们找到最佳的组合方式之后我们需要考虑的就是如何才能保证这些机器 24 小时都是不间断运行的呢？我们不希望任何一个阶段的出现闲置")]),t._v(" "),a("p",[t._v("当我们发现 P1 需要并行 7 个时，那么我们如果保证 P1 的任务量是充足的，那么后续的两个阶段在不考虑其他问题的情况下，也一定是充足的，所以我们需要保证始终维持 P1 时刻都有 7 个任务")]),t._v(" "),a("div",{staticClass:"language-toml extra-class"},[a("pre",{pre:!0,attrs:{class:"language-toml"}},[a("code",[a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 在 venus-sealer 的配置文件中我们可以设置最大的任务数，这可以帮我我们避免任务数下发过多")]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("DataDir")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"~/.venussealer"')]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("[")]),a("span",{pre:!0,attrs:{class:"token table class-name"}},[t._v("API")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("]")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("ListenAddress")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"/ip4/0.0.0.0/tcp/2345/http"')]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("RemoteListenAddress")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"192.168.200.6:2345"')]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("Timeout")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token string"}},[t._v('"30s"')]),t._v("\n\n"),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("[")]),a("span",{pre:!0,attrs:{class:"token table class-name"}},[t._v("Sealing")]),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("]")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("MaxWaitDealsSectors")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("MaxSealingSectors")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("7")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token comment"}},[t._v("# 修改为 7")]),t._v("\n "),a("span",{pre:!0,attrs:{class:"token key property"}},[t._v("MaxSealingSectorsForDeals")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token punctuation"}},[t._v("=")]),t._v(" "),a("span",{pre:!0,attrs:{class:"token number"}},[t._v("0")]),t._v("\n")])])]),a("p",[t._v("此时我们可以通过一个简单的定时脚本就可以做到，始终维持最佳的任务量了")]),t._v(" "),a("h2",{attrs:{id:"损失和止损"}},[a("a",{staticClass:"header-anchor",attrs:{href:"#损失和止损"}},[t._v("#")]),t._v(" 损失和止损")]),t._v(" "),a("p",[t._v("  如果一个任务执行错误之后又被反复的重试，这就像我们有 7 个通道进行算力的封装，但是此时有一通道阻塞或者损坏，这就会降低我们 1 / 7 的产量，所以及时的处理错误也是非常重要的")]),t._v(" "),a("ul",[a("li",[a("p",[t._v("何种情况下应该立刻抛弃任务")]),t._v(" "),a("ol",[a("li",[t._v("ticket 过期")]),t._v(" "),a("li",[t._v("Commit 过期")]),t._v(" "),a("li",[t._v("依赖文件损坏重试多次都未成功时;")])])]),t._v(" "),a("li",[a("p",[t._v("移除无法完成的 sector")])])]),t._v(" "),a("div",{staticClass:"language-bash extra-class"},[a("pre",{pre:!0,attrs:{class:"language-bash"}},[a("code",[t._v("venus-sealer sectors remove --really-do-it "),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v("<")]),t._v("sectorNum"),a("span",{pre:!0,attrs:{class:"token operator"}},[t._v(">")]),t._v("\n")])])]),a("p",[t._v("如遇到无法彻底删除请查询："),a("a",{attrs:{href:"https://github.com/filguard/lotus-ops/blob/master/documents/questions.md#1-%E9%A1%BD%E5%9B%BA%E6%89%87%E5%8C%BA%E5%A6%82%E4%BD%95%E5%88%A0%E9%99%A4",target:"_blank",rel:"noopener noreferrer"}},[t._v("顽固扇区如何删除"),a("OutboundLink")],1)])])}),[],!1,null,null,null);s.default=r.exports}}]); \ No newline at end of file diff --git a/assets/js/58.e1f68517.js b/assets/js/58.bdfb0b74.js similarity index 98% rename from assets/js/58.e1f68517.js rename to assets/js/58.bdfb0b74.js index 6423cf9eb..ce1d03bab 100644 --- a/assets/js/58.e1f68517.js +++ b/assets/js/58.bdfb0b74.js @@ -1 +1 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[58],{449:function(v,a,t){"use strict";t.r(a);var e=t(17),_=Object(e.a)({},(function(){var v=this,a=v.$createElement,t=v._self._c||a;return t("ContentSlotsDistributor",{attrs:{"slot-key":v.$parent.slotKey}},[t("h1",{attrs:{id:"venus-各组件升级文档-持续更新中"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#venus-各组件升级文档-持续更新中"}},[v._v("#")]),v._v(" Venus 各组件升级文档 (持续更新中)")]),v._v(" "),t("h2",{attrs:{id:"注意事项"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#注意事项"}},[v._v("#")]),v._v(" 注意事项")]),v._v(" "),t("ol",[t("li",[v._v("所有组件全部更换")]),v._v(" "),t("li",[v._v("更新完通过 curl 命令调用 "),t("code",[v._v("Version")]),v._v(" 接口检查版本号，各组件接口调用方式：https://github.com/filecoin-project/venus/issues/5132")]),v._v(" "),t("li",[v._v("pre/pro消息上链的情况")]),v._v(" "),t("li",[v._v("WD消息上链的情况")]),v._v(" "),t("li",[v._v("出块情况是否正常")]),v._v(" "),t("li",[v._v("gas fee 相关设置是否生效")])]),v._v(" "),t("h2",{attrs:{id:"需要升级的组件"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#需要升级的组件"}},[v._v("#")]),v._v(" 需要升级的组件")]),v._v(" "),t("table",[t("thead",[t("tr",[t("th",[v._v("组件名")]),v._v(" "),t("th",[v._v("tag")]),v._v(" "),t("th",[v._v("commit")])])]),v._v(" "),t("tbody",[t("tr",[t("td",[v._v("sophon-auth")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("a1e964b")])]),v._v(" "),t("tr",[t("td",[v._v("venus")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("aabda75")])]),v._v(" "),t("tr",[t("td",[v._v("sophon-co")]),v._v(" "),t("td",[v._v("v0.8.0")]),v._v(" "),t("td",[v._v("0e48712")])]),v._v(" "),t("tr",[t("td",[v._v("sophon-messager")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("1e4f0d5")])]),v._v(" "),t("tr",[t("td",[v._v("soohon-gateway")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("541891a")])]),v._v(" "),t("tr",[t("td",[v._v("venus-wallet")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("6b3de34")])]),v._v(" "),t("tr",[t("td",[v._v("sophon-miner")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("8dd6c68")])]),v._v(" "),t("tr",[t("td",[v._v("droplet")]),v._v(" "),t("td",[v._v("v2.11.0")]),v._v(" "),t("td",[v._v("44481dd")])]),v._v(" "),t("tr",[t("td",[v._v("damocles-manager")]),v._v(" "),t("td",[v._v("v0.10.0-rc1")]),v._v(" "),t("td",[v._v("2f6c5f9")])]),v._v(" "),t("tr",[t("td",[v._v("damocles-worker")]),v._v(" "),t("td",[v._v("v0.10.0-rc1")]),v._v(" "),t("td",[v._v("2f6c5f9")])])])]),v._v(" "),t("h3",{attrs:{id:"升级顺序"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#升级顺序"}},[v._v("#")]),v._v(" 升级顺序")]),v._v(" "),t("ol",[t("li",[v._v("sophon-auth")]),v._v(" "),t("li",[v._v("venus")]),v._v(" "),t("li",[v._v("soohon-co")]),v._v(" "),t("li",[v._v("soohon-gateway")]),v._v(" "),t("li",[v._v("sophon-messager")]),v._v(" "),t("li",[v._v("sophon-miner")]),v._v(" "),t("li",[v._v("droplet")]),v._v(" "),t("li",[v._v("venus-wallet")]),v._v(" "),t("li",[v._v("damocles-manager")]),v._v(" "),t("li",[v._v("damocles-worker")])]),v._v(" "),t("h3",{attrs:{id:"sophon-auth"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-auth"}},[v._v("#")]),v._v(" sophon-auth")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("ul",[t("li",[v._v("其他组件对获取 auth 的服务")])]),v._v(" "),t("p",[v._v("依赖升级组件: 无")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("启动后能否正常鉴权")])]),v._v(" "),t("h3",{attrs:{id:"venus"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#venus"}},[v._v("#")]),v._v(" venus")]),v._v(" "),t("p",[v._v("影响功能：无")]),v._v(" "),t("p",[v._v("依赖升级组件: sophon-auth")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("p",[v._v("编译：先 "),t("code",[v._v("make dist-clean")]),v._v(" 再 "),t("code",[v._v("make")]),v._v("，这样可以防止未能正常升级 "),t("code",[v._v("filecoin-ffi")]),v._v(" 而带来的问题")]),v._v(" "),t("ol",[t("li",[t("p",[v._v("升级后检查vk文件是否完整")])]),v._v(" "),t("li",[t("p",[v._v("升级后执行命令 "),t("code",[v._v("./venus state network-info")]),v._v("，然后检查通过日志检查 UpgradeDragonHeight 是否正常:")]),v._v(" "),t("div",{staticClass:"language- extra-class"},[t("pre",{pre:!0,attrs:{class:"language-text"}},[t("code",[v._v("# cali\nUpgradeDragonHeight: 1427974\n# mainnet\nUpgradeDragonHeight: 3817920\n")])])])]),v._v(" "),t("li",[t("p",[v._v("升级后需检查是否正常同步区块")])]),v._v(" "),t("li",[t("p",[v._v("检查主网 v13 actors code，确保与下面输出一样")]),v._v(" "),t("div",{staticClass:"language- extra-class"},[t("pre",{pre:!0,attrs:{class:"language-text"}},[t("code",[v._v("./venus state actor-cids --network-version 22\n\n# 顺序可能会不一样\nNetwork Version: 22\nActor Version: 13\nManifest CID: bafy2bzacecdhvfmtirtojwhw2tyciu4jkbpsbk5g53oe24br27oy62sn4dc4e\nActor CID\naccount bafk2bzacedxnbtlsqdk76fsfmnhyvsblwyfducerwwtp3mqtx2wbrvs5idl52\ncron bafk2bzacebbopddyn5csb3fsuhh2an4ttd23x6qnwixgohlirj5ahtcudphyc\ndatacap bafk2bzaceah42tfnhd7xnztawgf46gbvc3m2gudoxshlba2ucmmo2vy67t7ci\neam bafk2bzaceb23bhvvcjsth7cn7vp3gbaphrutsaz7v6hkls3ogotzs4bnhm4mk\nethaccount bafk2bzaceautge6zhuy6jbj3uldwoxwhpywuon6z3xfvmdbzpbdribc6zzmei\nevm bafk2bzacedq6v2lyuhgywhlllwmudfj2zufzcauxcsvvd34m2ek5xr55mvh2q\ninit bafk2bzacedr4xacm3fts4vilyeiacjr2hpmwzclyzulbdo24lrfxbtau2wbai\nmultisig bafk2bzacecr5zqarfqak42xqcfeulsxlavcltawsx2fvc7zsjtby6ti4b3wqc\npaymentchannel bafk2bzacebntdhfmyc24e7tm52ggx5tnw4i3hrr3jmllsepv3mibez4hywsa2\nplaceholder bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro\nreward bafk2bzacedq4q2kwkruu4xm7rkyygumlbw2yt4nimna2ivea4qarvtkohnuwu\nstoragemarket bafk2bzacebjtoltdviyznpj34hh5qp6u257jnnbjole5rhqfixm7ug3epvrfu\nstorageminer bafk2bzacebf4rrqyk7gcfggggul6nfpzay7f2ordnkwm7z2wcf4mq6r7i77t2\nstoragepower bafk2bzacecjy4dkulvxppg3ocbmeixe2wgg6yxoyjxrm4ko2fm3uhpvfvam6e\nsystem bafk2bzacecyf523quuq2kdjfdvyty446z2ounmamtgtgeqnr3ynlu5cqrlt6e\nverifiedregistry bafk2bzacedkxehp7y7iyukbcje3wbpqcvufisos6exatkanyrbotoecdkrbta\n")])])])]),v._v(" "),t("li",[t("p",[v._v("若不排查问题，rust日志级别"),t("strong",[v._v("不建议")]),v._v("设置为 "),t("code",[v._v("trace")]),v._v("，因为会打印较多日志")])]),v._v(" "),t("li",[t("p",[v._v("升级后可以通过命令来 "),t("code",[v._v("./venus state get-actor t01000")]),v._v(" 来确认是否升级成功")])]),v._v(" "),t("li",[t("p",[v._v("actor 迁移")]),v._v(" "),t("p",[t("strong",[v._v("经测试本次预迁移时间在 30 分钟左右，正式迁移时间在 100 秒左右")])]),v._v(" "),t("div",{staticClass:"language- extra-class"},[t("pre",{pre:!0,attrs:{class:"language-text"}},[t("code",[v._v("预迁移高度是升级高度前 120 个高度：\npre-migration 开始：STARTING pre-migration 结束：COMPLETED pre-migration\nmigration 开始：STARTING migration 结束：COMPLETED migration\n")])])])]),v._v(" "),t("li",[t("p",[v._v("如果 "),t("code",[v._v("~/.venus")]),v._v(" 存在且需要导入快照，需要先删除 "),t("code",[v._v("~/.venus/version")]),v._v(" 文件再导入快照")]),v._v(" "),t("ul",[t("li",[v._v("主网: "),t("code",[v._v("./venus daemon --import-snapshot snapshot.car")])]),v._v(" "),t("li",[v._v("calibnet: "),t("code",[v._v("./venus daemon --import-snapshot snapshot.car --network calibrationnet")])])])])]),v._v(" "),t("h3",{attrs:{id:"sophon-gateway"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-gateway"}},[v._v("#")]),v._v(" sophon-gateway")]),v._v(" "),t("p",[v._v("影响功能：无")]),v._v(" "),t("p",[v._v("依赖升级组件: sophon-auth")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("编译时,需要先 "),t("code",[v._v("make dist-clean")]),v._v(" 再 "),t("code",[v._v("make")])])]),v._v(" "),t("h3",{attrs:{id:"sophon-messager"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-messager"}},[v._v("#")]),v._v(" sophon-messager")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("p",[v._v("依赖升级组件: venus, sophon-auth, soohon-gateway")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("升级之后需要观察能否正常接收消息, 消息能否正常上链")])]),v._v(" "),t("h3",{attrs:{id:"sophon-miner"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-miner"}},[v._v("#")]),v._v(" sophon-miner")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("p",[v._v("依赖升级组件：auth, venus, gateway")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("h3",{attrs:{id:"droplet"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#droplet"}},[v._v("#")]),v._v(" droplet")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("ul",[t("li",[v._v("支持 direct data onboarding，使用文档：https://github.com/ipfs-force-community/droplet/blob/master/docs/zh/direct-on-boarding.md")])]),v._v(" "),t("p",[v._v("依赖升级组件: auth, venus, gateway, messager")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("升级后能否正常发单和检索")])]),v._v(" "),t("h3",{attrs:{id:"venus-wallet"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#venus-wallet"}},[v._v("#")]),v._v(" venus-wallet")]),v._v(" "),t("p",[v._v("影响功能： 无")]),v._v(" "),t("p",[v._v("依赖升级组件: gateway")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("升级后观察是否正常签名，消息能否正常上链")])]),v._v(" "),t("h3",{attrs:{id:"damocles-manager"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#damocles-manager"}},[v._v("#")]),v._v(" damocles-manager")]),v._v(" "),t("p",[v._v("依赖升级组件: 链服务组件")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("编译时,需要先 "),t("code",[v._v("make dist-clean")]),v._v(" 再 "),t("code",[v._v("make")])])]),v._v(" "),t("h3",{attrs:{id:"damocles-worker"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#damocles-worker"}},[v._v("#")]),v._v(" damocles-worker")]),v._v(" "),t("p",[v._v("依赖升级组件: damocles-manager")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("hr"),v._v(" "),t("p",[v._v("更新结果验证步骤:")]),v._v(" "),t("ol",[t("li",[v._v("程序启动正常")]),v._v(" "),t("li",[v._v("pre/pro消息正常上链")]),v._v(" "),t("li",[v._v("出块正常")]),v._v(" "),t("li",[v._v("WD上链正常")]),v._v(" "),t("li",[v._v("算力增长正常")]),v._v(" "),t("li",[v._v("真实订单检索正常")]),v._v(" "),t("li",[v._v("数据库各种gas，生命周期，聚合设置正常")])]),v._v(" "),t("h3",{attrs:{id:"数据库变更"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#数据库变更"}},[v._v("#")]),v._v(" 数据库变更")]),v._v(" "),t("ol",[t("li",[v._v("droplet 增加 direct_deals 表，用于存储 direct 订单。")])])])}),[],!1,null,null,null);a.default=_.exports}}]); \ No newline at end of file +(window.webpackJsonp=window.webpackJsonp||[]).push([[58],{449:function(v,a,t){"use strict";t.r(a);var e=t(17),_=Object(e.a)({},(function(){var v=this,a=v.$createElement,t=v._self._c||a;return t("ContentSlotsDistributor",{attrs:{"slot-key":v.$parent.slotKey}},[t("h1",{attrs:{id:"venus-各组件升级文档-持续更新中"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#venus-各组件升级文档-持续更新中"}},[v._v("#")]),v._v(" Venus 各组件升级文档 (持续更新中)")]),v._v(" "),t("h2",{attrs:{id:"注意事项"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#注意事项"}},[v._v("#")]),v._v(" 注意事项")]),v._v(" "),t("ol",[t("li",[v._v("所有组件全部更换")]),v._v(" "),t("li",[v._v("更新完通过 curl 命令调用 "),t("code",[v._v("Version")]),v._v(" 接口检查版本号，各组件接口调用方式：https://github.com/filecoin-project/venus/issues/5132")]),v._v(" "),t("li",[v._v("pre/pro消息上链的情况")]),v._v(" "),t("li",[v._v("WD消息上链的情况")]),v._v(" "),t("li",[v._v("出块情况是否正常")]),v._v(" "),t("li",[v._v("gas fee 相关设置是否生效")])]),v._v(" "),t("h2",{attrs:{id:"需要升级的组件"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#需要升级的组件"}},[v._v("#")]),v._v(" 需要升级的组件")]),v._v(" "),t("table",[t("thead",[t("tr",[t("th",[v._v("组件名")]),v._v(" "),t("th",[v._v("tag")]),v._v(" "),t("th",[v._v("commit")])])]),v._v(" "),t("tbody",[t("tr",[t("td",[v._v("sophon-auth")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("a1e964b")])]),v._v(" "),t("tr",[t("td",[v._v("venus")]),v._v(" "),t("td",[v._v("v1.15.1")]),v._v(" "),t("td",[v._v("81c99f3")])]),v._v(" "),t("tr",[t("td",[v._v("sophon-co")]),v._v(" "),t("td",[v._v("v0.8.0")]),v._v(" "),t("td",[v._v("0e48712")])]),v._v(" "),t("tr",[t("td",[v._v("sophon-messager")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("1e4f0d5")])]),v._v(" "),t("tr",[t("td",[v._v("soohon-gateway")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("541891a")])]),v._v(" "),t("tr",[t("td",[v._v("venus-wallet")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("6b3de34")])]),v._v(" "),t("tr",[t("td",[v._v("sophon-miner")]),v._v(" "),t("td",[v._v("v1.15.0")]),v._v(" "),t("td",[v._v("8dd6c68")])]),v._v(" "),t("tr",[t("td",[v._v("droplet")]),v._v(" "),t("td",[v._v("v2.11.0")]),v._v(" "),t("td",[v._v("44481dd")])]),v._v(" "),t("tr",[t("td",[v._v("damocles-manager")]),v._v(" "),t("td",[v._v("v0.10.0-rc1")]),v._v(" "),t("td",[v._v("2f6c5f9")])]),v._v(" "),t("tr",[t("td",[v._v("damocles-worker")]),v._v(" "),t("td",[v._v("v0.10.0-rc1")]),v._v(" "),t("td",[v._v("2f6c5f9")])])])]),v._v(" "),t("h3",{attrs:{id:"升级顺序"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#升级顺序"}},[v._v("#")]),v._v(" 升级顺序")]),v._v(" "),t("ol",[t("li",[v._v("sophon-auth")]),v._v(" "),t("li",[v._v("venus")]),v._v(" "),t("li",[v._v("soohon-co")]),v._v(" "),t("li",[v._v("soohon-gateway")]),v._v(" "),t("li",[v._v("sophon-messager")]),v._v(" "),t("li",[v._v("sophon-miner")]),v._v(" "),t("li",[v._v("droplet")]),v._v(" "),t("li",[v._v("venus-wallet")]),v._v(" "),t("li",[v._v("damocles-manager")]),v._v(" "),t("li",[v._v("damocles-worker")])]),v._v(" "),t("h3",{attrs:{id:"sophon-auth"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-auth"}},[v._v("#")]),v._v(" sophon-auth")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("ul",[t("li",[v._v("其他组件对获取 auth 的服务")])]),v._v(" "),t("p",[v._v("依赖升级组件: 无")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("启动后能否正常鉴权")])]),v._v(" "),t("h3",{attrs:{id:"venus"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#venus"}},[v._v("#")]),v._v(" venus")]),v._v(" "),t("p",[v._v("影响功能：无")]),v._v(" "),t("p",[v._v("依赖升级组件: sophon-auth")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("p",[v._v("编译：先 "),t("code",[v._v("make dist-clean")]),v._v(" 再 "),t("code",[v._v("make")]),v._v("，这样可以防止未能正常升级 "),t("code",[v._v("filecoin-ffi")]),v._v(" 而带来的问题")]),v._v(" "),t("ol",[t("li",[t("p",[v._v("升级后检查vk文件是否完整")])]),v._v(" "),t("li",[t("p",[v._v("升级后执行命令 "),t("code",[v._v("./venus state network-info")]),v._v("，然后检查通过日志检查 UpgradeDragonHeight 是否正常:")]),v._v(" "),t("div",{staticClass:"language- extra-class"},[t("pre",{pre:!0,attrs:{class:"language-text"}},[t("code",[v._v("# cali\nUpgradeDragonHeight: 1427974\n# mainnet\nUpgradeDragonHeight: 3855360\n")])])])]),v._v(" "),t("li",[t("p",[v._v("升级后需检查是否正常同步区块")])]),v._v(" "),t("li",[t("p",[v._v("检查主网 v13 actors code，确保与下面输出一样")]),v._v(" "),t("div",{staticClass:"language- extra-class"},[t("pre",{pre:!0,attrs:{class:"language-text"}},[t("code",[v._v("./venus state actor-cids --network-version 22\n\n# 顺序可能会不一样\nNetwork Version: 22\nActor Version: 13\nManifest CID: bafy2bzacecdhvfmtirtojwhw2tyciu4jkbpsbk5g53oe24br27oy62sn4dc4e\nActor CID\naccount bafk2bzacedxnbtlsqdk76fsfmnhyvsblwyfducerwwtp3mqtx2wbrvs5idl52\ncron bafk2bzacebbopddyn5csb3fsuhh2an4ttd23x6qnwixgohlirj5ahtcudphyc\ndatacap bafk2bzaceah42tfnhd7xnztawgf46gbvc3m2gudoxshlba2ucmmo2vy67t7ci\neam bafk2bzaceb23bhvvcjsth7cn7vp3gbaphrutsaz7v6hkls3ogotzs4bnhm4mk\nethaccount bafk2bzaceautge6zhuy6jbj3uldwoxwhpywuon6z3xfvmdbzpbdribc6zzmei\nevm bafk2bzacedq6v2lyuhgywhlllwmudfj2zufzcauxcsvvd34m2ek5xr55mvh2q\ninit bafk2bzacedr4xacm3fts4vilyeiacjr2hpmwzclyzulbdo24lrfxbtau2wbai\nmultisig bafk2bzacecr5zqarfqak42xqcfeulsxlavcltawsx2fvc7zsjtby6ti4b3wqc\npaymentchannel bafk2bzacebntdhfmyc24e7tm52ggx5tnw4i3hrr3jmllsepv3mibez4hywsa2\nplaceholder bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro\nreward bafk2bzacedq4q2kwkruu4xm7rkyygumlbw2yt4nimna2ivea4qarvtkohnuwu\nstoragemarket bafk2bzacebjtoltdviyznpj34hh5qp6u257jnnbjole5rhqfixm7ug3epvrfu\nstorageminer bafk2bzacebf4rrqyk7gcfggggul6nfpzay7f2ordnkwm7z2wcf4mq6r7i77t2\nstoragepower bafk2bzacecjy4dkulvxppg3ocbmeixe2wgg6yxoyjxrm4ko2fm3uhpvfvam6e\nsystem bafk2bzacecyf523quuq2kdjfdvyty446z2ounmamtgtgeqnr3ynlu5cqrlt6e\nverifiedregistry bafk2bzacedkxehp7y7iyukbcje3wbpqcvufisos6exatkanyrbotoecdkrbta\n")])])])]),v._v(" "),t("li",[t("p",[v._v("若不排查问题，rust日志级别"),t("strong",[v._v("不建议")]),v._v("设置为 "),t("code",[v._v("trace")]),v._v("，因为会打印较多日志")])]),v._v(" "),t("li",[t("p",[v._v("升级后可以通过命令来 "),t("code",[v._v("./venus state get-actor t01000")]),v._v(" 来确认是否升级成功")])]),v._v(" "),t("li",[t("p",[v._v("actor 迁移")]),v._v(" "),t("p",[t("strong",[v._v("经测试本次预迁移时间在 30 分钟左右，正式迁移时间在 100 秒左右")])]),v._v(" "),t("div",{staticClass:"language- extra-class"},[t("pre",{pre:!0,attrs:{class:"language-text"}},[t("code",[v._v("预迁移高度是升级高度前 120 个高度：\npre-migration 开始：STARTING pre-migration 结束：COMPLETED pre-migration\nmigration 开始：STARTING migration 结束：COMPLETED migration\n")])])])]),v._v(" "),t("li",[t("p",[v._v("如果 "),t("code",[v._v("~/.venus")]),v._v(" 存在且需要导入快照，需要先删除 "),t("code",[v._v("~/.venus/version")]),v._v(" 文件再导入快照")]),v._v(" "),t("ul",[t("li",[v._v("主网: "),t("code",[v._v("./venus daemon --import-snapshot snapshot.car")])]),v._v(" "),t("li",[v._v("calibnet: "),t("code",[v._v("./venus daemon --import-snapshot snapshot.car --network calibrationnet")])])])])]),v._v(" "),t("h3",{attrs:{id:"sophon-gateway"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-gateway"}},[v._v("#")]),v._v(" sophon-gateway")]),v._v(" "),t("p",[v._v("影响功能：无")]),v._v(" "),t("p",[v._v("依赖升级组件: sophon-auth")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("编译时,需要先 "),t("code",[v._v("make dist-clean")]),v._v(" 再 "),t("code",[v._v("make")])])]),v._v(" "),t("h3",{attrs:{id:"sophon-messager"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-messager"}},[v._v("#")]),v._v(" sophon-messager")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("p",[v._v("依赖升级组件: venus, sophon-auth, soohon-gateway")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("升级之后需要观察能否正常接收消息, 消息能否正常上链")])]),v._v(" "),t("h3",{attrs:{id:"sophon-miner"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#sophon-miner"}},[v._v("#")]),v._v(" sophon-miner")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("p",[v._v("依赖升级组件：auth, venus, gateway")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("h3",{attrs:{id:"droplet"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#droplet"}},[v._v("#")]),v._v(" droplet")]),v._v(" "),t("p",[v._v("影响功能：")]),v._v(" "),t("ul",[t("li",[v._v("支持 direct data onboarding，使用文档：https://github.com/ipfs-force-community/droplet/blob/master/docs/zh/direct-on-boarding.md")])]),v._v(" "),t("p",[v._v("依赖升级组件: auth, venus, gateway, messager")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("升级后能否正常发单和检索")])]),v._v(" "),t("h3",{attrs:{id:"venus-wallet"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#venus-wallet"}},[v._v("#")]),v._v(" venus-wallet")]),v._v(" "),t("p",[v._v("影响功能： 无")]),v._v(" "),t("p",[v._v("依赖升级组件: gateway")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("升级后观察是否正常签名，消息能否正常上链")])]),v._v(" "),t("h3",{attrs:{id:"damocles-manager"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#damocles-manager"}},[v._v("#")]),v._v(" damocles-manager")]),v._v(" "),t("p",[v._v("依赖升级组件: 链服务组件")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("ul",[t("li",[v._v("编译时,需要先 "),t("code",[v._v("make dist-clean")]),v._v(" 再 "),t("code",[v._v("make")])])]),v._v(" "),t("h3",{attrs:{id:"damocles-worker"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#damocles-worker"}},[v._v("#")]),v._v(" damocles-worker")]),v._v(" "),t("p",[v._v("依赖升级组件: damocles-manager")]),v._v(" "),t("p",[v._v("注意事项：")]),v._v(" "),t("hr"),v._v(" "),t("p",[v._v("更新结果验证步骤:")]),v._v(" "),t("ol",[t("li",[v._v("程序启动正常")]),v._v(" "),t("li",[v._v("pre/pro消息正常上链")]),v._v(" "),t("li",[v._v("出块正常")]),v._v(" "),t("li",[v._v("WD上链正常")]),v._v(" "),t("li",[v._v("算力增长正常")]),v._v(" "),t("li",[v._v("真实订单检索正常")]),v._v(" "),t("li",[v._v("数据库各种gas，生命周期，聚合设置正常")])]),v._v(" "),t("h3",{attrs:{id:"数据库变更"}},[t("a",{staticClass:"header-anchor",attrs:{href:"#数据库变更"}},[v._v("#")]),v._v(" 数据库变更")]),v._v(" "),t("ol",[t("li",[v._v("droplet 增加 direct_deals 表，用于存储 direct 订单。")])])])}),[],!1,null,null,null);a.default=_.exports}}]); \ No newline at end of file diff --git a/assets/js/app.315ddca5.js b/assets/js/app.315ddca5.js deleted file mode 100644 index 0bae7f348..000000000 --- a/assets/js/app.315ddca5.js +++ /dev/null @@ -1,8 +0,0 @@ -(window.webpackJsonp=window.webpackJsonp||[]).push([[0],[]]);!function(e){function n(n){for(var r,i,s=n[0],c=n[1],l=n[2],p=0,d=[];p0?o(r(e),9007199254740991):0}},function(e,n){var t=Array.isArray;e.exports=t},function(e,n,t){var r=t(152),o="object"==typeof self&&self&&self.Object===Object&&self,a=r||o||Function("return this")();e.exports=a},function(e,n,t){"use strict";function r(e,n,t,r,o,a,i,s){var c,l="function"==typeof e?e.options:e;if(n&&(l.render=n,l.staticRenderFns=t,l._compiled=!0),r&&(l.functional=!0),a&&(l._scopeId="data-v-"+a),i?(c=function(e){(e=e||this.$vnode&&this.$vnode.ssrContext||this.parent&&this.parent.$vnode&&this.parent.$vnode.ssrContext)||"undefined"==typeof __VUE_SSR_CONTEXT__||(e=__VUE_SSR_CONTEXT__),o&&o.call(this,e),e&&e._registeredComponents&&e._registeredComponents.add(i)},l._ssrRegister=c):o&&(c=s?function(){o.call(this,(l.functional?this.parent:this).$root.$options.shadowRoot)}:o),c)if(l.functional){l._injectStyles=c;var u=l.render;l.render=function(e,n){return c.call(n),u(e,n)}}else{var p=l.beforeCreate;l.beforeCreate=p?[].concat(p,c):[c]}return{exports:e,options:l}}t.d(n,"a",(function(){return r}))},function(e,n,t){var r=t(5),o=t(1),a=t(7),i=Object.defineProperty,s={},c=function(e){throw e};e.exports=function(e,n){if(a(s,e))return s[e];n||(n={});var t=[][e],l=!!a(n,"ACCESSORS")&&n.ACCESSORS,u=a(n,0)?n[0]:c,p=a(n,1)?n[1]:void 0;return s[e]=!!t&&!o((function(){if(l&&!r)return!0;var e={length:-1};l?i(e,1,{enumerable:!0,get:c}):e[1]=1,t.call(e,u,p)}))}},function(e,n,t){var r=t(126),o=t(2),a=function(e){return"function"==typeof e?e:void 0};e.exports=function(e,n){return arguments.length<2?a(r[e])||a(o[e]):r[e]&&r[e][n]||o[e]&&o[e][n]}},function(e,n,t){var r=t(5),o=t(84),a=t(35),i=t(11),s=t(39),c=t(7),l=t(121),u=Object.getOwnPropertyDescriptor;n.f=r?u:function(e,n){if(e=i(e),n=s(n,!0),l)try{return u(e,n)}catch(e){}if(c(e,n))return a(!o.f.call(e,n),e[n])}},function(e,n){e.exports=function(e){if(null==e)throw TypeError("Can't call method on "+e);return e}},function(e,n,t){"use strict";var r=t(0),o=t(32).filter,a=t(59),i=t(18),s=a("filter"),c=i("filter");r({target:"Array",proto:!0,forced:!s||!c},{filter:function(e){return o(this,e,arguments.length>1?arguments[1]:void 0)}})},function(e,n){e.exports=!1},function(e,n){var t={}.toString;e.exports=function(e){return t.call(e).slice(8,-1)}},function(e,n){e.exports=function(e){if("function"!=typeof e)throw TypeError(String(e)+" is not a function");return e}},function(e,n,t){var r=t(235),o=t(238);e.exports=function(e,n){var t=o(e,n);return r(t)?t:void 0}},function(e,n,t){"use strict";var r=t(114).charAt,o=t(31),a=t(127),i=o.set,s=o.getterFor("String Iterator");a(String,"String",(function(e){i(this,{type:"String Iterator",string:String(e),index:0})}),(function(){var e,n=s(this),t=n.string,o=n.index;return o>=t.length?{value:void 0,done:!0}:(e=r(t,o),n.index+=e.length,{value:e,done:!1})}))},function(e,n,t){var r,o=t(6),a=t(110),i=t(82),s=t(40),c=t(125),l=t(79),u=t(55),p=u("IE_PROTO"),d=function(){},f=function(e){return" - + @@ -46,6 +46,6 @@

    Distributed Infrastructure

    Adhering to design principles of distributed systems, Venus chain service enables you to scale and guarantees availability to your storage providing systems

    Optimized Storage Deal

    Solution for both storage client and storage provider enables seamless storage deal process

    Reimagined Storage Power

    Completely revamped sealer submodule to help you to grow and maintain your storage power with more efficiency and stability

    MIT Apache dual Licensed
    - + diff --git a/intro/_Footer.html b/intro/_Footer.html index 2c917ed41..d9ca8e4f3 100644 --- a/intro/_Footer.html +++ b/intro/_Footer.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    - +

    See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    + diff --git a/intro/contribute-docs.html b/intro/contribute-docs.html index 5dc802709..a6b0f6317 100644 --- a/intro/contribute-docs.html +++ b/intro/contribute-docs.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -66,12 +66,12 @@ git push -f git@github.com:filecoin-project/venus-docs.git master:gh-pages cd - -

    # Notes:

    +

    # Notes:

    ←

    - + diff --git a/intro/damocles.html b/intro/damocles.html index e3558995a..3f2da8c1d 100644 --- a/intro/damocles.html +++ b/intro/damocles.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • damocles

    # Damocles

    Damocles, formerly known as Venus Power Service, is THE Filecoin storage power solution. Learn more about Damocles here (opens new window).

    - +

    damocles

    # Damocles

    Damocles, formerly known as Venus Power Service, is THE Filecoin storage power solution. Learn more about Damocles here (opens new window).

    + diff --git a/intro/droplet.html b/intro/droplet.html index 4112e5144..61666ffca 100644 --- a/intro/droplet.html +++ b/intro/droplet.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • droplet

    # Droplet

    Droplet, formerly known as Venus Deal Service, is THE Filecoin storage deal solution. Learn more about Droplet here (opens new window).

    - +

    droplet

    # Droplet

    Droplet, formerly known as Venus Deal Service, is THE Filecoin storage deal solution. Learn more about Droplet here (opens new window).

    + diff --git a/intro/index.html b/intro/index.html index 7b217db05..e43e2e5e4 100644 --- a/intro/index.html +++ b/intro/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,11 +37,11 @@ English
  • 简体中文 -

    • # Preface

    Multiple interoperable implementations are required on the same public blockchain. Each implementation may has its own set of security issues, but they are not all the same . Therefore, launching cryptocurrency networks with multiple implementations can reduce the catastrophic errors. Venus is one of the four implementations in Filecoin network.

    Venus (Capital V) refers to one of the general implementations of Filecoin, while venus (v in lowercase) refers to one of the components of Venus. Venus is committed to helping small and medium-sized storage providers to join the Filecoin ecosystem network with a lower barrier.

    Now Venus has lead the way to the distributed storage pool of Filecoin through components like venus、damocles, sophon-miner, venus-wallet, sophon-messager, sophon-auth, sophon-gateway. In the future, Venus will continue its evolvement and jointly promote the open source development of Filecoin ecosystem.

    # Why are we doing this

    On June 2020, Protocol Labs launched an RFP to handover the maintenance of go-filecoin to another community member, and IPFSForce applied for it and successfully obtain the project. In October, We renamed go-filecoin as Venus, and take over the maintenance of Venus Implementation.

    Before IPFSForce’s application, maintenance effort is seriously lacking in Venus project. In terms of protocols and components, vm,mpool, chain, rpc are all available, but all have different kind of issue. It takes Venus team more than 3 months to gradually fix protocol layer, code layer, and problematic fuctions, making Venus complete the interoperability with Lotus, so that the nodes using Venus can run smoothly in the Filecoin network. And then we let Venus support calibration and 2K networks.

    After completing the above work, we start to set the roadmap of Venus development.

    We plan to let Venus support the development of storage pool. At the begining, we decide to achieve the best of expansion from a single storage provider. It is technically feasible, but the biggest problem was caused by the mechanism of Filecoin proofs. Storage providers in the Filecoin network have to submit the PoSt periodically, and in order to generate the proof, they need to read the data of a whole Partition. If all sectors are distributed in different places, to read the data through the public network will be heavy time-consuming.

    After that, through several times of re-design and modification, we finally decide to build it as a distributed storage pool. Distributed storage pool will not completely in charge with any single storage provider, but managed by multiple storage providers, which is more like a storage provider group/union.

    The external features of Venus distributed storage pool are similar to other pools. Storage Providers can store their resources in distributed geographic nodes. As long as there is a stable connection to the network, the storage provider can create a node accessible to Venus storage pool; The probability of earning the block reward is proportional to the amount of storage the storage provider contributes to the Filecoin network, and the final result of separate calculation and overall calculation should be the same: n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p, which provides a theoretical basis on the algorithm.

    For the storage and retrieval, storage providers can access the network through the venus unified entrance or by themselves. In the design and with the permission from storage providers, venus will select the appropriate node to store data according to specific requirements, so that the data is closer to the real scenario.

    1. Data storage: component sharing is supported, and the storage will be gradually migrated to MySQL to ensure the metadata security of Venus through some highly available solutions.

    2. Shared Modules: support high availability, ensure the quality of service, reduce the time cost and maintenance cost of storage providers, which make it easier for storage providers to join the storage pool. Nowadays, mining is a high-tech activity, but to achieve Filecoin's goal to get the utmost out of storage resources, it is inevitable to lower the threshold to attract more participants.

    3. Combine the right for more block rewards: storage providers can integrate resources together and help each other pack messages, so as to avoid the situation of small storage providers that no one can pack messages.

    4. Improve the TPS of Filecoin network: if there are multiple blocks at the same height, sophon-miner can ensure that the messages in each block are different, as the avoidance of highly-repeated messages when blocks are separated.

    5. Improve the stability of messages: messages in storing activities can be separated from nodes and managed by sophon-messager, which can track the latest state of the chain to set a relatively reasonable estimated gas parameter, and also supports users to set a message parameter themselves.

    6. Improve the speed of data access: the current Filecoin network is more like a pool which is merely for data storage, but as a complete data service, it also needs data retrieval to realize its real value. With sufficient miner users, Venus has more chances to promote the real data application. For example, for data distribution, Venus can distribute the data to some storage providers' nodes nearest to the customers, which can improve the access speed; some public data can distribute these data to more nodes as much as possible to ensure that access at any location is effective, which can greatly improve the performance of IPFS network and further realize the goal of IPFS, as one of the Web3.0 solutions.

    # How Venus works

    # Architecture

    Venus architecture includes venus, sophon-miner, damocles, sophon-messager, venus-wallet, sophon-auth, and droplet. In the classic architecture, venus, sophon-miner, sophon-auth, sophon-messager and droplet are public components, and damocles and venus-wallet are local components.

    Public components can be established by service providers or by multiple storage providers, and they only need to run damocles and venus-wallet locally. In fact, all components of Venus are protocol oriented. If storage providers have sufficient skills, they can also deploy all or part of the public components locally, so the deployment can be more flexible.

    The following figure is a typical application scenario in our design.

    The following contents show the relationship between components, which are similar in function, but with more powerful expanded functions in details and uses.

    • sophon-auth --> token authentication service extend lotus jwt
    • sophon-miner --> lotus-miner block produce part
    • damocles --> lotus-miner sealer scheduler part/wd
    • venus daemon --> lotus daemon
    • venus-wallet -> lotus wallet part
    • sophon-messager --> lotus mpool

    # venus

    venus is similar to lotus-daemon, which is used to support all nodes. venus is connected to the Filecoin blockchain network to provide data support for Venus. venus can be used as an ordinary node. It has all the necessary functions of blockchain nodes, such as chain, mpool and wallet. The APIs of venus are almost compatible with those of lotus (you can mention the issue of incompatible APIs). On venus, you can create private keys, query assets, transfer funds, etc. In a typical deployment environment, venus only provides data query service on the basic chain without private key restoration. The block data needed by slashfilter is stored in the database, and the node itself is stateless. In this case, venus node can realize its high availability through nginx reverse proxy.

    # Venus and Lotus,The Difference

    1. External signature is supported in the API of creating block (request will be proposed to lotus too).
    2. The API of message selection supports the selection of multiple batches of messages at the same time, which is used to select messages when multiple storage providers get the block rewards.
    3. Support the centralized authorization access to sophon-auth.

    Therefore, if you are interested in the mixed deployment of venus / lotus, you need to use Venus project which is compatible to Lotus (opens new window) or pick your own CCS.

    # sophon-auth

    sophon-auth (opens new window) (formerly venus-auth) is a component used for authorization. In a typical deployment environment, sophon-auth is used to provide authorization services to venus, sophon-miner and sophon-messager. Local nodes need to be authorized to have access to the shared components. Based on the authorization, sophon-auth will expand its functions, such as security control, including access restriction and blacklist.

    # sophon-miner

    The function of sophon-miner (opens new window) (formerly venus-miner) is to combine the rights to earn block rewards. The program can configure the location of multiple storage providers and their sealers and wallets, and generate blocks for these storage providers at the same time. sophon-miner has the following features:

    1. Separate data: because the process of generating blocks needs to access data, and storage provider's sealer may be heterogeneous, but now most storage providers will use their own codes, so there is a problem about how to access these data to realize joint mining. By sophon-miner’s independence on the storage organization mode and completing the proofs by storage providers, no matter how the miner's sealer organizes the storage, as long as the Computeproof API is implemented, sophon-miner can generate the proof through it.
    2. Separate private key: when calculating random numbers and signature blocks, all operations about private key are accessed through remote wallet, which can improve the security of mining activities.
    3. Improve storage providers' wincount and TPS: when the miner who uses sophon-miner rto get multiple (> 1) rights of block rewards in a period, sophon-miner will try to select different messages from the message pool for packaging, which can somehow improve the speed of these messages on the chain, and make the block get more gas premium.

    # sophon-messenger

    The goal of sophon-messager (opens new window) (formerly venus-messager) is to help messages on chain more efficiently, and to flexibly control the timing of messages on chain to reduce gas consumption and control the data traffic, etc. It includes remote wallet management, address management and message management.

    1. Wallet management: sophon-messager connects multiple wallets and scans these addresses into the list.
    2. Address management: the major purpose is to manage the nonce value to ensure that the value can be assigned in the correct order.
    3. Message management: it is divided into three parts, namely "message receiving and saving", "message selection and pushing" and "tracking the status of message on the chain".

    In terms of functions:

    1. Support remote wallet: one messenger supports multiple wallets to manage their message separately.
    2. Support local storage of SQLite and remote storage of MySQL for more secure and stable storage.
    3. Dynamic Fill: gas related parameters and nonce are to be filled out when sending a message on chain according to gas and push policy, to make sure the gas-estimation and other setting are valid.
    4. Maintain message status, including whether the message is chained and replaced and save the results of the execution.
    5. Multi-point message delivery (directly to the blockchain network with libp2p, push to the node by Mpool API), to make sure that messages are propagated over the network.
    6. Flexible config includes gas estimate, msg push strategy, etc.

    # venus-wallet

    venus-wallet is a remote wallet, which can support both Lotus and Venus in terms of protocols. In a typical deployment environment, this module is deployed locally by storage providers, and the security of assets is guaranteed by certain policy configuration. venus-wallet has the following features:

    1. Private key management function: currently it supports the private key management of asymmetric algorithms BLS and SECP, and it can generate random private key, and uses aes128 to encrypt and store the private key symmetrically whilst supports the private key to sign the data.
    2. Signature verification: each signature type has its verification policy, which ensures that the signer won't do deceits the wallet through non-credible signature type.
    3. Signature tactics module: for the Lotus and Venus implementation of Filecoin, the module is created to manage 10 existing data structures and more than 60 signature types in message data structure, and configure various combination methods on demand to bind private key signature rules, and then integrate several different private key signature rules and authorize them to external components for further usage.

    # droplet

    Droplet (formerly venus-market) is the market component in the Venus system. Its vision is to create a distributed storage and retrieval market in the Filecoin network. Currently, it has realized order storage and retrieval compatible with the Lotus protocol, and is gradually moving towards receiving orders from multiple clusters of droplet services and providing unified retrieval services to the outside world. You can refer to droplet design and roadmap (opens new window).

    # sophon-gateway

    sophon-gateway (opens new window) (formerly venus-gateway) is a bridge between independent components and the chain service layer. It is used to simplify deployment and reduce the complexity of storage provider access, and increase the security of storage provider access. When the independent component is started, its service interface is registered with sophon-gateway. The chain service component needs to request the corresponding cluster’s service API through sophon-gateway.

    • Storage providers do not need external IP and exposed wallet service;
    • After the storage pool is configured with an SSL certificate, the connection between the cluster and the storage pool is secure;
    • Storage providers can simply register multiple clients (wallets/proofs) with the storage pool to achieve high availability.

    sophon-gateway

    # damocles

    damocles (opens new window) (formerly venus-cluster) is a new version of sector sealing and computing power maintenance components launched by Venus. Compared with the original venus-sealer, it has certain advantages in task scheduling and maximizing system resources, and its target users will also be different

    # Learn more about Venus

    +

    # Preface

    Multiple interoperable implementations are required on the same public blockchain. Each implementation may has its own set of security issues, but they are not all the same . Therefore, launching cryptocurrency networks with multiple implementations can reduce the catastrophic errors. Venus is one of the four implementations in Filecoin network.

    Venus (Capital V) refers to one of the general implementations of Filecoin, while venus (v in lowercase) refers to one of the components of Venus. Venus is committed to helping small and medium-sized storage providers to join the Filecoin ecosystem network with a lower barrier.

    Now Venus has lead the way to the distributed storage pool of Filecoin through components like venus、damocles, sophon-miner, venus-wallet, sophon-messager, sophon-auth, sophon-gateway. In the future, Venus will continue its evolvement and jointly promote the open source development of Filecoin ecosystem.

    # Why are we doing this

    On June 2020, Protocol Labs launched an RFP to handover the maintenance of go-filecoin to another community member, and IPFSForce applied for it and successfully obtain the project. In October, We renamed go-filecoin as Venus, and take over the maintenance of Venus Implementation.

    Before IPFSForce’s application, maintenance effort is seriously lacking in Venus project. In terms of protocols and components, vm,mpool, chain, rpc are all available, but all have different kind of issue. It takes Venus team more than 3 months to gradually fix protocol layer, code layer, and problematic fuctions, making Venus complete the interoperability with Lotus, so that the nodes using Venus can run smoothly in the Filecoin network. And then we let Venus support calibration and 2K networks.

    After completing the above work, we start to set the roadmap of Venus development.

    We plan to let Venus support the development of storage pool. At the begining, we decide to achieve the best of expansion from a single storage provider. It is technically feasible, but the biggest problem was caused by the mechanism of Filecoin proofs. Storage providers in the Filecoin network have to submit the PoSt periodically, and in order to generate the proof, they need to read the data of a whole Partition. If all sectors are distributed in different places, to read the data through the public network will be heavy time-consuming.

    After that, through several times of re-design and modification, we finally decide to build it as a distributed storage pool. Distributed storage pool will not completely in charge with any single storage provider, but managed by multiple storage providers, which is more like a storage provider group/union.

    The external features of Venus distributed storage pool are similar to other pools. Storage Providers can store their resources in distributed geographic nodes. As long as there is a stable connection to the network, the storage provider can create a node accessible to Venus storage pool; The probability of earning the block reward is proportional to the amount of storage the storage provider contributes to the Filecoin network, and the final result of separate calculation and overall calculation should be the same: n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p, which provides a theoretical basis on the algorithm.

    For the storage and retrieval, storage providers can access the network through the venus unified entrance or by themselves. In the design and with the permission from storage providers, venus will select the appropriate node to store data according to specific requirements, so that the data is closer to the real scenario.

    1. Data storage: component sharing is supported, and the storage will be gradually migrated to MySQL to ensure the metadata security of Venus through some highly available solutions.

    2. Shared Modules: support high availability, ensure the quality of service, reduce the time cost and maintenance cost of storage providers, which make it easier for storage providers to join the storage pool. Nowadays, mining is a high-tech activity, but to achieve Filecoin's goal to get the utmost out of storage resources, it is inevitable to lower the threshold to attract more participants.

    3. Combine the right for more block rewards: storage providers can integrate resources together and help each other pack messages, so as to avoid the situation of small storage providers that no one can pack messages.

    4. Improve the TPS of Filecoin network: if there are multiple blocks at the same height, sophon-miner can ensure that the messages in each block are different, as the avoidance of highly-repeated messages when blocks are separated.

    5. Improve the stability of messages: messages in storing activities can be separated from nodes and managed by sophon-messager, which can track the latest state of the chain to set a relatively reasonable estimated gas parameter, and also supports users to set a message parameter themselves.

    6. Improve the speed of data access: the current Filecoin network is more like a pool which is merely for data storage, but as a complete data service, it also needs data retrieval to realize its real value. With sufficient miner users, Venus has more chances to promote the real data application. For example, for data distribution, Venus can distribute the data to some storage providers' nodes nearest to the customers, which can improve the access speed; some public data can distribute these data to more nodes as much as possible to ensure that access at any location is effective, which can greatly improve the performance of IPFS network and further realize the goal of IPFS, as one of the Web3.0 solutions.

    # How Venus works

    # Architecture

    Venus architecture includes venus, sophon-miner, damocles, sophon-messager, venus-wallet, sophon-auth, and droplet. In the classic architecture, venus, sophon-miner, sophon-auth, sophon-messager and droplet are public components, and damocles and venus-wallet are local components.

    Public components can be established by service providers or by multiple storage providers, and they only need to run damocles and venus-wallet locally. In fact, all components of Venus are protocol oriented. If storage providers have sufficient skills, they can also deploy all or part of the public components locally, so the deployment can be more flexible.

    The following figure is a typical application scenario in our design.

    The following contents show the relationship between components, which are similar in function, but with more powerful expanded functions in details and uses.

    • sophon-auth --> token authentication service extend lotus jwt
    • sophon-miner --> lotus-miner block produce part
    • damocles --> lotus-miner sealer scheduler part/wd
    • venus daemon --> lotus daemon
    • venus-wallet -> lotus wallet part
    • sophon-messager --> lotus mpool

    # venus

    venus is similar to lotus-daemon, which is used to support all nodes. venus is connected to the Filecoin blockchain network to provide data support for Venus. venus can be used as an ordinary node. It has all the necessary functions of blockchain nodes, such as chain, mpool and wallet. The APIs of venus are almost compatible with those of lotus (you can mention the issue of incompatible APIs). On venus, you can create private keys, query assets, transfer funds, etc. In a typical deployment environment, venus only provides data query service on the basic chain without private key restoration. The block data needed by slashfilter is stored in the database, and the node itself is stateless. In this case, venus node can realize its high availability through nginx reverse proxy.

    # Venus and Lotus,The Difference

    1. External signature is supported in the API of creating block (request will be proposed to lotus too).
    2. The API of message selection supports the selection of multiple batches of messages at the same time, which is used to select messages when multiple storage providers get the block rewards.
    3. Support the centralized authorization access to sophon-auth.

    Therefore, if you are interested in the mixed deployment of venus / lotus, you need to use Venus project which is compatible to Lotus (opens new window) or pick your own CCS.

    # sophon-auth

    sophon-auth (opens new window) (formerly venus-auth) is a component used for authorization. In a typical deployment environment, sophon-auth is used to provide authorization services to venus, sophon-miner and sophon-messager. Local nodes need to be authorized to have access to the shared components. Based on the authorization, sophon-auth will expand its functions, such as security control, including access restriction and blacklist.

    # sophon-miner

    The function of sophon-miner (opens new window) (formerly venus-miner) is to combine the rights to earn block rewards. The program can configure the location of multiple storage providers and their sealers and wallets, and generate blocks for these storage providers at the same time. sophon-miner has the following features:

    1. Separate data: because the process of generating blocks needs to access data, and storage provider's sealer may be heterogeneous, but now most storage providers will use their own codes, so there is a problem about how to access these data to realize joint mining. By sophon-miner’s independence on the storage organization mode and completing the proofs by storage providers, no matter how the miner's sealer organizes the storage, as long as the Computeproof API is implemented, sophon-miner can generate the proof through it.
    2. Separate private key: when calculating random numbers and signature blocks, all operations about private key are accessed through remote wallet, which can improve the security of mining activities.
    3. Improve storage providers' wincount and TPS: when the miner who uses sophon-miner rto get multiple (> 1) rights of block rewards in a period, sophon-miner will try to select different messages from the message pool for packaging, which can somehow improve the speed of these messages on the chain, and make the block get more gas premium.

    # sophon-messenger

    The goal of sophon-messager (opens new window) (formerly venus-messager) is to help messages on chain more efficiently, and to flexibly control the timing of messages on chain to reduce gas consumption and control the data traffic, etc. It includes remote wallet management, address management and message management.

    1. Wallet management: sophon-messager connects multiple wallets and scans these addresses into the list.
    2. Address management: the major purpose is to manage the nonce value to ensure that the value can be assigned in the correct order.
    3. Message management: it is divided into three parts, namely "message receiving and saving", "message selection and pushing" and "tracking the status of message on the chain".

    In terms of functions:

    1. Support remote wallet: one messenger supports multiple wallets to manage their message separately.
    2. Support local storage of SQLite and remote storage of MySQL for more secure and stable storage.
    3. Dynamic Fill: gas related parameters and nonce are to be filled out when sending a message on chain according to gas and push policy, to make sure the gas-estimation and other setting are valid.
    4. Maintain message status, including whether the message is chained and replaced and save the results of the execution.
    5. Multi-point message delivery (directly to the blockchain network with libp2p, push to the node by Mpool API), to make sure that messages are propagated over the network.
    6. Flexible config includes gas estimate, msg push strategy, etc.

    # venus-wallet

    venus-wallet is a remote wallet, which can support both Lotus and Venus in terms of protocols. In a typical deployment environment, this module is deployed locally by storage providers, and the security of assets is guaranteed by certain policy configuration. venus-wallet has the following features:

    1. Private key management function: currently it supports the private key management of asymmetric algorithms BLS and SECP, and it can generate random private key, and uses aes128 to encrypt and store the private key symmetrically whilst supports the private key to sign the data.
    2. Signature verification: each signature type has its verification policy, which ensures that the signer won't do deceits the wallet through non-credible signature type.
    3. Signature tactics module: for the Lotus and Venus implementation of Filecoin, the module is created to manage 10 existing data structures and more than 60 signature types in message data structure, and configure various combination methods on demand to bind private key signature rules, and then integrate several different private key signature rules and authorize them to external components for further usage.

    # droplet

    Droplet (formerly venus-market) is the market component in the Venus system. Its vision is to create a distributed storage and retrieval market in the Filecoin network. Currently, it has realized order storage and retrieval compatible with the Lotus protocol, and is gradually moving towards receiving orders from multiple clusters of droplet services and providing unified retrieval services to the outside world. You can refer to droplet design and roadmap (opens new window).

    # sophon-gateway

    sophon-gateway (opens new window) (formerly venus-gateway) is a bridge between independent components and the chain service layer. It is used to simplify deployment and reduce the complexity of storage provider access, and increase the security of storage provider access. When the independent component is started, its service interface is registered with sophon-gateway. The chain service component needs to request the corresponding cluster’s service API through sophon-gateway.

    • Storage providers do not need external IP and exposed wallet service;
    • After the storage pool is configured with an SSL certificate, the connection between the cluster and the storage pool is secure;
    • Storage providers can simply register multiple clients (wallets/proofs) with the storage pool to achieve high availability.

    sophon-gateway

    # damocles

    damocles (opens new window) (formerly venus-cluster) is a new version of sector sealing and computing power maintenance components launched by Venus. Compared with the original venus-sealer, it has certain advantages in task scheduling and maximizing system resources, and its target users will also be different

    # Learn more about Venus

    One Pager →

    - + diff --git a/intro/one-pager.html b/intro/one-pager.html index be5eb27e4..1a8a1d6fa 100644 --- a/intro/one-pager.html +++ b/intro/one-pager.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • venus-cluster

    +

    venus-cluster

    ← →

    - + diff --git a/intro/sophon.html b/intro/sophon.html index e4f5a2214..5ae3b7854 100644 --- a/intro/sophon.html +++ b/intro/sophon.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • sophon

    # Sophon

    Sophon, formerly known as Venus chain service, is THE Filecoin super node solution. Learn more about Sophon here (opens new window).

    - +

    sophon

    # Sophon

    Sophon, formerly known as Venus chain service, is THE Filecoin super node solution. Learn more about Sophon here (opens new window).

    + diff --git a/operation/Efficiency_of_sealing.html b/operation/Efficiency_of_sealing.html index 193858cd7..e9452e259 100644 --- a/operation/Efficiency_of_sealing.html +++ b/operation/Efficiency_of_sealing.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -139,7 +139,7 @@

    For example, if we have one box and can finish P1 in 240 minutes, P2 in 30 minutes and Commit in 35 minutes, then you can derive daily growth by the following chart.

    Task Minute Parallel Hourly production rate
    P1 240 1 0.25 = 1 / (240 /60)
    P2 30 1 2 = 1 / (30 /60)
    Commit 35 1 1.71 = 1 / (35 /60)

    # Finding optimal task configurations

    From the table above, we know that daily growth will be bottlenecked by P1. Adjust number of parallel tasks for different types of task to achieve maximum efficiency.

    Task Minutes Parallel Hourly productin Output Memory consumption
    P1 240 7 1.75 = 7 / (240 /60) 1344 G 504 G = 7*64+56
    P2 30 1 2 = 1 / (30 /60) 1536 G 96 G = 1*96
    Commit 35 1 1.71 = 1 / (35 /60) 1316 G 192 G = 1*128+64

    The goal is to have output for each task to be as close as possilbe so that the sealing pipeline runs in its maximum efficiency. Things to watchout for includes...

    1. hourly production for Commit is lower than P1, which may result in tasks backlogged in Commit phase.
    2. When one type of tasks being overly efficient than others, resources may become idle.
    3. Miro management is needed to have highest possible efficiency.

    # Finding optimal pledging

    For example, if you find 7 P1 task to the optimal for your system, change the following venus-sealer configurations.

    [Sealing]  
   MaxSealingSectors = 7

    # Stop-loss

    If one of tasks fails too many times, manual intervention is needed to get sealing pipeline back to its normal output.

    Remove sectors when you have the following issues.

    1. Expired ticket
    2. Expired Commit
    3. Corrupted proof params

    To remove incomplete sectors.

    venus-sealer sectors remove --really-do-it <sectorNum>
-
    - +
    + diff --git a/operation/System_monitor_of_Zabbix.html b/operation/System_monitor_of_Zabbix.html index 878dd3175..b377f12a2 100644 --- a/operation/System_monitor_of_Zabbix.html +++ b/operation/System_monitor_of_Zabbix.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -112,7 +112,7 @@

    Add zabbix-agent.

    Check zabbix RAM usage.

    Check problems in dashboard. -

    - +

    + diff --git a/operation/_Footer.html b/operation/_Footer.html index 67eb05dc5..9d1af077b 100644 --- a/operation/_Footer.html +++ b/operation/_Footer.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    - +

    See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    + diff --git a/operation/example-single-box.html b/operation/example-single-box.html index 128ac9208..0f93260b7 100644 --- a/operation/example-single-box.html +++ b/operation/example-single-box.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # Venus Single box setup

    This is an exmaple venus single box setup that is estimated to grow 1TiB power per day.

    # Specs

    Parts Recommendation
    CPU 3970X * 1 (32 core)
    RAM 512G
    NVMe (for sealing) 3T/SSD
    SSD (for OS) 500G
    GPU RTX 3080 * 1

    # Job scheduling

    Task Core limit Minutes RAM(G) Hourly production rate Daily growth(T)
    P1 * 5 20 220 376 1.3636 1.0227
    AP, P2, Commit 12 10 120 3 1.125

    For more information on core limit, please refer to the next tutorial.

    - +

    # Venus Single box setup

    This is an exmaple venus single box setup that is estimated to grow 1TiB power per day.

    # Specs

    Parts Recommendation
    CPU 3970X * 1 (32 core)
    RAM 512G
    NVMe (for sealing) 3T/SSD
    SSD (for OS) 500G
    GPU RTX 3080 * 1

    # Job scheduling

    Task Core limit Minutes RAM(G) Hourly production rate Daily growth(T)
    P1 * 5 20 220 376 1.3636 1.0227
    AP, P2, Commit 12 10 120 3 1.125

    For more information on core limit, please refer to the next tutorial.

    + diff --git a/operation/index.html b/operation/index.html index 560da66c5..cc5877700 100644 --- a/operation/index.html +++ b/operation/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,11 +37,11 @@ English
  • 简体中文 -

    • # Deployment of a Venus System

    Venus refers to products developed and maintained by Venus team to interact efficiently and robustly with Filecoin protocol. The target audience are storage providers, storage clients, ecosystem partners and Dapp. Venus has been widely adopted in SP and SC use cases.

    # Deployment

    Since the rebranding (opens new window) of Venus by the end of 2022, three main products has been formed, namely Sophon (opens new window)，Damocles (opens new window) and Droplet (opens new window). Please refer to each product's own documentation for deployment guide.

    # Architecture

    +

    # Deployment of a Venus System

    Venus refers to products developed and maintained by Venus team to interact efficiently and robustly with Filecoin protocol. The target audience are storage providers, storage clients, ecosystem partners and Dapp. Venus has been widely adopted in SP and SC use cases.

    # Deployment

    Since the rebranding (opens new window) of Venus by the end of 2022, three main products has been formed, namely Sophon (opens new window)，Damocles (opens new window) and Droplet (opens new window). Please refer to each product's own documentation for deployment guide.

    # Architecture

    nv22 upgrade →

    - + diff --git a/operation/lotus-vs-venus.html b/operation/lotus-vs-venus.html index 2244bc382..48a2f8199 100644 --- a/operation/lotus-vs-venus.html +++ b/operation/lotus-vs-venus.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # Commands from Lotus

    Many basic commands including but not limited to creating worker/controler addresses (opens new window), setting different types of configurations (opens new window), or changing storage locations (opens new window) apply to both Lotus and Venus. Node operators are expected to follow the same process as what is instructed on the Lotus documentation. If you encounter any questions please do not hesitate to reach out to us on #fil-venus (opens new window).

    - +

    # Commands from Lotus

    Many basic commands including but not limited to creating worker/controler addresses (opens new window), setting different types of configurations (opens new window), or changing storage locations (opens new window) apply to both Lotus and Venus. Node operators are expected to follow the same process as what is instructed on the Lotus documentation. If you encounter any questions please do not hesitate to reach out to us on #fil-venus (opens new window).

    + diff --git a/operation/nv15-upgrade.html b/operation/nv15-upgrade.html index f678b5184..35f809870 100644 --- a/operation/nv15-upgrade.html +++ b/operation/nv15-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -46,11 +46,11 @@ "maxFee": "10 FIL" },

    WARNING

    As a result of a mandatory network upgrade with API changes, sealer connection maybe lost during the this step of the upgrade.

    1. venus wrapped deamon: mandatory upgrade (if you are using chain-co); branch/tag venus/v1.14.0;

    TIP

    Checkups after upgrading:

    • see if chain synchronization is working properly
    • see if connection to venus-auth is okay
    curl http://127.0.0.1:3453/rpc/v0 -X POST -H "Content-Type: application/json" -H "Authorization: Bearer <YOUR_TOKEN>" -d '{"method": "Filecoin.ChainHead","params":[], "id": 0}'
-
    1. chain-co: mandatory upgrade (if you deployed chain-co for your HA solution); branch/tag v0.1.0;

    TIP

    Checkups after upgrading:

    • see if two new API MpoolPending and MpoolGetNonce are working properly

    1. venus-messager: mandatory upgrade; branch/tag v1.4.0;

    2. venus-gateway: mandatory upgrade; branch/tag v1.2.0;

    TIP

    • support for both old and new API due to changes in ComputeProof's params
    • see if both v0 and v1 APIs are working properly
    1. venus-miner: mandatory upgrade; branch/tag v1.4.0;

    TIP

    Parameter changes for ComputeProof.

    1. venus-market: optional upgrade; branch/tag v2.0.0;

    2. venus-sealer: mandatory upgrade; branch/tag v1.4.0;

    For more question regarding nv15 upgrade, please refer to this discussion thread (opens new window).

    +

    1. chain-co: mandatory upgrade (if you deployed chain-co for your HA solution); branch/tag v0.1.0;

    TIP

    Checkups after upgrading:

    • see if two new API MpoolPending and MpoolGetNonce are working properly

    1. venus-messager: mandatory upgrade; branch/tag v1.4.0;

    2. venus-gateway: mandatory upgrade; branch/tag v1.2.0;

    TIP

    • support for both old and new API due to changes in ComputeProof's params
    • see if both v0 and v1 APIs are working properly
    1. venus-miner: mandatory upgrade; branch/tag v1.4.0;

    TIP

    Parameter changes for ComputeProof.

    1. venus-market: optional upgrade; branch/tag v2.0.0;

    2. venus-sealer: mandatory upgrade; branch/tag v1.4.0;

    For more question regarding nv15 upgrade, please refer to this discussion thread (opens new window).

    ←

    - + diff --git a/operation/nv16-upgrade.html b/operation/nv16-upgrade.html index 4cf6a439b..06349d091 100644 --- a/operation/nv16-upgrade.html +++ b/operation/nv16-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -60,7 +60,7 @@ init bafk2bzaceaipvjhoxmtofsnv3aj6gj5ida4afdrxa4ewku2hfipdlxpaektlw storagepower bafk2bzacebjvqva6ppvysn5xpmiqcdfelwbbcxmghx5ww6hr37cgred6dyrpm verifiedregistry bafk2bzaceb3zbkjz3auizmoln2unmxep7dyfcmsre64vnqfhdyh7rkqfoxlw4 -

  • Mainnet can use fvm on nv15 network by setting environment variable export VENUS_USE_FVM_TO_SYNC_MAINNET_V15=1

  • If you do not troubleshoot the problem, the rust log level is not recommended to be set to trace, because more logs will be printed

  • After the upgrade, you can use the command ./venus state get-actor t01000 to confirm whether the upgrade is successful

    • # venus-messager

    Things to look out for:

    1. Whether to generate the main directory ~/.venus-messager after the upgrade

    2. After the upgrade, the main directory should contain config.toml and tipset.json, config.toml should be consistent with the configuration file used to start messager, ~/.venus-messager/tipset.json is copied from tipset.json in the current directory

    3. After the upgrade is successful, restarting again is to read the configuration is ~/.venus-messager/config.toml

    4. Whether the message can be received and pushed to the node normally

    # venus-miner

    Things to look out for:

    1. After the upgrade, use the commonly used command address state/list/update to verify it.
    2. If you use a mysql database, check that the parent_key field in the miner_blocks table is varchar(1000)

    # venus-gateway

    Things to look out for:

    1. Is wallet re-registered after the upgrade

    # venus-market

    Things to look out for::

    # venus-wallet

    # Community

    Things to look out for::

    1. Need to unlock wallet
    2. if wallet is properly registered on the gateway

    +

  • Mainnet can use fvm on nv15 network by setting environment variable export VENUS_USE_FVM_TO_SYNC_MAINNET_V15=1

  • If you do not troubleshoot the problem, the rust log level is not recommended to be set to trace, because more logs will be printed

  • After the upgrade, you can use the command ./venus state get-actor t01000 to confirm whether the upgrade is successful

    • # venus-messager

    Things to look out for:

    1. Whether to generate the main directory ~/.venus-messager after the upgrade

    2. After the upgrade, the main directory should contain config.toml and tipset.json, config.toml should be consistent with the configuration file used to start messager, ~/.venus-messager/tipset.json is copied from tipset.json in the current directory

    3. After the upgrade is successful, restarting again is to read the configuration is ~/.venus-messager/config.toml

    4. Whether the message can be received and pushed to the node normally

    # venus-miner

    Things to look out for:

    1. After the upgrade, use the commonly used command address state/list/update to verify it.
    2. If you use a mysql database, check that the parent_key field in the miner_blocks table is varchar(1000)

    # venus-gateway

    Things to look out for:

    1. Is wallet re-registered after the upgrade

    # venus-market

    Things to look out for::

    # venus-wallet

    # Community

    Things to look out for::

    1. Need to unlock wallet
    2. if wallet is properly registered on the gateway

    ← →

    - + diff --git a/operation/nv17-upgrade.html b/operation/nv17-upgrade.html index 4641a4651..c1eb92ec3 100644 --- a/operation/nv17-upgrade.html +++ b/operation/nv17-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -61,7 +61,7 @@ cron bafk2bzacebcec3lffmos3nawm5cvwehssxeqwxixoyyfvejy7viszzsxzyu26 init bafk2bzacebtdq4zyuxk2fzbdkva6kc4mx75mkbfmldplfntayhbl5wkqou33i storageminer bafk2bzacedyux5hlrildwutvvjdcsvjtwsoc5xnqdjl73ouiukgklekeuyfl4 -

  • If you are not troubleshooting anything, it is NOT recommended to set rust log level to trace as more irrelavant logs will be printed

  • After the upgrade, you can use the command ./venus state get-actor t01000 to confirm whether the upgrade is successful

    • # venus-messager

    Affected function:

    1. Increase the control of basefee, you can set the basefee separately for an address, when the basefee on the chain is higher than the basefee limit, the message will not be pushed out

    Dependency upgrade components:

    Precautions:

    1. After the upgrade, observe whether the message can be on-chained normally

    # venus-miner

    Affected function:

    Dependency upgrade components:

    Precautions:

    1. If you are upgrading from 1.7.* to v1.8.0, it will automatically migrate configuration files. Whereas if you are upgrading from 1.6.* to v1.8.0, it is required to have a reinitialization of repo (init). Please checkout this guide (opens new window) to learn more.

    2. Check if blocks can be produced normally after the upgrade.

    # venus-gateway

    Affected function:

    Precautions:

    Compile: first make dist-clean and then make

    1. Check wallet after upgrade: ./venus-gateway wallet list
    2. Check miners after upgrade: ./venus-gateway miner list

    # venus-market

    Affected function:

    Precautions:

    Compile: first make dist-clean and then make

    # venus-wallet

    Affect function:

    Precautions:

    1. Make sure to unlock the wallet after startup
    2. Check whether the wallet is registered on the gateway

    +

  • If you are not troubleshooting anything, it is NOT recommended to set rust log level to trace as more irrelavant logs will be printed

  • After the upgrade, you can use the command ./venus state get-actor t01000 to confirm whether the upgrade is successful

    • # venus-messager

    Affected function:

    1. Increase the control of basefee, you can set the basefee separately for an address, when the basefee on the chain is higher than the basefee limit, the message will not be pushed out

    Dependency upgrade components:

    Precautions:

    1. After the upgrade, observe whether the message can be on-chained normally

    # venus-miner

    Affected function:

    Dependency upgrade components:

    Precautions:

    1. If you are upgrading from 1.7.* to v1.8.0, it will automatically migrate configuration files. Whereas if you are upgrading from 1.6.* to v1.8.0, it is required to have a reinitialization of repo (init). Please checkout this guide (opens new window) to learn more.

    2. Check if blocks can be produced normally after the upgrade.

    # venus-gateway

    Affected function:

    Precautions:

    Compile: first make dist-clean and then make

    1. Check wallet after upgrade: ./venus-gateway wallet list
    2. Check miners after upgrade: ./venus-gateway miner list

    # venus-market

    Affected function:

    Precautions:

    Compile: first make dist-clean and then make

    # venus-wallet

    Affect function:

    Precautions:

    1. Make sure to unlock the wallet after startup
    2. Check whether the wallet is registered on the gateway

    ← →

    - + diff --git a/operation/nv18-upgrade.html b/operation/nv18-upgrade.html index 9d0a4c7f6..f99f11a28 100644 --- a/operation/nv18-upgrade.html +++ b/operation/nv18-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -89,7 +89,7 @@ "parameters": { "allowableClockDriftSecs": 1 }, -

    # venus-auth

    Feature:

    Dependency: none

    Precautions:

    1. Check whether the command line can be used correctly

    # venus-messager

    Function:

    1. Added additional interface authentication

    Dependency:

    Precautions:

    1. Observe if messages can be received normally after upgrading

    2. After upgrading, observe whether the message can be on-chained properly

    3. ReplacedMsg is renamed to NonceConflictMsg

    # venus-miner

    Feature:

    Dependency:

    Precautions:

    1. Check if block be produced properly after upgrading

    # venus-gateway

    Feature:

    Precautions:

    1. Compile: first make dist-clean and then make

    2. Check remote wallet after upgrading: ./venus-gateway wallet list

    3. Check miners after upgrading: ./venus-gateway miner list

    # venus-market

    Feature:

    Precautions:

    1. Compile: first make dist-clean and then make

    # venus-wallet

    Feature:

    Precautions:

    1. Need to unlock the wallet after restart

    2. Check if wallet is properly registered to the gateway

    # venus-sector-manager

    Compile: first make dist-clean and then make

    +

    # venus-auth

    Feature:

    Dependency: none

    Precautions:

    1. Check whether the command line can be used correctly

    # venus-messager

    Function:

    1. Added additional interface authentication

    Dependency:

    Precautions:

    1. Observe if messages can be received normally after upgrading

    2. After upgrading, observe whether the message can be on-chained properly

    3. ReplacedMsg is renamed to NonceConflictMsg

    # venus-miner

    Feature:

    Dependency:

    Precautions:

    1. Check if block be produced properly after upgrading

    # venus-gateway

    Feature:

    Precautions:

    1. Compile: first make dist-clean and then make

    2. Check remote wallet after upgrading: ./venus-gateway wallet list

    3. Check miners after upgrading: ./venus-gateway miner list

    # venus-market

    Feature:

    Precautions:

    1. Compile: first make dist-clean and then make

    # venus-wallet

    Feature:

    Precautions:

    1. Need to unlock the wallet after restart

    2. Check if wallet is properly registered to the gateway

    # venus-sector-manager

    Compile: first make dist-clean and then make

    ← →

    - + diff --git a/operation/nv19-upgrade.html b/operation/nv19-upgrade.html index a4cd623bb..c0ccec8b9 100644 --- a/operation/nv19-upgrade.html +++ b/operation/nv19-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -70,7 +70,7 @@ Pre-migration start: STARTING pre-migration end: COMPLETED pre-migration migration start: STARTING migration end: COMPLETED migration ``` -

    # venus-gateway

    Affected function: none

    Dependency upgrade component: venus-auth

    Precautions:

    # venus-messager

    Affected function:

    Dependency upgrade components: venus, venus-auth, venus-gateway

    Precautions:

    Note:

    # venus-miner

    Affected function:

    Dependency upgrade component: auth, venus, gateway

    Precautions:

    # venus-market

    Affected function:

    Dependency upgrade components: auth, venus, gateway, messager

    Precautions:

    # venus-wallet

    Affected function: none

    Dependency upgrade component: gateway

    Precautions:

    # venus-sector-manger

    Affected features: fip-0061 wdpost algorithm changes

    Dependency upgrade component: Chain Service component

    Precautions:

    Upgrade verification:

    1. The program starts normally
    2. Pre/Pro messages are on-chained normally
    3. Block generation is normal
    4. WdPost on-chain is normal
    5. Storage power is increasing normally
    6. Verified deal retrieval is normal
    7. Various gas, life cycle, database and aggregation settings are normal

    # Notes on Database Changes

    1. venus-messager added actor configuration and related commands, and adds actor_cfg table (opens new window)

    2. Added index to venus-market storage_deals table: CREATE INDEX idx_cdpprovider_state ON storage_deals(cdp_provider,state)

    +

    # venus-gateway

    Affected function: none

    Dependency upgrade component: venus-auth

    Precautions:

    # venus-messager

    Affected function:

    Dependency upgrade components: venus, venus-auth, venus-gateway

    Precautions:

    Note:

    # venus-miner

    Affected function:

    Dependency upgrade component: auth, venus, gateway

    Precautions:

    # venus-market

    Affected function:

    Dependency upgrade components: auth, venus, gateway, messager

    Precautions:

    # venus-wallet

    Affected function: none

    Dependency upgrade component: gateway

    Precautions:

    # venus-sector-manger

    Affected features: fip-0061 wdpost algorithm changes

    Dependency upgrade component: Chain Service component

    Precautions:

    Upgrade verification:

    1. The program starts normally
    2. Pre/Pro messages are on-chained normally
    3. Block generation is normal
    4. WdPost on-chain is normal
    5. Storage power is increasing normally
    6. Verified deal retrieval is normal
    7. Various gas, life cycle, database and aggregation settings are normal

    # Notes on Database Changes

    1. venus-messager added actor configuration and related commands, and adds actor_cfg table (opens new window)

    2. Added index to venus-market storage_deals table: CREATE INDEX idx_cdpprovider_state ON storage_deals(cdp_provider,state)

    ← →

    - + diff --git a/operation/nv21-upgrade.html b/operation/nv21-upgrade.html index 91f732faf..1129a9754 100644 --- a/operation/nv21-upgrade.html +++ b/operation/nv21-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -78,7 +78,7 @@ migration starts: STARTING migration ends: COMPLETED migration ```

    # sophon-gateway

    Functions affected:

    Dependency:

    Precautions:

    # sophon-messager

    Affected functions:

    Dependency:

    Precautions:

    # sophon-miner

    Affect functions:

    Dependency:

    Precautions:

    # Droplet

    Affected functions:

    Dependency:

    Precautions:

    # venus-wallet

    Affected functions:

    Dependency:

    Precautions:

    # damocles-manager

    Dependency:

    Precautions:

    # damocles-worker

    Dependency:

    Precautions: -Translation:

    Upgrade result verification steps:

    1. Check if program starts normally
    2. Check if Pre & prove messages are on-chained normally
    3. Check if block producing is normal
    4. Check if window post is normal
    5. Check if storage power grows normally
    6. Check if storage deal retrieval is normal
    7. Check if various gas, life cycle, and aggregation settings of the database are normal.

    # Database changes

    1. Add id field to droplet storage_deals table ==> ALTER TABLE storage_deals ADD id varchar(128)

    +Translation:

    Upgrade result verification steps:

    1. Check if program starts normally
    2. Check if Pre & prove messages are on-chained normally
    3. Check if block producing is normal
    4. Check if window post is normal
    5. Check if storage power grows normally
    6. Check if storage deal retrieval is normal
    7. Check if various gas, life cycle, and aggregation settings of the database are normal.

    # Database changes

    1. Add id field to droplet storage_deals table ==> ALTER TABLE storage_deals ADD id varchar(128)

    ← →

    - + diff --git a/operation/nv22-upgrade.html b/operation/nv22-upgrade.html index 11ec402d2..3d8515255 100644 --- a/operation/nv22-upgrade.html +++ b/operation/nv22-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,10 +37,10 @@ English
  • 简体中文 -

    • # Venus Stack nv22 Upgrade Guide (WIP)

    # Precautions

    1. Upgrade all Venus products / components
    2. Use the curl command to call the Version interface to check the version number after upgrading. Refer to the guide here (opens new window) for details.
    3. Check if pre/pro messages are on-chained
    4. Check if windowPost messages are on-chained
    5. Check if block producing is working correctly
    6. Check if the gas fee related settings are in effect

    # Products / Components to be Upgraded

    Component name tag commit
    sophon-auth v1.15.0 a1e964b
    venus v1.15.0 aabda75
    sophon-co v0.8.0 0e48712
    sophon-messager v1.15.0 1e4f0d5
    soohon-gateway v1.15.0 541891a
    venus-wallet v1.15.0 6b3de34
    sophon-miner v1.15.0 8dd6c68
    droplet v2.11.0 44481dd
    damocles-manager v0.10.0-rc1 2f6c5f9
    damocles-worker v0.10.0-rc1 2f6c5f9

    # Upgrade Sequence

    1. sophon-auth
    2. venus
    3. soohon-co
    4. soohon-gateway
    5. sophon-messager
    6. sophon-miner
    7. droplet
    8. venus-wallet
    9. damocles-manager
    10. damocles-worker

    # sophon-auth

    Affected functions:

    • Aquiring auth services from other components

    Upgrade Dependency:

    • None

    Precautions:

    • Is authentication working normally after startup?

    # Venus

    Affected functions:

    • None

    Upgrade Dependency:

    • sophon-auth

    Precautions:

    Compile: First make dist-clean and then make, this can prevent problems caused by failure to upgrade filecoin-ffi properly.

    1. Check if the vk file is complete after upgrading

    2. After the upgrade, execute the command ./venus state network-info, and then check whether the UpgradeDragonHeight is normal through the log:

      #cali
+

    # Venus Stack nv22 Upgrade Guide (WIP)

    # Precautions

    1. Upgrade all Venus products / components
    2. Use the curl command to call the Version interface to check the version number after upgrading. Refer to the guide here (opens new window) for details.
    3. Check if pre/pro messages are on-chained
    4. Check if windowPost messages are on-chained
    5. Check if block producing is working correctly
    6. Check if the gas fee related settings are in effect

    # Products / Components to be Upgraded

    Component name tag commit
    sophon-auth v1.15.0 a1e964b
    venus v1.15.1 81c99f3
    sophon-co v0.8.0 0e48712
    sophon-messager v1.15.0 1e4f0d5
    soohon-gateway v1.15.0 541891a
    venus-wallet v1.15.0 6b3de34
    sophon-miner v1.15.0 8dd6c68
    droplet v2.11.0 44481dd
    damocles-manager v0.10.0-rc1 2f6c5f9
    damocles-worker v0.10.0-rc1 2f6c5f9

    # Upgrade Sequence

    1. sophon-auth
    2. venus
    3. soohon-co
    4. soohon-gateway
    5. sophon-messager
    6. sophon-miner
    7. droplet
    8. venus-wallet
    9. damocles-manager
    10. damocles-worker

    # sophon-auth

    Affected functions:

    • Aquiring auth services from other components

    Upgrade Dependency:

    • None

    Precautions:

    • Is authentication working normally after startup?

    # Venus

    Affected functions:

    • None

    Upgrade Dependency:

    • sophon-auth

    Precautions:

    Compile: First make dist-clean and then make, this can prevent problems caused by failure to upgrade filecoin-ffi properly.

    1. Check if the vk file is complete after upgrading

    2. After the upgrade, execute the command ./venus state network-info, and then check whether the UpgradeDragonHeight is normal through the log:

      #cali
 UpgradeDragonHeight: 1427974
 #mainnet
-UpgradeDragonHeight: 3817920
+UpgradeDragonHeight: 3855360

    3. After the upgrade, you need to check if the blocks are synchronized normally.

    4. Check the mainnet v13 actors code and make sure it is the same as the output below

      ./venus state actor-cids --network-version 22
 
 # The order may be different
@@ -68,7 +68,7 @@
 pre-migration start: STARTING pre-migration end: COMPLETED pre-migration
 migration starts: STARTING migration ends: COMPLETED migration

    5. If ~/.venus exists and you need to import a snapshot, you need to delete the ~/.venus/version file first and then import the snapshot.

      • Mainnet: ./venus daemon --import-snapshot snapshot.car
      • calibnet: ./venus daemon --import-snapshot snapshot.car --network calibrationnet

    # sophon-gateway

    Affected functions:

    • None

    Upgrade Dependency:

    • sophon-auth

    Precautions:

    • When compiling, you need to first make dist-clean and then make

    # sophon-messager

    Affected functions:

    • None

    Upgrade Dependency:

    • venus
    • sophon-auth
    • sophon-gateway

    Precautions:

    • After the upgrade, you need to observe whether the messages can be received normally and whether the messages can be on-chained normally.

    # sophon-miner

    Affected functions:

    • None

    Upgrade Dependency:

    • auth
    • venus
    • gateway

    Precautions:

    # droplet

    Affected functions:

    Upgrade Dependency:

    • auth
    • venus
    • gateway
    • messager

    Precautions:

    • Check if deals and retrieval can be issued normally after the upgrade?

    # venus-wallet

    Affected functions:

    • None

    Upgrade Dependency:

    • gateway

    Precautions:

    • After the upgrade, observe whether the signing is normal and whether the message can be on-chained normally.

    # damocles-manager

    Upgrade Dependency:

    • Sophon service

    Precautions:

    • When compiling, you need to first make dist-clean and then make

    # damocles-worker

    Upgrade Dependency:

    • damocles-manager

    Precautions:

    Upgrade result verification steps:

    1. Check if the program starts normally
    2. Check if pre / pro messages are uploaded normally
    3. Check if block producing is normal
    4. Check if windowPost is normal
    5. Check if storage power grows normally
    6. Check if verified deal retrieval is normal
    7. Check if various gas, sector life cycle, and aggregation settings in the database are normal.

    # Database changes

    1. The droplet adds the direct_deals table to store DD -O deals.

    +O deals.

    ← →

    - + diff --git a/questions.html b/questions.html index 54a7668e9..21369fe7d 100644 --- a/questions.html +++ b/questions.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # Have a question?

    Filecoin.io (opens new window) - general information about the Filecoin network

    Community Channels (opens new window) - links to Filecoin community chat and forum

    Last Updated: 4/7/2024, 5:12:29 AM
    - +

    # Have a question?

    Filecoin.io (opens new window) - general information about the Filecoin network

    Community Channels (opens new window) - links to Filecoin community chat and forum

    Last Updated: 4/10/2024, 1:39:14 AM
    + diff --git a/zh/TODO.html b/zh/TODO.html index f0cf382fd..dffc36ece 100644 --- a/zh/TODO.html +++ b/zh/TODO.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -38,7 +38,7 @@
  • 简体中文

    • # 原则

      基于目前的需要，先从重构 guide 和 modules 模块，让两块联动，形成比较易读的 venus 集群部署介绍。

    • modules 模块存储各组件的简介，将不相干的文档移到对应位置

    • guide 和 modules 对于组件介绍存在很多重复的，只保留一份

    • modules 模块组件介绍老旧，超链接到项目的介绍文档，避免项目内更新后 doc 中不及时及重复劳动

    • guide 将组件介绍，编译构建，部署文档独立

    • guide 模块增加 QA 模块，将 venus discussion 的问题以超链接方式统一到 QA 模块

    • 部署模块尽量少一些设计的介绍，简明扼要，每个指定的操作尽量不涉及不相干的，以免造成误解

    # TODO list

    • [ ] modules 模块

      • [ ] 引导页内容更新
      • [ ] 不相关文档移走
      • [ ] 文档命名一致
      • [ ] 组件介绍匹配项目进度
      • [x] 编译构建独立到一个文档
      • [ ] 组件文档移除从项目中搬过来的内容，用超链接
      • [ ] market 和 cluster 模块的技术文档移到 modules 模块，

    • [ ] guide 模块

      • [ ] 将部署用到的基础知识单独形成文档
      • [x] 编译构建超链接到对应文档
      • [x] 增加部分组件的验证：怎么判断部署成功
      • [ ] 目录结构调整 -
        • [ ] market 和 cluster 归属到链服务部署和独立组件部署文档
        • [ ] .fil_withdraw_and_send.md.swp 文件删除
        • [ ] sealer 文档放到单独的目录
      • [ ] Troubleshooting-&-FAQ.md 用超链接方式管理 venus discussion

    • [ ] 移除没有价值或过时的文档

    • [ ] 在很多模块中重复的内容整合

    • [ ] 每个项目搬过来的内容使用超链接

    - +
    • [ ] market 和 cluster 归属到链服务部署和独立组件部署文档
    • [ ] .fil_withdraw_and_send.md.swp 文件删除
    • [ ] sealer 文档放到单独的目录
  • [ ] Troubleshooting-&-FAQ.md 用超链接方式管理 venus discussion

  • [ ] 移除没有价值或过时的文档

  • [ ] 在很多模块中重复的内容整合

  • [ ] 每个项目搬过来的内容使用超链接

    • + diff --git a/zh/about/index.html b/zh/about/index.html index e7faf66ba..3e2791548 100644 --- a/zh/about/index.html +++ b/zh/about/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # 使命，愿景，价值观

    • ❗️使命：建设 Filecoin 基础设施和工具，支持生态繁荣发展
    • 🌏 愿景：人人都能参与 Filecoin 生态
    • ☯️ 价值观：开放并且去信任

    # 联系方式

    # 其他资源

    - +

    # 使命，愿景，价值观

    • ❗️使命：建设 Filecoin 基础设施和工具，支持生态繁荣发展
    • 🌏 愿景：人人都能参与 Filecoin 生态
    • ☯️ 价值观：开放并且去信任

    # 联系方式

    # 其他资源

    + diff --git a/zh/index.html b/zh/index.html index 0cb9da2dd..daaf5a7d9 100644 --- a/zh/index.html +++ b/zh/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -46,6 +46,6 @@

    分布式架构

    依照分布式系统的设计理念和原则，实现了一套快速扩展，高可用的分布式基础架构

    优化订单体验

    完善了一整套方便存储提供者接收真实存储订单，同时也方便存储客户发送存储订单的解决方案

    全新的算力服务

    安全，有韧性的算力维持服务；高效，灵活，可扩容的算力增长服务

    MIT Apache dual Licensed
    - + diff --git a/zh/intro/_Footer.html b/zh/intro/_Footer.html index fb9581107..cd4683c88 100644 --- a/zh/intro/_Footer.html +++ b/zh/intro/_Footer.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    - +

    See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    + diff --git a/zh/intro/contribute-doc.html b/zh/intro/contribute-doc.html index d42629353..0dcfaec19 100644 --- a/zh/intro/contribute-doc.html +++ b/zh/intro/contribute-doc.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -44,12 +44,12 @@

    英文文档直接在 master 下更改，中文在 zh 文件夹下面更改，请确保文件夹结构完全相同。在文档上做的修改能够实时的反映在网站上，不需要重新运行命令。 增加文档需要修改 ./docs/.vuepress/config.js 文件，并在 sidebar 下的 children 增加一行新的记录。

    # 编译与部署

    yarn docs:links   # verify all links are well-formed
 yarn docs:build   # generate html pages
-

    build 完成后结果输入到 ./docs/.vuepress/dist 目录里面，将本目录覆盖 gh-page 分支即可部署项目文档。

    +

    build 完成后结果输入到 ./docs/.vuepress/dist 目录里面，将本目录覆盖 gh-page 分支即可部署项目文档。

    ←

    - + diff --git a/zh/intro/damocles.html b/zh/intro/damocles.html index 749d961b2..6a18429b9 100644 --- a/zh/intro/damocles.html +++ b/zh/intro/damocles.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • damocles

    # 执剑人

    执剑人，原 Venus 算力服务，是一个Filecoin存储算力解决方案。请在此 (opens new window)了解更多关于执剑人的信息。

    - +

    damocles

    # 执剑人

    执剑人，原 Venus 算力服务，是一个Filecoin存储算力解决方案。请在此 (opens new window)了解更多关于执剑人的信息。

    + diff --git a/zh/intro/droplet.html b/zh/intro/droplet.html index 5b70ae9f6..734c67d33 100644 --- a/zh/intro/droplet.html +++ b/zh/intro/droplet.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • droplet

    # 水滴

    水滴，原 Venus 订单服务，是一个Filecoin存储订单解决方案。请在此 (opens new window)了解更多关于水滴的信息。

    - +

    droplet

    # 水滴

    水滴，原 Venus 订单服务，是一个Filecoin存储订单解决方案。请在此 (opens new window)了解更多关于水滴的信息。

    + diff --git a/zh/intro/index.html b/zh/intro/index.html index 6d0497687..2bada4840 100644 --- a/zh/intro/index.html +++ b/zh/intro/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,11 +37,11 @@ English
  • 简体中文 -

    • # 前言

    在同一条区块链上需要具有多个互操作的软件实现，每个实现都有自己的安全问题集，但是所有实现不尽相同，因此，启动具有多种实现方式的加密货币网络可降低发生灾难性错误的可能性，Venus 正是 Filecoin 的实现之一。

    Venus 代指 Filecoin 的通用实现之一，venus 则代指 Venus 的组件之一。Venus 致力于帮助中小存储提供者能够更加简单的加入到 Filecoin 生态网络建设中。

    目前 Venus 通过 venus、damocles、sophon-miner、venus-wallet、sophon-messager、sophon-auth、sophon-gateway 组件，已经实现了 Filecoin 分布式矿池的支持，未来，Venus 将持续完善自身，并共同推进开源的 Filecoin 开发与生态的发展。

    # 为什么我们要这样做

    2020 年 6 月，Protocol Lab 发起了关于由社区后续维护 go-filecoin 的 RFP，IPFSForce 随后申请并获得了维护权。10 月，go-filecoin 更名为 Venus，我们继续推进对 Venus 项目的维护工作。

    在重新保持维护之前，Venus 是一个严重缺乏维护的项目。协议和组件上，vm/mpool/chain/rpc 虽然都有了，但是全都存在不同程度的问题，我们用了三个多月的时间，逐渐修复很多协议层、代码层，、性能的问题，使得 Venus 完成了与 Lotus 的互操作，让使用 Venus 的节点可以正常的在网络上运行。后续我们又逐渐的让 Venus 支持了 Calibration、2k 网络。

    完成以上工作后，我们着手于 Venus 的开发方向。

    我们的设计是让 Venus 向矿池的发展角度去支持，最初的设计是从“如何扩展单一存储提供者”思考，这个方向存在理论上的可行性，但是最大的问题在于 Filecoin 独特的证明机制。因为 Filecoin 网络的存储提供者必须周期性的提交‘时空证明’，而为了生成证明，存储提供者必须读取一整个 partition 的数据，如果 sector 极其分散的分布到不同的地方，通过公网读取，则不是一个可执行的方案。

    后来我们通过数次的设计与修改，最终产生了现在的方案，就是分布式矿池。分布式矿池并非体现在单一存储提供者，而是将分布式的概念体现在多存储提供者的管理，这更像一个存储提供者联合体。

    Venus 分布式矿池在外部的体现和传统的分布式矿池是相似的。在存储资源上体现在地域分布性，只要有网络可以访问的地方，都可以使节点接入到 Venus 矿池；在出块的角度上，因为 Filecoin 按算力比例来计算出块机率，所以分散的计算和整体的计算的最终结果应该是相同：n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p，这在算法的基础上提供了理论基础。

    在真实数据存储检索上，存储提供者可以通过 venus 统一入口接入网络或者自主接入。设计中，venus 会在获得存储提供者允许的条件下，按照数据的访问需求来选择合适的节点存储数据，使得数据更贴近真实的使用场景。

    1. 数据存储：支持组件共享，存储会逐渐迁移到 MySQL，通过一些高可用的方案保证 Venus 的元数据安全。
    2. 共享组件：支持高可用，保证服务的质量，减少存储提供者的时间成本与维护成本，这使得存储提供者能够更容易加入到矿池生态中。现在的挖矿活动专业性很强，而实现 Filecoin 利用闲散存储资源的梦想则不可避免需要降低参与门槛，才能吸引更多的参与者进来。
    3. 聚集出块权：存储提供者能够将资源整合在一起，互相帮助打包消息，这样可以避免小存储提供者的消息无人打包的困境。
    4. 提升 Filecoin 网络的吞吐量：如果同一高度存在多个区块，venus-miner 能够保证每个区块中的消息都是不同的，而如果各自出块，消息则很可能大量重复。
    5. 提升消息的稳定性：挖矿活动中的消息可以和节点分开，由 venus-messager 来管理，venus-messager 会跟踪链的最新状态来设置一个相对合理的预估的 gas 参数，同时也支持用户自己设置一个消息参数。
    6. 提升数据访问速度：目前的 Filecoin 网络更多的还是存储，但是作为一个存储服务，最终需要对外输出检索服务才能实现根本价值。如果有足够多的存储提供者使用 Venus，那么 Venus 在真实数据的处理上就有更多的可能，比如数据的分布，Venus 可以将数据分布到距离客户最近的一些存储提供者节点，这样可以提高客户的访问速度；比如一些公有数据可以把这些数据尽可能的分散到更多的节点上，保障在任意位置的访问都有效，这可以大大提升 IPFS 网络的效能，进一步实现 IPFS Web3.0 的梦想。

    # venus 如何工作

    Venus 是 Filecoin 的通用实现之一，致力于分布式的集群架构及更简洁的职责划分。

    Venus 分布式存储池在外部的呈现和传统的分布式矿池是相似的。在存储资源上体现在地域分布性，只要有网络可以访问的地方，都可以使节点接入到 Venus 矿池。

    # venus

    venus (opens new window) 类似 lotus-daemon，用于实现全节点。venus 接入 Filecoin 区块链网络，为 Venus 提供数据支持。可以把 venus 当作普通节点来使用，它具有区块链节点必备的所有功能，如 chain、mpool、wallet。venus 的接口和 lotus 基本兼容（如果存在不兼容的接口，欢迎发布 Issue），你可以在 venus 上创建私钥、查询资产、转账等等。在典型部署环境里，venus 仅仅提供基础链上数据查询服务，本身不保存私钥。slashfilter 所需要的区块数据，存储到数据库里，节点本身是无状态的，这样通过 nginx 反向代理后就可以实现 venus 节点的高可用。

    venus 节点自身有一些区别与 lotus 的地方：

    1. 创建区块的接口中支持了外部签名（后续会向 Lotus 提 PR）
    2. 消息选择的接口支持同时选择多个批次的消息，用于多存储提供者出块时选择消息。
    3. 支持 sophon-auth 的的中心访问授权

    因此如果对 Venus/Lotus 混合部署感兴趣，需要使用我们维护的 lotus 兼容 venus 的项目 (opens new window)，可自行 pick 代码编译。

    # sophon-auth

    sophon-auth (opens new window) (原 venus-auth) 是用于授权的组件，在典型的部署环境下 sophon-auth 用于给 venus、sophon-miner、sophon-messager 提供授权服务，每个本地的节点访问共享组件都要经过授权，后续会在这个基础上进行功能扩充，做一些安全方面的控制，比如访问限流、黑名单。

    # sophon-miner

    sophon-miner (opens new window) (原 venus-miner) 的作用是聚集出块权，可以为接入链服务的多个集群执行出块逻辑。sophon-miner 有以下特点：

    1. 分离数据：由于生成区块的过程需要访问数据，并且存储提供者的 sealer 可能是异构的，但目前多数存储提供者会使用自己定制的代码，那么要实现联合挖矿就存在如何访问到这些数据的问题。通过隔断 sophon-miner 对存储组织方式的依赖，通过让证明在存储提供者侧完成，无论存储提供者的 sealer 如何组织存储，只要实现了ComputeProof接口，sophon-miner 就可以通过这个接口来生成证明。
    2. 分离私钥：计算随机数及签名区块的过程中，所有涉及到私钥的操作都通过远程钱包的方式来访问，这样既无泄漏集群私钥，又能保证出块逻辑正常运行。
    3. 提高网络 TPS：当 sophon-miner 负责的存储提供者在一个周期获得多个（>1）出块权，sophon-miner 会尽量从消息池中选择不同的消息进行打包，这样一定程度上可以提升消息上链的速度，同时使该出块可能获得更多的小费奖励（Premium）。
    4. 收益稳定性：多存储提供者联合挖矿配套奖励池分配系统可以让小存储提供者每天都能获得区块奖励，也可以减少某些存储提供者偶发性出块错误造成的损失。

    # sophon-messager

    sophon-messager (opens new window) (原 venus-messager) 组件的目标是更好的帮助消息上链，并能够灵活的控制消息上链的时机，减少 gas 消耗，流量控制等。其中包括远程钱包管理、地址管理、消息管理。

    1. 地址管理：主要是管理 nonce 值，保证 nonce 值能够按照正确的顺序分配。
    2. 消息管理：消息管理分成三个部分，分别是“消息接收和保存”、“消息选择及推送”“消息上链状态的追踪”。
    3. GasFee 管理：可以按地址分别设置 gasLimit 的系数和 maxFee。

    从功能性上来说：

    1. 远程钱包支持：一个 sophon-messager 支持多个钱包，分别管理自己的 message。
    2. 支持 sqlite 本地存储和 mysql 远程存储：存储更加安全稳定。
    3. 动态填充：根据 gas 和 push 策略，在链上发送消息时，需要填写 gas 相关参数和 nonce，以确保 gas 估算和其他设置有效。
    4. 维护消息状态：包括消息是否被链接和替换，保存执行结果。
    5. 多点消息传递（通过 Mpool API 推送到多个节点）：确保消息在网络上传播。
    6. 灵活配置：包括 gas 估算、消息推送策略等。

    # venus-wallet

    venus-wallet (opens new window) 是一个远程钱包，协议上能够同时支持 lotus 和 venus。在典型的部署环境中，这个组件由存储提供者部署在本地，并通过一定的策略配置保证资产的安全。venus-wallet 有以下功能特点：

    1. 私钥管理模块：目前支持非对称算法 BLS 和 SECP 的私钥管理，能够生成随机私钥，并运用 aes128 对私钥进行对称加密存储，同时支持私钥对数据进行签名。
    2. 签名验证：每种签名类型都有对应验证策略，保证了签名方不能在签名类型上欺骗钱包。
    3. 签名策略模块：针对 Filecoin 的 Lotus 及 Venus 实现，对存在的数 10 种数据结构以及 message 数据结构中的 60 余种签名类型进行统一管理，按需配置各种组合方式绑定私钥签名规则，而后可以将数种不同的私钥签名规则组成一个整体，授权于外部组件使用。

    # droplet

    droplet (opens new window) (原 venus-market) 是 Venus 系统中的市场组件。其愿景是打造 Filecoin 网络中分布式的存储和检索市场。目前已经实现了兼容 Lotus 协议的订单存储和检索，逐渐向着 droplet 服务多个集群的接单，对外提供统一的检索服务方向发展。可参见droplet 设计与路线图 (opens new window)

    # sophon-gateway

    sophon-gateway (opens new window) (原 venus-gateway) 是独立组件与链服务层的桥梁，用于简化部署并降低存储提供者访问的复杂性、增加存储提供者访问的安全性。独立组件启动时将其服务接口注册到 sophon-gateway，链服务组件需要时通过 sophon-gateway 请求对应集群的服务接口。

    • 存储提供者不需要外部 IP 和曝露钱包服务；
    • 存储池配置 SSL 证书后，集群与存储池的连接是安全的；
    • 存储提供者可以简单地将多个客户端（钱包/证明）注册到存储池以获得高可用性。

    sophon-gateway

    # damocles

    damocles (opens new window) (原 venus-cluster) 是 Venus 推出的新版本扇区封装、算力维持组件，相对于原本的 venus-sealer，在任务调度、最大化系统资源方面有一定优势，其面向的用户受众也将有所不同。

    +

    # 前言

    在同一条区块链上需要具有多个互操作的软件实现，每个实现都有自己的安全问题集，但是所有实现不尽相同，因此，启动具有多种实现方式的加密货币网络可降低发生灾难性错误的可能性，Venus 正是 Filecoin 的实现之一。

    Venus 代指 Filecoin 的通用实现之一，venus 则代指 Venus 的组件之一。Venus 致力于帮助中小存储提供者能够更加简单的加入到 Filecoin 生态网络建设中。

    目前 Venus 通过 venus、damocles、sophon-miner、venus-wallet、sophon-messager、sophon-auth、sophon-gateway 组件，已经实现了 Filecoin 分布式矿池的支持，未来，Venus 将持续完善自身，并共同推进开源的 Filecoin 开发与生态的发展。

    # 为什么我们要这样做

    2020 年 6 月，Protocol Lab 发起了关于由社区后续维护 go-filecoin 的 RFP，IPFSForce 随后申请并获得了维护权。10 月，go-filecoin 更名为 Venus，我们继续推进对 Venus 项目的维护工作。

    在重新保持维护之前，Venus 是一个严重缺乏维护的项目。协议和组件上，vm/mpool/chain/rpc 虽然都有了，但是全都存在不同程度的问题，我们用了三个多月的时间，逐渐修复很多协议层、代码层，、性能的问题，使得 Venus 完成了与 Lotus 的互操作，让使用 Venus 的节点可以正常的在网络上运行。后续我们又逐渐的让 Venus 支持了 Calibration、2k 网络。

    完成以上工作后，我们着手于 Venus 的开发方向。

    我们的设计是让 Venus 向矿池的发展角度去支持，最初的设计是从“如何扩展单一存储提供者”思考，这个方向存在理论上的可行性，但是最大的问题在于 Filecoin 独特的证明机制。因为 Filecoin 网络的存储提供者必须周期性的提交‘时空证明’，而为了生成证明，存储提供者必须读取一整个 partition 的数据，如果 sector 极其分散的分布到不同的地方，通过公网读取，则不是一个可执行的方案。

    后来我们通过数次的设计与修改，最终产生了现在的方案，就是分布式矿池。分布式矿池并非体现在单一存储提供者，而是将分布式的概念体现在多存储提供者的管理，这更像一个存储提供者联合体。

    Venus 分布式矿池在外部的体现和传统的分布式矿池是相似的。在存储资源上体现在地域分布性，只要有网络可以访问的地方，都可以使节点接入到 Venus 矿池；在出块的角度上，因为 Filecoin 按算力比例来计算出块机率，所以分散的计算和整体的计算的最终结果应该是相同：n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p，这在算法的基础上提供了理论基础。

    在真实数据存储检索上，存储提供者可以通过 venus 统一入口接入网络或者自主接入。设计中，venus 会在获得存储提供者允许的条件下，按照数据的访问需求来选择合适的节点存储数据，使得数据更贴近真实的使用场景。

    1. 数据存储：支持组件共享，存储会逐渐迁移到 MySQL，通过一些高可用的方案保证 Venus 的元数据安全。
    2. 共享组件：支持高可用，保证服务的质量，减少存储提供者的时间成本与维护成本，这使得存储提供者能够更容易加入到矿池生态中。现在的挖矿活动专业性很强，而实现 Filecoin 利用闲散存储资源的梦想则不可避免需要降低参与门槛，才能吸引更多的参与者进来。
    3. 聚集出块权：存储提供者能够将资源整合在一起，互相帮助打包消息，这样可以避免小存储提供者的消息无人打包的困境。
    4. 提升 Filecoin 网络的吞吐量：如果同一高度存在多个区块，venus-miner 能够保证每个区块中的消息都是不同的，而如果各自出块，消息则很可能大量重复。
    5. 提升消息的稳定性：挖矿活动中的消息可以和节点分开，由 venus-messager 来管理，venus-messager 会跟踪链的最新状态来设置一个相对合理的预估的 gas 参数，同时也支持用户自己设置一个消息参数。
    6. 提升数据访问速度：目前的 Filecoin 网络更多的还是存储，但是作为一个存储服务，最终需要对外输出检索服务才能实现根本价值。如果有足够多的存储提供者使用 Venus，那么 Venus 在真实数据的处理上就有更多的可能，比如数据的分布，Venus 可以将数据分布到距离客户最近的一些存储提供者节点，这样可以提高客户的访问速度；比如一些公有数据可以把这些数据尽可能的分散到更多的节点上，保障在任意位置的访问都有效，这可以大大提升 IPFS 网络的效能，进一步实现 IPFS Web3.0 的梦想。

    # venus 如何工作

    Venus 是 Filecoin 的通用实现之一，致力于分布式的集群架构及更简洁的职责划分。

    Venus 分布式存储池在外部的呈现和传统的分布式矿池是相似的。在存储资源上体现在地域分布性，只要有网络可以访问的地方，都可以使节点接入到 Venus 矿池。

    # venus

    venus (opens new window) 类似 lotus-daemon，用于实现全节点。venus 接入 Filecoin 区块链网络，为 Venus 提供数据支持。可以把 venus 当作普通节点来使用，它具有区块链节点必备的所有功能，如 chain、mpool、wallet。venus 的接口和 lotus 基本兼容（如果存在不兼容的接口，欢迎发布 Issue），你可以在 venus 上创建私钥、查询资产、转账等等。在典型部署环境里，venus 仅仅提供基础链上数据查询服务，本身不保存私钥。slashfilter 所需要的区块数据，存储到数据库里，节点本身是无状态的，这样通过 nginx 反向代理后就可以实现 venus 节点的高可用。

    venus 节点自身有一些区别与 lotus 的地方：

    1. 创建区块的接口中支持了外部签名（后续会向 Lotus 提 PR）
    2. 消息选择的接口支持同时选择多个批次的消息，用于多存储提供者出块时选择消息。
    3. 支持 sophon-auth 的的中心访问授权

    因此如果对 Venus/Lotus 混合部署感兴趣，需要使用我们维护的 lotus 兼容 venus 的项目 (opens new window)，可自行 pick 代码编译。

    # sophon-auth

    sophon-auth (opens new window) (原 venus-auth) 是用于授权的组件，在典型的部署环境下 sophon-auth 用于给 venus、sophon-miner、sophon-messager 提供授权服务，每个本地的节点访问共享组件都要经过授权，后续会在这个基础上进行功能扩充，做一些安全方面的控制，比如访问限流、黑名单。

    # sophon-miner

    sophon-miner (opens new window) (原 venus-miner) 的作用是聚集出块权，可以为接入链服务的多个集群执行出块逻辑。sophon-miner 有以下特点：

    1. 分离数据：由于生成区块的过程需要访问数据，并且存储提供者的 sealer 可能是异构的，但目前多数存储提供者会使用自己定制的代码，那么要实现联合挖矿就存在如何访问到这些数据的问题。通过隔断 sophon-miner 对存储组织方式的依赖，通过让证明在存储提供者侧完成，无论存储提供者的 sealer 如何组织存储，只要实现了ComputeProof接口，sophon-miner 就可以通过这个接口来生成证明。
    2. 分离私钥：计算随机数及签名区块的过程中，所有涉及到私钥的操作都通过远程钱包的方式来访问，这样既无泄漏集群私钥，又能保证出块逻辑正常运行。
    3. 提高网络 TPS：当 sophon-miner 负责的存储提供者在一个周期获得多个（>1）出块权，sophon-miner 会尽量从消息池中选择不同的消息进行打包，这样一定程度上可以提升消息上链的速度，同时使该出块可能获得更多的小费奖励（Premium）。
    4. 收益稳定性：多存储提供者联合挖矿配套奖励池分配系统可以让小存储提供者每天都能获得区块奖励，也可以减少某些存储提供者偶发性出块错误造成的损失。

    # sophon-messager

    sophon-messager (opens new window) (原 venus-messager) 组件的目标是更好的帮助消息上链，并能够灵活的控制消息上链的时机，减少 gas 消耗，流量控制等。其中包括远程钱包管理、地址管理、消息管理。

    1. 地址管理：主要是管理 nonce 值，保证 nonce 值能够按照正确的顺序分配。
    2. 消息管理：消息管理分成三个部分，分别是“消息接收和保存”、“消息选择及推送”“消息上链状态的追踪”。
    3. GasFee 管理：可以按地址分别设置 gasLimit 的系数和 maxFee。

    从功能性上来说：

    1. 远程钱包支持：一个 sophon-messager 支持多个钱包，分别管理自己的 message。
    2. 支持 sqlite 本地存储和 mysql 远程存储：存储更加安全稳定。
    3. 动态填充：根据 gas 和 push 策略，在链上发送消息时，需要填写 gas 相关参数和 nonce，以确保 gas 估算和其他设置有效。
    4. 维护消息状态：包括消息是否被链接和替换，保存执行结果。
    5. 多点消息传递（通过 Mpool API 推送到多个节点）：确保消息在网络上传播。
    6. 灵活配置：包括 gas 估算、消息推送策略等。

    # venus-wallet

    venus-wallet (opens new window) 是一个远程钱包，协议上能够同时支持 lotus 和 venus。在典型的部署环境中，这个组件由存储提供者部署在本地，并通过一定的策略配置保证资产的安全。venus-wallet 有以下功能特点：

    1. 私钥管理模块：目前支持非对称算法 BLS 和 SECP 的私钥管理，能够生成随机私钥，并运用 aes128 对私钥进行对称加密存储，同时支持私钥对数据进行签名。
    2. 签名验证：每种签名类型都有对应验证策略，保证了签名方不能在签名类型上欺骗钱包。
    3. 签名策略模块：针对 Filecoin 的 Lotus 及 Venus 实现，对存在的数 10 种数据结构以及 message 数据结构中的 60 余种签名类型进行统一管理，按需配置各种组合方式绑定私钥签名规则，而后可以将数种不同的私钥签名规则组成一个整体，授权于外部组件使用。

    # droplet

    droplet (opens new window) (原 venus-market) 是 Venus 系统中的市场组件。其愿景是打造 Filecoin 网络中分布式的存储和检索市场。目前已经实现了兼容 Lotus 协议的订单存储和检索，逐渐向着 droplet 服务多个集群的接单，对外提供统一的检索服务方向发展。可参见droplet 设计与路线图 (opens new window)

    # sophon-gateway

    sophon-gateway (opens new window) (原 venus-gateway) 是独立组件与链服务层的桥梁，用于简化部署并降低存储提供者访问的复杂性、增加存储提供者访问的安全性。独立组件启动时将其服务接口注册到 sophon-gateway，链服务组件需要时通过 sophon-gateway 请求对应集群的服务接口。

    • 存储提供者不需要外部 IP 和曝露钱包服务；
    • 存储池配置 SSL 证书后，集群与存储池的连接是安全的；
    • 存储提供者可以简单地将多个客户端（钱包/证明）注册到存储池以获得高可用性。

    sophon-gateway

    # damocles

    damocles (opens new window) (原 venus-cluster) 是 Venus 推出的新版本扇区封装、算力维持组件，相对于原本的 venus-sealer，在任务调度、最大化系统资源方面有一定优势，其面向的用户受众也将有所不同。

    单页介绍文档 →

    - + diff --git a/zh/intro/one-pager.html b/zh/intro/one-pager.html index a4dc0298d..7e7ed06d3 100644 --- a/zh/intro/one-pager.html +++ b/zh/intro/one-pager.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • venus-cluster

    +

    venus-cluster

    ← →

    - + diff --git a/zh/intro/sophon.html b/zh/intro/sophon.html index 9ab8aa664..c596b30e6 100644 --- a/zh/intro/sophon.html +++ b/zh/intro/sophon.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • sophon

    # 智子

    智子，原 Venus 链服务，是一个 Filecoin 超级节点解决方案。请在此 (opens new window)了解更多关于智子的信息。

    - +

    sophon

    # 智子

    智子，原 Venus 链服务，是一个 Filecoin 超级节点解决方案。请在此 (opens new window)了解更多关于智子的信息。

    + diff --git a/zh/operation/Efficiency_of_sealing.html b/zh/operation/Efficiency_of_sealing.html index 8490d2cbe..05b0c5293 100644 --- a/zh/operation/Efficiency_of_sealing.html +++ b/zh/operation/Efficiency_of_sealing.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -200,7 +200,7 @@ MaxSealingSectors = 7 # 修改为 7 MaxSealingSectorsForDeals = 0

    此时我们可以通过一个简单的定时脚本就可以做到，始终维持最佳的任务量了

    # 损失和止损

      如果一个任务执行错误之后又被反复的重试，这就像我们有 7 个通道进行算力的封装，但是此时有一通道阻塞或者损坏，这就会降低我们 1 / 7 的产量，所以及时的处理错误也是非常重要的

    • 何种情况下应该立刻抛弃任务

      1. ticket 过期
      2. Commit 过期
      3. 依赖文件损坏重试多次都未成功时;

    • 移除无法完成的 sector

    venus-sealer sectors remove --really-do-it <sectorNum>
-

    如遇到无法彻底删除请查询：顽固扇区如何删除 (opens new window)

    - +

    如遇到无法彻底删除请查询：顽固扇区如何删除 (opens new window)

    + diff --git a/zh/operation/Independent_com_access_analysis.html b/zh/operation/Independent_com_access_analysis.html index 267ba37e7..4a210e159 100644 --- a/zh/operation/Independent_com_access_analysis.html +++ b/zh/operation/Independent_com_access_analysis.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -63,7 +63,7 @@ INFO filecoin_proofs::caches > trying parameters memory cache for: STACKED[34359738368] INFO filecoin_proofs::caches > no params in memory cache for STACKED[34359738368] INFO storage_proofs_core::parameter_cache > parameter set identifier for cache: layered_drgporep::PublicParams{ graph: stacked_graph::StackedGraph{expansion_degree: 8 base_graph -
    - +
    + diff --git a/zh/operation/Sealing_deploy_plan_1.html b/zh/operation/Sealing_deploy_plan_1.html index aa3d6cb21..fe179c670 100644 --- a/zh/operation/Sealing_deploy_plan_1.html +++ b/zh/operation/Sealing_deploy_plan_1.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -100,7 +100,7 @@ # 指定worker02的seal路径与worker01相同，这样做的好处是不需要文件的拷贝。 ./venus-worker storage attach --seal <ABSOLUTE_LOCAL_PATH>

    TRUST_PARAMS=1 环境变量可以跳过校验证明参数文件，如果你确定参数文件都在且是正确的可以用此环境变量用加快 venus-sealer 或 venus-worker 的启动的速度；

    seal 要求较高的磁盘吞吐量，建议 ssd 盘。

       (1024G-112G)/128G=7.125，保险起见我们可以先并发 6 个观察一段时间资源使用率。

       确定了并发密封扇区个数后，就可以确定 seal 需要的磁盘空间= 6*1t=6t.

    做策略的思路：先考虑内存，确定并发数，在补充其他资源，如临时磁盘空间，至于 cpu，如果不足，可以限额，这样做的好处是系统可以持续运行，而不被 oom。

    可以利用 gpu 加速的任务时 P2，C2 和 windowPoSt，分配 gpu 的顺序是：wdPoSt>C2>P2

    - +   ./venus-sealer sectors pledge 发送一个密封任务，通常写一个定时脚本或系统事务，每隔一段时间发送一个 sector 任务；配置文件 MaxSealingSectors 控制同时进行的 sector 上限数。
    + diff --git a/zh/operation/Sealing_deploy_plan_2.html b/zh/operation/Sealing_deploy_plan_2.html index 68b41a234..3a86e8e2c 100644 --- a/zh/operation/Sealing_deploy_plan_2.html +++ b/zh/operation/Sealing_deploy_plan_2.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -90,7 +90,7 @@ # 加入进程的PID sudo echo <PID> > /sys/fs/cgroup/cpuset/worker/cgroup.procs -

    PID: 进程 ID 号;

    每次 worker 重启后 PID 会变化，需要更新文件。

    /sys/fs/cgroup/cpuset是系统目录,worker是自己创建的.

    - +

    PID: 进程 ID 号;

    每次 worker 重启后 PID 会变化，需要更新文件。

    /sys/fs/cgroup/cpuset是系统目录,worker是自己创建的.

    + diff --git a/zh/operation/System_monitor_of_Zabbix.html b/zh/operation/System_monitor_of_Zabbix.html index bef6e9c7d..e29d70f29 100644 --- a/zh/operation/System_monitor_of_Zabbix.html +++ b/zh/operation/System_monitor_of_Zabbix.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -116,7 +116,7 @@

    4、添加 zabbix-agent 主机

    5、查看 zabbix 监控机器的内存图

    6、异常报警，需要处理的机器 -

    - +

    + diff --git a/zh/operation/_Footer.html b/zh/operation/_Footer.html index df7c07f14..cd164e72c 100644 --- a/zh/operation/_Footer.html +++ b/zh/operation/_Footer.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    - +

    See something missing? Have tips to share? File an issue (opens new window), and we'll follow up as soon as possible. (If you have write permission in this repo, feel free to edit directly.)

    + diff --git a/zh/operation/example-single-box.html b/zh/operation/example-single-box.html index c230e87da..a0b9d5625 100644 --- a/zh/operation/example-single-box.html +++ b/zh/operation/example-single-box.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # venus 集群日增算力 1T 机器选型方案

    # 机器配置

    资源 配置
    CPU 3970X * 1 (32c)
    内存 512G
    硬盘 3T/SSD
    网卡 千兆
    系统盘 500G
    显卡 3080 * 1

    台数:1 台

    # 任务配比

    任务分为 AP,P1,P2,Commit 阶段

    运行方式 核数限制 耗时 (分钟) 内存消耗 (G) 效率 (个/小时) 日产量 (T)
    P1 * 5 20 220 376 1.3636 1.0227
    P2,AP,Commit 12 10 120 3 1.125

    关于限核，配置执行任务类型，并发任务数等请参考 venus-docs 项目中相关文档。

    - +

    # venus 集群日增算力 1T 机器选型方案

    # 机器配置

    资源 配置
    CPU 3970X * 1 (32c)
    内存 512G
    硬盘 3T/SSD
    网卡 千兆
    系统盘 500G
    显卡 3080 * 1

    台数:1 台

    # 任务配比

    任务分为 AP,P1,P2,Commit 阶段

    运行方式 核数限制 耗时 (分钟) 内存消耗 (G) 效率 (个/小时) 日产量 (T)
    P1 * 5 20 220 376 1.3636 1.0227
    P2,AP,Commit 12 10 120 3 1.125

    关于限核，配置执行任务类型，并发任务数等请参考 venus-docs 项目中相关文档。

    + diff --git a/zh/operation/index.html b/zh/operation/index.html index 1fb30950e..c295b4f4d 100644 --- a/zh/operation/index.html +++ b/zh/operation/index.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,11 +37,11 @@ English
  • 简体中文 -

    • # 部署Venus解决方案

    Venus泛指一系列与filecoin协议稳定/高效互动的软件产品。Venus的，目标群体大致分为4类。SP存储提供者，SC存储客户，生态合作伙伴，以及去中心化应用Dapp。Venus解决方案当前被广泛应用于SP和SC的场景中。

    # 部署

    经过Venus在 2022 年底的品牌重塑 (opens new window)之后，Venus拆分出 3 个产品，分别是智子 (opens new window)，执剑人 (opens new window)以及水滴 (opens new window)。关于各产品的具体部署流程，请参见各产品的文档。

    # 架构

    +

    # 部署Venus解决方案

    Venus泛指一系列与filecoin协议稳定/高效互动的软件产品。Venus的，目标群体大致分为4类。SP存储提供者，SC存储客户，生态合作伙伴，以及去中心化应用Dapp。Venus解决方案当前被广泛应用于SP和SC的场景中。

    # 部署

    经过Venus在 2022 年底的品牌重塑 (opens new window)之后，Venus拆分出 3 个产品，分别是智子 (opens new window)，执剑人 (opens new window)以及水滴 (opens new window)。关于各产品的具体部署流程，请参见各产品的文档。

    # 架构

    nv22网络升级 →

    - + diff --git a/zh/operation/lotus-vs-venus.html b/zh/operation/lotus-vs-venus.html index 8efde5f1e..46371b9af 100644 --- a/zh/operation/lotus-vs-venus.html +++ b/zh/operation/lotus-vs-venus.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,7 +37,7 @@ English
  • 简体中文 -

    • # 从 Lotus 来的命令

    很多日常的命令包括但不限于创建worker/controler地址 (opens new window)，设置不同的配置 (opens new window)，或者修改存储路径 (opens new window)等等，都同时适用于Lotus和Venus。节点运维工程师可以按照 Lotus 文档中的步骤来操作。如果遇到任何问题，欢迎到#fil-venus-cn (opens new window)来提出问题。

    - +

    # 从 Lotus 来的命令

    很多日常的命令包括但不限于创建worker/controler地址 (opens new window)，设置不同的配置 (opens new window)，或者修改存储路径 (opens new window)等等，都同时适用于Lotus和Venus。节点运维工程师可以按照 Lotus 文档中的步骤来操作。如果遇到任何问题，欢迎到#fil-venus-cn (opens new window)来提出问题。

    + diff --git a/zh/operation/migrate_market_v1_to_v2.html b/zh/operation/migrate_market_v1_to_v2.html index 19169dcf2..cdbc7cff0 100644 --- a/zh/operation/migrate_market_v1_to_v2.html +++ b/zh/operation/migrate_market_v1_to_v2.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -45,11 +45,11 @@ go build

    执行上述步骤后会生成一个工具，这个工具用于导出 v1 版本的数据

    # 升级步骤

    1. 停止 venus-market 程序

    2. 备份 venus-market 数据目录，这个目录默认保存在 ~/.venusmarket.

    3. 导出 v1 版本的数据

       ./market_export --repo <venus-market repo> export <path of export data file>

    4. 重新初始化 v2 版本的 venus-market(版本号必须高于 2.0.0 rc2)

    5. 执行 v2 版本的升级命令，这个命令用于导入步骤 3 中导出的数据。

      ./market_export --repo <venus-market repo> migrate import_v1 <path of export data file>
-

    稳妥起见，做升级之前请确保没有处于 (Publish/Publishing/StorageDealAwaitingPreCommit) 状态的订单

    +

    稳妥起见，做升级之前请确保没有处于 (Publish/Publishing/StorageDealAwaitingPreCommit) 状态的订单

    ←

    - + diff --git a/zh/operation/nv15-upgrade.html b/zh/operation/nv15-upgrade.html index 2ed3dbfe0..4cc04a9ed 100644 --- a/zh/operation/nv15-upgrade.html +++ b/zh/operation/nv15-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -73,7 +73,7 @@ Tag：v1.4.0 影响功能：无

  • venus-market：可选择升级 分支：v2.0.0 -影响功能 新版本

    • # 升级顺序

    1. venus-wallet Tag:v1.4.0
    2. venus v1.2.0
    3. lotus for venuspool venus/v1.14.0
    4. chain-co v0.1.0
    5. venus-messager v1.4.0
    6. venus-gateway v1.2.0
    7. venus-miner Tag:v1.4.0
    8. venus-market v2.0.0
    9. venus-sealer v1.4.0

    # 升级建议

    1. 对于还有证明空窗期的用户，选择一个安全的时间来升级。
    2. 对于已经不具备空窗期的用户，最好的办法是在建立一个环境来进行过度。
    3. 建议运行一个备用的兼容版本 lotus 用于备份。

    有任何关于升级的问题可以到 disscusion 讨论：https://github.com/filecoin-project/venus/discussions/4688

    +影响功能 新版本

    # 升级顺序

    1. venus-wallet Tag:v1.4.0
    2. venus v1.2.0
    3. lotus for venuspool venus/v1.14.0
    4. chain-co v0.1.0
    5. venus-messager v1.4.0
    6. venus-gateway v1.2.0
    7. venus-miner Tag:v1.4.0
    8. venus-market v2.0.0
    9. venus-sealer v1.4.0

    # 升级建议

    1. 对于还有证明空窗期的用户，选择一个安全的时间来升级。
    2. 对于已经不具备空窗期的用户，最好的办法是在建立一个环境来进行过度。
    3. 建议运行一个备用的兼容版本 lotus 用于备份。

    有任何关于升级的问题可以到 disscusion 讨论：https://github.com/filecoin-project/venus/discussions/4688

    ← →

    - + diff --git a/zh/operation/nv16-upgrade.html b/zh/operation/nv16-upgrade.html index 879609132..a0d48a176 100644 --- a/zh/operation/nv16-upgrade.html +++ b/zh/operation/nv16-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -60,7 +60,7 @@ init bafk2bzaceaipvjhoxmtofsnv3aj6gj5ida4afdrxa4ewku2hfipdlxpaektlw storagepower bafk2bzacebjvqva6ppvysn5xpmiqcdfelwbbcxmghx5ww6hr37cgred6dyrpm verifiedregistry bafk2bzaceb3zbkjz3auizmoln2unmxep7dyfcmsre64vnqfhdyh7rkqfoxlw4 -

  • 主网可以通过设置环境变量 export VENUS_USE_FVM_TO_SYNC_MAINNET_V15=1 在 nv15 网络使用 fvm

  • 若不排查问题，rust 日志级别不建议设置为 trace，因为会打印较多日志

  • 升级后可以通过命令来 ./venus state get-actor t01000 来确认是否升级成功

    • # venus-messager

    tag:v1.6.0

    影响功能：支持新的网络版本，新增主目录，默认在 ~/.venus-messager

    依赖升级组件：

    注意事项：

    1. 升级后是否生成主目录 ~/.venus-messager

    2. 升级后主目录应包含 config.toml 和 tipset.json，config.toml 应与启动 messager 使用的配置文件内容一致，~/.venus-messager/tipset.json 是由当前目录中的 tipset.json 拷贝而来

    3. 升级成功后再次重启是读取的配置是~/.venus-messager/config.toml

    4. 能否正常收到消息和推送消息到节点

    # venus-miner

    tag: v1.6.0

    影响功能：

    1. 获取 beacon 的接口名字 由 BeaconGetEntry 改为 StateGetBeaconEntry

    依赖升级组件：venus,venus-auth,venus-gateway

    注意事项：

    1. 升级后常用命令 address state/list/update验证一遍.
    2. 如果用 mysql 数据库，检查下 miner_blocks 表中 parent_key 字段是 varchar(1000)

    # venus-gateway

    tag: v1.6.0

    影响功能：修复没有自动清理超时的请求

    注意事项：

    1. 升级后 wallet 是否重新注册上来

    # venus-market

    tag: v2.2.0

    影响功能：

    注意事项：

    # venus-wallet

    # 社区

    tag: v1.6.0

    影响功能：

    注意事项：

    1. 需要解锁钱包
    2. 是否注册到 gateway

    +

  • 主网可以通过设置环境变量 export VENUS_USE_FVM_TO_SYNC_MAINNET_V15=1 在 nv15 网络使用 fvm

  • 若不排查问题，rust 日志级别不建议设置为 trace，因为会打印较多日志

  • 升级后可以通过命令来 ./venus state get-actor t01000 来确认是否升级成功

    • # venus-messager

    tag:v1.6.0

    影响功能：支持新的网络版本，新增主目录，默认在 ~/.venus-messager

    依赖升级组件：

    注意事项：

    1. 升级后是否生成主目录 ~/.venus-messager

    2. 升级后主目录应包含 config.toml 和 tipset.json，config.toml 应与启动 messager 使用的配置文件内容一致，~/.venus-messager/tipset.json 是由当前目录中的 tipset.json 拷贝而来

    3. 升级成功后再次重启是读取的配置是~/.venus-messager/config.toml

    4. 能否正常收到消息和推送消息到节点

    # venus-miner

    tag: v1.6.0

    影响功能：

    1. 获取 beacon 的接口名字 由 BeaconGetEntry 改为 StateGetBeaconEntry

    依赖升级组件：venus,venus-auth,venus-gateway

    注意事项：

    1. 升级后常用命令 address state/list/update验证一遍.
    2. 如果用 mysql 数据库，检查下 miner_blocks 表中 parent_key 字段是 varchar(1000)

    # venus-gateway

    tag: v1.6.0

    影响功能：修复没有自动清理超时的请求

    注意事项：

    1. 升级后 wallet 是否重新注册上来

    # venus-market

    tag: v2.2.0

    影响功能：

    注意事项：

    # venus-wallet

    # 社区

    tag: v1.6.0

    影响功能：

    注意事项：

    1. 需要解锁钱包
    2. 是否注册到 gateway

    ← →

    - + diff --git a/zh/operation/nv17-upgrade.html b/zh/operation/nv17-upgrade.html index 00ee268e6..08c4af878 100644 --- a/zh/operation/nv17-upgrade.html +++ b/zh/operation/nv17-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -60,7 +60,7 @@ cron bafk2bzacebcec3lffmos3nawm5cvwehssxeqwxixoyyfvejy7viszzsxzyu26 init bafk2bzacebtdq4zyuxk2fzbdkva6kc4mx75mkbfmldplfntayhbl5wkqou33i storageminer bafk2bzacedyux5hlrildwutvvjdcsvjtwsoc5xnqdjl73ouiukgklekeuyfl4 -

  • 若不排查问题，rust 日志级别不建议设置为 trace，因为会打印较多日志

  • 升级后可以通过命令来 ./venus state get-actor t01000 来确认是否升级成功

    • # venus-messager

    功能：

    1. 增加对 basefee 的控制，可以对某个地址单独设置 basefee，当链上 basefee 高于限制的 basefee，消息将不会被推送出去

    依赖升级组件：

    注意事项：

    1. 升级后观察消息能否正常上链

    # venus-miner

    影响功能：

    依赖升级组件：

    注意事项：

    1. 从 1.7.*升级到v1.8.0会自动迁移配置文件，从 1.6.* 升级到v1.8.0需重新初始化repo(init)，参考 (opens new window)
    2. 升级后能否正常出块

    # venus-gateway

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    1. 升级后检查钱包：./venus-gateway wallet list
    2. 升级后检查矿工：./venus-gateway miner list

    # venus-market

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    # venus-wallet

    影响功能：

    注意事项：

    1. 启动后需要解锁钱包
    2. 是否注册到 gateway

    +

  • 若不排查问题，rust 日志级别不建议设置为 trace，因为会打印较多日志

  • 升级后可以通过命令来 ./venus state get-actor t01000 来确认是否升级成功

    • # venus-messager

    功能：

    1. 增加对 basefee 的控制，可以对某个地址单独设置 basefee，当链上 basefee 高于限制的 basefee，消息将不会被推送出去

    依赖升级组件：

    注意事项：

    1. 升级后观察消息能否正常上链

    # venus-miner

    影响功能：

    依赖升级组件：

    注意事项：

    1. 从 1.7.*升级到v1.8.0会自动迁移配置文件，从 1.6.* 升级到v1.8.0需重新初始化repo(init)，参考 (opens new window)
    2. 升级后能否正常出块

    # venus-gateway

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    1. 升级后检查钱包：./venus-gateway wallet list
    2. 升级后检查矿工：./venus-gateway miner list

    # venus-market

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    # venus-wallet

    影响功能：

    注意事项：

    1. 启动后需要解锁钱包
    2. 是否注册到 gateway

    ← →

    - + diff --git a/zh/operation/nv18-upgrade.html b/zh/operation/nv18-upgrade.html index a9d3efe76..27cc59c69 100644 --- a/zh/operation/nv18-upgrade.html +++ b/zh/operation/nv18-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -89,7 +89,7 @@ "parameters": { "allowableClockDriftSecs": 1 }, -

    # venus-auth

    影响功能：

    依赖升级组件：无

    注意事项：

    1. 命令行能否正常使用

    # venus-messager

    功能：

    1. 补充对接口权限的验证

    依赖升级组件：

    注意事项：

    1. 升级后观察能够正常收消息

    2. 升级后观察消息能否正常上链

    3. ReplacedMsg 更名为 NonceConflictMsg

    # venus-miner

    影响功能：

    依赖升级组件：

    注意事项：

    1. 升级后能否正常出块

    # venus-gateway

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    1. 升级后检查钱包：./venus-gateway wallet list
    2. 升级后检查矿工：./venus-gateway miner list

    # venus-market

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    # venus-wallet

    影响功能：

    注意事项：

    1. 启动后需要解锁钱包
    2. 是否注册到 gateway

    # venus-sector-manager

    编译：先 make dist-clean 再 make

    +

    # venus-auth

    影响功能：

    依赖升级组件：无

    注意事项：

    1. 命令行能否正常使用

    # venus-messager

    功能：

    1. 补充对接口权限的验证

    依赖升级组件：

    注意事项：

    1. 升级后观察能够正常收消息

    2. 升级后观察消息能否正常上链

    3. ReplacedMsg 更名为 NonceConflictMsg

    # venus-miner

    影响功能：

    依赖升级组件：

    注意事项：

    1. 升级后能否正常出块

    # venus-gateway

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    1. 升级后检查钱包：./venus-gateway wallet list
    2. 升级后检查矿工：./venus-gateway miner list

    # venus-market

    影响功能：

    注意事项：

    编译：先 make dist-clean 再 make

    # venus-wallet

    影响功能：

    注意事项：

    1. 启动后需要解锁钱包
    2. 是否注册到 gateway

    # venus-sector-manager

    编译：先 make dist-clean 再 make

    ← →

    - + diff --git a/zh/operation/nv19-upgrade.html b/zh/operation/nv19-upgrade.html index 439c98fc9..cdcf67810 100644 --- a/zh/operation/nv19-upgrade.html +++ b/zh/operation/nv19-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -70,7 +70,7 @@ migration 开始：STARTING migration 结束：COMPLETED migration

    # venus-gateway

    影响功能：无

    依赖升级组件：venus-auth

    注意事项：

    # venus-messager

    影响功能：

    依赖升级组件：venus, venus-auth, venus-gateway

    注意事项：

    备注：

    # venus-miner

    影响功能：

    依赖升级组件：auth, venus, gateway

    注意事项：

    # venus-market

    影响功能：

    注意事项：

    # venus-wallet

    影响功能：无

    依赖升级组件：gateway

    注意事项：

    # venus-sector-manger

    影响功能：fip-0061 wdpost 算法改动

    依赖升级组件：链服务组件

    注意事项：

    更新结果验证步骤：

    1. 程序启动正常
    2. pre/pro消息正常上链
    3. 出块正常
    4. WD 上链正常
    5. 算力增长正常
    6. 真实订单检索正常
    7. 数据库各种 gas，生命周期，聚合设置正常

    # 数据库变更

    1. venus-messager 增加对 actor 的配置及相关命令，新增 actor_cfg 表 (opens new window)

    2. venus-market storage_deals 表增加索引：CREATE INDEX idx_cdpprovider_state ON storage_deals(cdp_provider,state)

    +

    1. vsm 切换到 [fip-0061-fallback] https://github.com/ipfs-force-community/venus-cluster/tree/fip-0061-fallback 分支

    更新结果验证步骤：

    1. 程序启动正常
    2. pre/pro消息正常上链
    3. 出块正常
    4. WD 上链正常
    5. 算力增长正常
    6. 真实订单检索正常
    7. 数据库各种 gas，生命周期，聚合设置正常

    # 数据库变更

    1. venus-messager 增加对 actor 的配置及相关命令，新增 actor_cfg 表 (opens new window)

    2. venus-market storage_deals 表增加索引：CREATE INDEX idx_cdpprovider_state ON storage_deals(cdp_provider,state)

    ← →

    - + diff --git a/zh/operation/nv21-upgrade.html b/zh/operation/nv21-upgrade.html index d5757aea8..e95a4ba6e 100644 --- a/zh/operation/nv21-upgrade.html +++ b/zh/operation/nv21-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -74,7 +74,7 @@

  • 若不排查问题，rust日志级别不建议设置为 trace，因为会打印较多日志

  • 升级后可以通过命令来 ./venus state get-actor t01000 来确认是否升级成功

  • actor 迁移

    经测试本次预迁移时间在 20-30 分钟，正式迁移时间在 70 秒左右

    预迁移高度是升级高度前 180 个高度：
 pre-migration  开始：STARTING pre-migration  结束：COMPLETED pre-migration
 migration      开始：STARTING migration      结束：COMPLETED migration
-

    • # sophon-gateway

    影响功能：无

    依赖升级组件: sophon-auth

    注意事项：

    # sophon-messager

    影响功能：

    依赖升级组件: venus, sophon-auth, soohon-gateway

    注意事项：

    # sophon-miner

    影响功能：

    依赖升级组件：auth, venus, gateway

    注意事项：

    # droplet

    影响功能：

    依赖升级组件: auth, venus, gateway, messager

    注意事项：

    # venus-wallet

    影响功能： 无

    依赖升级组件: gateway

    注意事项：

    # damocles-manager

    依赖升级组件: 链服务组件

    注意事项：

    # damocles-worker

    依赖升级组件: damocles-manager

    注意事项：

    更新结果验证步骤:

    1. 程序启动正常
    2. pre/pro消息正常上链
    3. 出块正常
    4. WD上链正常
    5. 算力增长正常
    6. 真实订单检索正常
    7. 数据库各种gas，生命周期，聚合设置正常

    # 数据库变更

    1. droplet storage_deals 表增加 id 字段 ==> ALTER TABLE storage_deals ADD id varchar(128)

    +

    # sophon-gateway

    影响功能：无

    依赖升级组件: sophon-auth

    注意事项：

    # sophon-messager

    影响功能：

    依赖升级组件: venus, sophon-auth, soohon-gateway

    注意事项：

    # sophon-miner

    影响功能：

    依赖升级组件：auth, venus, gateway

    注意事项：

    # droplet

    影响功能：

    依赖升级组件: auth, venus, gateway, messager

    注意事项：

    # venus-wallet

    影响功能： 无

    依赖升级组件: gateway

    注意事项：

    # damocles-manager

    依赖升级组件: 链服务组件

    注意事项：

    # damocles-worker

    依赖升级组件: damocles-manager

    注意事项：

    更新结果验证步骤:

    1. 程序启动正常
    2. pre/pro消息正常上链
    3. 出块正常
    4. WD上链正常
    5. 算力增长正常
    6. 真实订单检索正常
    7. 数据库各种gas，生命周期，聚合设置正常

    # 数据库变更

    1. droplet storage_deals 表增加 id 字段 ==> ALTER TABLE storage_deals ADD id varchar(128)

    ← →

    - + diff --git a/zh/operation/nv22-upgrade.html b/zh/operation/nv22-upgrade.html index ae9a529ae..134f53848 100644 --- a/zh/operation/nv22-upgrade.html +++ b/zh/operation/nv22-upgrade.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -37,10 +37,10 @@ English
  • 简体中文 -

    • # Venus 各组件升级文档 (持续更新中)

    # 注意事项

    1. 所有组件全部更换
    2. 更新完通过 curl 命令调用 Version 接口检查版本号，各组件接口调用方式：https://github.com/filecoin-project/venus/issues/5132
    3. pre/pro消息上链的情况
    4. WD消息上链的情况
    5. 出块情况是否正常
    6. gas fee 相关设置是否生效

    # 需要升级的组件

    组件名 tag commit
    sophon-auth v1.15.0 a1e964b
    venus v1.15.0 aabda75
    sophon-co v0.8.0 0e48712
    sophon-messager v1.15.0 1e4f0d5
    soohon-gateway v1.15.0 541891a
    venus-wallet v1.15.0 6b3de34
    sophon-miner v1.15.0 8dd6c68
    droplet v2.11.0 44481dd
    damocles-manager v0.10.0-rc1 2f6c5f9
    damocles-worker v0.10.0-rc1 2f6c5f9

    # 升级顺序

    1. sophon-auth
    2. venus
    3. soohon-co
    4. soohon-gateway
    5. sophon-messager
    6. sophon-miner
    7. droplet
    8. venus-wallet
    9. damocles-manager
    10. damocles-worker

    # sophon-auth

    影响功能：

    • 其他组件对获取 auth 的服务

    依赖升级组件: 无

    注意事项：

    • 启动后能否正常鉴权

    # venus

    影响功能：无

    依赖升级组件: sophon-auth

    注意事项：

    编译：先 make dist-clean 再 make，这样可以防止未能正常升级 filecoin-ffi 而带来的问题

    1. 升级后检查vk文件是否完整

    2. 升级后执行命令 ./venus state network-info，然后检查通过日志检查 UpgradeDragonHeight 是否正常:

      # cali
+

    # Venus 各组件升级文档 (持续更新中)

    # 注意事项

    1. 所有组件全部更换
    2. 更新完通过 curl 命令调用 Version 接口检查版本号，各组件接口调用方式：https://github.com/filecoin-project/venus/issues/5132
    3. pre/pro消息上链的情况
    4. WD消息上链的情况
    5. 出块情况是否正常
    6. gas fee 相关设置是否生效

    # 需要升级的组件

    组件名 tag commit
    sophon-auth v1.15.0 a1e964b
    venus v1.15.1 81c99f3
    sophon-co v0.8.0 0e48712
    sophon-messager v1.15.0 1e4f0d5
    soohon-gateway v1.15.0 541891a
    venus-wallet v1.15.0 6b3de34
    sophon-miner v1.15.0 8dd6c68
    droplet v2.11.0 44481dd
    damocles-manager v0.10.0-rc1 2f6c5f9
    damocles-worker v0.10.0-rc1 2f6c5f9

    # 升级顺序

    1. sophon-auth
    2. venus
    3. soohon-co
    4. soohon-gateway
    5. sophon-messager
    6. sophon-miner
    7. droplet
    8. venus-wallet
    9. damocles-manager
    10. damocles-worker

    # sophon-auth

    影响功能：

    • 其他组件对获取 auth 的服务

    依赖升级组件: 无

    注意事项：

    • 启动后能否正常鉴权

    # venus

    影响功能：无

    依赖升级组件: sophon-auth

    注意事项：

    编译：先 make dist-clean 再 make，这样可以防止未能正常升级 filecoin-ffi 而带来的问题

    1. 升级后检查vk文件是否完整

    2. 升级后执行命令 ./venus state network-info，然后检查通过日志检查 UpgradeDragonHeight 是否正常:

      # cali
 UpgradeDragonHeight: 1427974
 # mainnet
-UpgradeDragonHeight: 3817920
+UpgradeDragonHeight: 3855360

    3. 升级后需检查是否正常同步区块

    4. 检查主网 v13 actors code，确保与下面输出一样

      ./venus state actor-cids --network-version 22
 
 # 顺序可能会不一样
@@ -67,7 +67,7 @@

    5. 若不排查问题，rust日志级别不建议设置为 trace，因为会打印较多日志

    6. 升级后可以通过命令来 ./venus state get-actor t01000 来确认是否升级成功

    7. actor 迁移

      经测试本次预迁移时间在 30 分钟左右，正式迁移时间在 100 秒左右

      预迁移高度是升级高度前 120 个高度：
 pre-migration  开始：STARTING pre-migration  结束：COMPLETED pre-migration
 migration      开始：STARTING migration      结束：COMPLETED migration
-

    8. 如果 ~/.venus 存在且需要导入快照，需要先删除 ~/.venus/version 文件再导入快照

      • 主网: ./venus daemon --import-snapshot snapshot.car
      • calibnet: ./venus daemon --import-snapshot snapshot.car --network calibrationnet

    # sophon-gateway

    影响功能：无

    依赖升级组件: sophon-auth

    注意事项：

    • 编译时,需要先 make dist-clean 再 make

    # sophon-messager

    影响功能：

    依赖升级组件: venus, sophon-auth, soohon-gateway

    注意事项：

    • 升级之后需要观察能否正常接收消息, 消息能否正常上链

    # sophon-miner

    影响功能：

    依赖升级组件：auth, venus, gateway

    注意事项：

    # droplet

    影响功能：

    • 支持 direct data onboarding，使用文档：https://github.com/ipfs-force-community/droplet/blob/master/docs/zh/direct-on-boarding.md

    依赖升级组件: auth, venus, gateway, messager

    注意事项：

    • 升级后能否正常发单和检索

    # venus-wallet

    影响功能： 无

    依赖升级组件: gateway

    注意事项：

    • 升级后观察是否正常签名，消息能否正常上链

    # damocles-manager

    依赖升级组件: 链服务组件

    注意事项：

    • 编译时,需要先 make dist-clean 再 make

    # damocles-worker

    依赖升级组件: damocles-manager

    注意事项：

    更新结果验证步骤:

    1. 程序启动正常
    2. pre/pro消息正常上链
    3. 出块正常
    4. WD上链正常
    5. 算力增长正常
    6. 真实订单检索正常
    7. 数据库各种gas，生命周期，聚合设置正常

    # 数据库变更

    1. droplet 增加 direct_deals 表，用于存储 direct 订单。

    +

  • 如果 ~/.venus 存在且需要导入快照，需要先删除 ~/.venus/version 文件再导入快照

    • 主网: ./venus daemon --import-snapshot snapshot.car
    • calibnet: ./venus daemon --import-snapshot snapshot.car --network calibrationnet

    • # sophon-gateway

    影响功能：无

    依赖升级组件: sophon-auth

    注意事项：

    • 编译时,需要先 make dist-clean 再 make

    # sophon-messager

    影响功能：

    依赖升级组件: venus, sophon-auth, soohon-gateway

    注意事项：

    • 升级之后需要观察能否正常接收消息, 消息能否正常上链

    # sophon-miner

    影响功能：

    依赖升级组件：auth, venus, gateway

    注意事项：

    # droplet

    影响功能：

    • 支持 direct data onboarding，使用文档：https://github.com/ipfs-force-community/droplet/blob/master/docs/zh/direct-on-boarding.md

    依赖升级组件: auth, venus, gateway, messager

    注意事项：

    • 升级后能否正常发单和检索

    # venus-wallet

    影响功能： 无

    依赖升级组件: gateway

    注意事项：

    • 升级后观察是否正常签名，消息能否正常上链

    # damocles-manager

    依赖升级组件: 链服务组件

    注意事项：

    • 编译时,需要先 make dist-clean 再 make

    # damocles-worker

    依赖升级组件: damocles-manager

    注意事项：

    更新结果验证步骤:

    1. 程序启动正常
    2. pre/pro消息正常上链
    3. 出块正常
    4. WD上链正常
    5. 算力增长正常
    6. 真实订单检索正常
    7. 数据库各种gas，生命周期，聚合设置正常

    # 数据库变更

    1. droplet 增加 direct_deals 表，用于存储 direct 订单。

    ← →

    - + diff --git a/zh/operation/prometheus-instruction.html b/zh/operation/prometheus-instruction.html index dc6656ef6..806b5cf5e 100644 --- a/zh/operation/prometheus-instruction.html +++ b/zh/operation/prometheus-instruction.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -109,7 +109,7 @@ __metrics_path__: "/debug/metrics" instance: "messager"

    # 启动

    $ ./prometheus --config.file=prometheus.yml
-

    使用http://localhost:9090/targets, 可查询组件的指标。

    - +

    使用http://localhost:9090/targets, 可查询组件的指标。

    + diff --git a/zh/operation/troubleshoot-consensus-fault.html b/zh/operation/troubleshoot-consensus-fault.html index b6737a07f..f97a6a646 100644 --- a/zh/operation/troubleshoot-consensus-fault.html +++ b/zh/operation/troubleshoot-consensus-fault.html @@ -13,7 +13,7 @@ gtag('config', 'G-SMSDTMGLTV'); - + @@ -189,7 +189,7 @@ implicit message(f00 -> f03, method : 2, nonce:1288233) idx:480, Compare msg({'/': 'bafy2bzacebka5xwpzelt4cl5pa452k3oi45mbcy7pyrlc3om7sfnul4cz7dcu'}) stateAfterApply: bafy2bzacebhpihnow4fwuebtxenpl27kvl4k7aeozlsruwcdj3berrposkfgs execution-traces: failed -

    程序会打印出不同的 execution-trace 的消息，以及不匹配的调用堆栈，可以方便快速定位问题。

    - +

    程序会打印出不同的 execution-trace 的消息，以及不匹配的调用堆栈，可以方便快速定位问题。

    +