v1.15.0 lotus-miner sealing is not same as config

[jzmexec]

I set the lotus-miner config as "CommittedCapacitySectorLifetime = "4320h0m0s"".
But, I get the cc sectors is "2253571 (in 30 weeks 16 hours)".

Can you help me, and how to set the CommittedCapacitySectorLifetime config?

[jzmexec]

[stuberman]

4320 hours == 180 days

In your .lotusminer/config.toml set/add this variable and then restart the lotus-miner.
You can only set the duration of new CC sectors before you pledge that sector.
You cannot modify existing sectors

[Sealing]
CommittedCapacitySectorLifetime = "4320h0m0s"

[stuberman]

FYI - There is a bug in the code such that you cannot actually set the minimum of 180 days (25.7 weeks), but a bit more than 200 days (30 weeks)

[jzmexec]

@stuberman thanks, I'm sure i restart lotus-miner and it is new CC sectors.

[rjan90]

As @stuberman commented above, there is a bug in the code where it takes into account the MaxProveCommitDuration when creating a CC-sector, which does not make it possible to create a 180 day CC-sector, only approx 210 days as minimum. The issue is being tracked here: #7609