Opened 10 years ago

Closed 5 years ago

#189 closed Bug (invalid)

Multiple p2p enabled tabs cause problems

Reported by: schwittmann Owned by: Sven Rech
Priority: Important Milestone: CrypTool 2.1 BETA 1
Component: KeySearcher Keywords:
Cc: kopal

Description

If you have two tabs running the same p2p keysearcher workspace, you might encounter unexpected side effects:

Since both workspaces share the same peer-to-peer stack, they also have the same versioned DHT. A versioned dht should prevent the "lost update" problem in a distributed environment. That is if, two peers write to the same entry, only one will succeed. The other has to read again before being able to write successfully. The underlying assumption is that the read entry will be considered at application level and meaningful measurements will be taken.

However, under the mentioned circumstances this won't work. If both tabs write data at the same key, BOTH will succeed, because from the viewpoint of the DHT these are two writes from the SAME peer.

Change History (5)

comment:1 Changed 10 years ago by Matthäus Wander

Cc: kopal added

As a consequence, two different KeySearcher instances may reserve and compute the same chunk without knowing about the conflict.

comment:2 Changed 10 years ago by Matthäus Wander

Milestone: CrypTool 2.0 BETA 4

Is this still valid?

comment:3 Changed 10 years ago by Sven Rech

Milestone: CrypTool 2.0 BETA 4CrypTool 2.0 BETA 5
Status: newaccepted

Yes, but not for Beta 4!

comment:4 Changed 10 years ago by Matthäus Wander

Milestone: CrypTool 2.0 BETA 5CrypTool 2.1

p2p-related, postponed

comment:5 Changed 5 years ago by kopal

Resolution: invalid
Status: acceptedclosed

we completely replaced p2p with voluntlib

Note: See TracTickets for help on using tickets.