Class FloodfillVerifyStoreJob
java.lang.Object
net.i2p.router.JobImpl
net.i2p.router.networkdb.kademlia.FloodfillVerifyStoreJob
- All Implemented Interfaces:
Job
Send a netDb lookup to a floodfill peer - If it is found, great,
but if they reply back saying they dont know it, queue up a store of the
key to a random floodfill peer again (via FloodfillStoreJob)
-
Constructor Summary
ConstructorDescriptionFloodfillVerifyStoreJob
(RouterContext ctx, Hash key, Hash client, long published, int type, Hash sentTo, Set<Hash> toSkip, FloodfillNetworkDatabaseFacade facade) Delay a few seconds, then start the verify -
Method Summary
Methods inherited from class net.i2p.router.JobImpl
dropped, getAddedBy, getContext, getJobId, getMadeReadyOn, getTiming, madeReady, madeReady, requeue, toString
-
Constructor Details
-
FloodfillVerifyStoreJob
public FloodfillVerifyStoreJob(RouterContext ctx, Hash key, Hash client, long published, int type, Hash sentTo, Set<Hash> toSkip, FloodfillNetworkDatabaseFacade facade) Delay a few seconds, then start the verify- Parameters:
client
- generally the same as key, unless encrypted LS2; non-nullpublished
- getDate() for RI or LS1, getPublished() for LS2sentTo
- who to give the credit or blame to, can be nulltoSkip
- don't query any of these peers, may be null- Since:
- 0.9.53 added toSkip param
-
-
Method Details
-
getName
Description copied from interface:Job
Descriptive name of the task -
runJob
public void runJob()Query a random floodfill for the leaseset or routerinfo that we just stored to a (hopefully different) floodfill peer. If it fails (after a timeout period), resend the data. If the queried data is older than what we stored, that counts as a fail.
-