5

There are a few people working on a project along with me that have been trying to figure out the best way to deal with this issue. It seems this should be a standard thing wanted regularly, but for some reason we can't seem to get the right answer.

If I have some work to be done and I throw a bunch of messages at a router, how can I tell when all the work is done? For example, if we're reading lines of a 1 million line file and sending the line off to actors to process this, and you need to process the next file, but must wait for the first to complete, how can you know when it is complete?

One further comment. I'm aware and have used Await.result() and Await.ready() used with Patters.ask(). One difference is, each line would have a Future and we'd have a HUGE array of these futures to wait on, not just one. Additionally, we are populating a large domain model taking up considerable memory, and do not wish to add additional memory for holding an equal number of futures in memory waiting to be composed, while using actors each one completes after doing it's work not holding memory waiting to be composed.

We're using Java and not Scala.

Pseudo code:

for(File file : files) {
    ...
    while((String line = getNextLine(fileStream)) != null) {
        router.tell(line, this.getSelf());
    }
    // we need to wait for this work to finish to do the next
    // file because it's dependent on the previous work
}

It would seem you'd often want to do a lot of work and know when it's finished with actors.

4

2 に答える 2

0

ルートで使用context.setRecieveTimeoutして、処理されたメッセージの数とともにメッセージを送信者に送り返します。処理されたメッセージの合計 == 送信された量になったら完了です。

ルートが頻繁に起動しないほどビジーなままにsetReceiveTimeoutなる場合は、独自のメッセージをスケジュールしてカウントを送り返します。

于 2013-07-12T16:36:09.073 に答える