asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Carey <dtab...@gmail.com>
Subject Re: Additional Documentation
Date Thu, 26 May 2016 00:13:44 GMT
Nice...!!!
On May 25, 2016 4:25 PM, "Chris Hillery" <chillery@hillery.land> wrote:

> Awesome stuff, Abdullah. That would have helped me quite a bit in the past,
> and will I'm sure be useful in future as well.
>
> Ceej
> aka Chris Hillery
>
> On Wed, May 25, 2016 at 2:11 PM, abdullah alamoudi <bamousaa@gmail.com>
> wrote:
>
> > Hi dev,
> > Recently, I have been working on introducing NC to NC messaging for
> > different messages needed to be communicated between different NCs. Right
> > now, our current NC to NC network communication is only used for job
> > communication to send data in the Hyracks job pipeline.
> >
> > I have completed the implementation of additional network communication
> > interfaces using Netty when I was asked to check the feasibility of using
> > the existing infrastructure to perform this task.
> >
> > As with every task that requires complete understanding of some existing
> > AsterixDB / Hyracks components, I had to spend sometime reading and
> tracing
> > code. During this, I started two documents:
> > 1. Node Controller Bootstrap: In this document, I list the sequence of
> > actions taken when the NC starts up.
> >
> >
> https://cwiki.apache.org/confluence/display/ASTERIXDB/Node+Controller+Bootstrap
> >
> > 2. Node Controller Network Threads: In this document, I list the
> different
> > network threads and how each of them work.
> >
> >
> https://cwiki.apache.org/confluence/display/ASTERIXDB/Node+Controller+Network+Threads
> >
> > We still need better and more documentation of what components we have,
> > where they live, what they do, and how they work. If you can help achieve
> > that, then please do. At least, if you find yourself in a situation where
> > you need to do some code reading to understand something, take the
> > opportunity to contribute to the documentation.
> >
> > Hope others make good use of these,
> > ~Abdullah.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message