Your SlideShare is downloading. ×
Peer-to-Peer Management of Large-Scale Memory Sources (midterm)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Peer-to-Peer Management of Large-Scale Memory Sources (midterm)

482
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
482
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. XPeer Peer-to-Peer Management of Large-Scale Memory Sources Vincent Andrieu – Dr. Mark Roantree
  • 2. Why is XPeer needed ?
    • CDVP experiments so as to study the links between movie content and viewer reactions :
    • 29 movies, 33 experiments, 44 persons and 8 sensors per experiment
    • Sensors data stored in XML files that CDVP needs to query
    • 250 XML files ; more than 670 MB
    • Centralized XML database is not suitable
    • Spreading the XML files over several databases and querying them through a Peer-to-Peer (P2P) network.
  • 3. Application design diagram P2P Network QueryPeers DataPeers (running on eXist servers (native XML databases))
  • 4. Implementation
    • XML Documents (DataPeers) gathered into clusters with keywords
        •  ClusterPeer
    • Metadata stored in an Oracle database, containing info about all the peers
        •  RepositoryPeer
    •  4 peer types :
        • DataPeer
        • QueryPeer
        • ClusterPeer
        • RepositoryPeer
  • 5. Implementation Diagram
  • 6. Launching
    • Peers have a lot of attributes :
        • ID
        • Name
        • Description
        • Keywords
        • Oracle/eXist URLs and username/password to connect
        • Clusters they belong to
        • ...
    • All this metadata is stored in the Oracle metabase.
    • When a peer is launched, the first thing it does is finding a repository peer (because it is connected to the metabase) so as to get his context, so as to know everything about itself.
    • If a repository peer can’t find any other repository peer, then it connects to the metabase
    • But if a non-repository peer can’t find a repository, it dies
  • 7. JXTA platform
    • The JXTA platform is an open source peer-to-peer protocol specification .
    • Logical layer over the network layer
    • The physical network configuration of the peer is transparent. All of them are in the same logical P2P network, even if they actually are in different physical networks.
    • Connection and disconnections are managed.
  • 8. JXTA platform
    • As a JVM is very heavy and several peers may run on the same machine, so the application was designed so as to allow several peers (even different types of peer) to run in the same process, over 1 JXTA Peer.
    ClusterPeer DataPeer DataPeer JXTA Platform RepositoryPeer QueryPeer JXTA Platform DataPeer QueryPeer ClusterPeer JXTA Platform P2P Network
  • 9. Peer design
  • 10. What’s next ?
    • Caching systems (e.g. between ClusterPeer and DataPeer, between QueryPeer and ClusterPeer )
    • Logical expressions or regexps for keywords (e.g. «cdvplex AND Shrek»)
    • Dynamically set the keywords for clusters