Distributed Monitoring 	 in P2P Systems
Download
1 / 24

Distributed Monitoring in P2P Systems - PowerPoint PPT Presentation


  • 272 Views
  • Updated On :

Distributed Monitoring in P2P Systems Serge Abiteboul , Bogdan Marinoiu INRIA-Futurs and Univ. Paris 11. Organization. Motivation An algebra over XML streams The P2PMonitor system Optimization Conclusion. Motivation. P2P systems.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Distributed Monitoring in P2P Systems ' - PamelaLan


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Slide1 l.jpg
Distributed Monitoring in P2P SystemsSerge Abiteboul, Bogdan MarinoiuINRIA-Futurs and Univ. Paris 11

DocFlow - kick off - 2007 - Monitoring


Organization l.jpg
Organization

  • Motivation

  • An algebra over XML streams

  • The P2PMonitor system

  • Optimization

  • Conclusion

DocFlow - kick off - 2007 - Monitoring



P2p systems l.jpg
P2P systems

  • Peer-to-peer: A large and varying number of computers cooperate to solve some particular task without any centralized authority

  • [email protected]; kazaa; cabal

  • Interactivity between the peers (Web 2.0)

  • Content sharing communities

  • Distributed applications (e.g., games)

  • New services

DocFlow - kick off - 2007 - Monitoring


P2p systems5 l.jpg
P2P systems

  • Benefit from technologies like XML and Web services

  • Complex and hard to control systems

    • Many peers

    • Peers are distributed

    • Peers are autonomous

    • Peers are often unreliable and selfish

    • Peers come and leave

    • Intense communications between peers

    • Content changes rapidly

  • Goal: monitor such systems

DocFlow - kick off - 2007 - Monitoring


Why monitor p2p systems l.jpg
Why monitor P2P systems?

  • P2P Monitoring, e.g., supply chain or manufacturing system

  • Web Intelligence: e.g., business intelligence and surveillance of competing companies

  • P2P Security: e.g., against intrusion, spamming

  • P2P optimization and tuning: e.g., gather statistics, control indexing

  • P2P system administration: e.g., choose where to log or control replication

  • P2P error management: e.g., error detection, error, diagnosis

  • Business: e.g., billing for using resources, procurement

DocFlow - kick off - 2007 - Monitoring



Monitoring one peer alerters l.jpg

XML stream

Detect events at the peer level

Data changes

Database updates

Events in RSS feed

Web page changes

Web service calls

Out call

In call

Each event is represented as an XML document

XML Stream

Monitoring one peer - Alerters

DocFlow - kick off - 2007 - Monitoring


An algebra over streams l.jpg
An algebra over streams

 = outer join &  = s=“Lhasa”

  • Efficient Filter (can provide many selections simultaneously)

  • Binary operators: union, join, etc.

  • Operator with memory: duplicate elimination

  • Same plans meaningful for query processing or monitoring

s2

s3

s4

s1

s5

DocFlow - kick off - 2007 - Monitoring


Activexml algebra in short l.jpg
ActiveXML algebra in short

  • Used both for query and monitoring plans

  • Local computation - Algebra for queries over trees:

    • Pick your favorite

    • Has to work on streams

  • Manage replication

    • Generic data and services

  • Glue

    • Send, receive, eval

  • Essential

    • Include service calls – typically query calls

    • Exchange streams of ActiveXML Algebraic Expressions

DocFlow - kick off - 2007 - Monitoring


Axml stream operator l.jpg
AXML stream operator

  • AXML stream

Q

a

[email protected]

r

[email protected]

[email protected]

r1

r1

r1

“Easy case”

Monotone in-stream

Monotone query

Stream of ActiveXML

s

t

s

t

s

t

Peer p1

DocFlow - kick off - 2007 - Monitoring



Stream specification language l.jpg
Stream specification language

  • for $c on local: outCOM

  • let $timeCall := $c.call.time

  • and $duration := $c.response.time - $timeCall

  • where

  • $c.call.method = "GetTemp“and $duration > 300

  • and $c.call.site = "http://meteofrance.fr"

  • return <longGetTemp>

  • <callTime>{$timeCall}</callTime>

  • <duration>{$duration}</duration>

  • </longGetTemp>

DocFlow - kick off - 2007 - Monitoring


Compiled into a monitoring plan l.jpg
Compiled into a monitoring plan

  • Compile the specification into a monitoring plan

    • Some alerters produce input streams

    • Stream operators

  • Evaluate it

  • The monitoring plan is distributed

DocFlow - kick off - 2007 - Monitoring


What to do with the result streams l.jpg
What to do with the result streams

  • Publish a stream

    • RSS, email, web site

  • Turn a stream into a channel

    • Users can subscribe to it

  • Store stream – distributed tracing

    • Provide traces of the computation

    • Basis for querying a run

    • Basis for analyzing a run: diagnosis

DocFlow - kick off - 2007 - Monitoring


Example monitoring involving many peers l.jpg
Example: monitoring involving many peers

  • For $com1 on http://peer.a.com :outCOM | http://peer.b.com :outCOM,

  • $com2 on http://meteo.fr : inCOM

  • Let $duration := $com1.response.timestamp - $com1.call.timestamp

  • Where

  • $duration > 10 and

  • $com1.call.method = « getTemp »  and Filter

  • $com1.call.site = http://meteo.fr and

  • $com1.call.id = $com2.call.id Join

  • Return Report($com1, $com2)

  • By email to [email protected];

A

M

B

DocFlow - kick off - 2007 - Monitoring


Monitoring task global plan l.jpg
Monitoring Task Global Plan

[email protected]

[email protected]

Filter

Filter

[email protected]

Join

Reporter

Publisher

DocFlow - kick off - 2007 - Monitoring


Distributed monitoring task l.jpg
Distributed Monitoring Task

Peer A:

For $c on local:outCOM

Let $duration = …

Where .

Return $c

By publish as channel X

[email protected]

[email protected]

[email protected]

X

∪@B

[email protected]

[email protected]

Peer M:

For $c1 on local:inCOM ,

$c2 on Y

Where $c1.call.id = $c2.call.id

Return Report($c1, $c2)

By email to [email protected]

[email protected]

[email protected]

Y

Peer B:

For $c on

local:outCOM | X

Let $duration = …

Where ….

Return $c

By publish as channel Y

[email protected]

[email protected]

[email protected]

DocFlow - kick off - 2007 - Monitoring



Optimize the plan l.jpg
Optimize the plan

  • Distribute the work among the peers

  • Try to place computation close to data if possible

  • Try to reduce redundancy

DocFlow - kick off - 2007 - Monitoring


Optimization based on activexml algebra l.jpg

 = outer join &  = s=“Lhasa”

Optimization based on ActiveXML algebra

monitoring plan (a)

r2[s,at]

r3[t,s]

r4[t,s]

r1[t,s]

r5[t,s]

r1[t,s]

r3[t,s]

r4[t,s]

r5[t,s]

monitoring plan (b)

r5[t,s]

r1[t,s]

r3[t,s]

r4[t,s]

monitoring plan (c)

DocFlow - kick off - 2007 - Monitoring



The plan l.jpg
The plan

Specify monitoring

Generate data streams

Store traces

Query traces

Mine traces (e.g., diagnosis)

streams

DocFlow - kick off - 2007 - Monitoring


Merci l.jpg
Merci

Merci

DocFlow - kick off - 2007 - Monitoring


ad