filecoin-project/boost

Error with boost data-transfer after Yugabyte upgrade

stuberman opened this issue · 2 comments

stuberman commented

Checklist

  • This is not a question or a support request. If you have any boost related questions, please ask in the discussion forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • This is not an enhancement request. If it is, please file a improvement suggestion instead.
  • I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
  • I did not make any code changes to boost.

Boost component

  • boost daemon - storage providers
  • boost client
  • boost UI
  • boost data-transfer
  • boost index-provider
  • Other

Boost Version

boostd version 2.1.0-rc3+mainnet+git.1622d0c

Describe the Bug

I was able to successfully upgrade Yugabyte from version 2.19.0.0 to 2.19.3.0
However when running nohup boostd-data run yugabyte --hosts 127.0.0.2 --connect-string="postgresql://yugabyte:yugabyte@127.0.0.2:5433?sslmode=disable" --addr 0.0.0.0:8044 & I get an error and the process exits.

Logging Information

Setting up connection and creating data structures... this might take a minute...
Error: starting yugabyte store: creating cassandra tables: executing
CREATE TABLE IF NOT EXISTS PayloadToPieces (
    PayloadMultihash BLOB,
    PieceCid BLOB,
    -- PayloadMultihash is the partition key: the key that determines which
    -- node the row is sent to.
    -- PieceCid is the clustering key: the data is sorted by this key.
    -- We want both of these to be in the primary key because
    -- the piece cids should be a unique set.
    PRIMARY KEY (PayloadMultihash, PieceCid)
)
code=2200; message=Invalid Table Definition. Error creating table idx.payloadtopieces on the master: num_tablets should be greater than 0. Client would need to wait for master leader get heartbeats from tserver.
CREATE TABLE IF NOT EXISTS PayloadToPieces (
                           ^^^^^^^^^^^^^^^
    PayloadMultihash BLOB,
    PieceCid BLOB,
    -- PayloadMultihash is the partition key: the key that determines which
    -- node the row is sent to.
    -- PieceCid is the clustering key: the data is sorted by this key.
    -- We want both of these to be in the primary key because
    -- the piece cids should be a unique set.
    PRIMARY KEY (PayloadMultihash, PieceCid)
)
 (ql error -302)

Repo Steps

  1. Run 'boostd-data'
  2. Do '...'
  3. See error '...'
    ...
LexLuthr commented

It sounds like something went wrong with your upgrade. I am assuming you are running a single node Yugabyte. The error states "tserver is down". Can you please check the status of your Yugabyte and verify that tserver is actually running and there are no error in the logs.

  • 👍1
stuberman commented

Fixed T-Server start error