[Nfd-dev] Getting onContentStoreMiss even if the data is in ContentStore

[S. Obaid]

Thanks Ashlesh; this seems to be the problem.
I was not aware of this change.

Regards,
Obaid

On Tue, Sep 19, 2017 at 7:59 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Hi Obaid,
>
>
> What's the data freshness period (if not set, it is set to 0 ms by default
> after this issue was implemented: https://redmine.
> named-data.net/issues/3944)?
>
> (Assuming must be fresh is set on the interest, content store will not
> answer).
>
>
> Ashlesh
> ------------------------------
> *From:* Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu> on behalf of S. Obaid
> <obaidasyed at gmail.com>
> *Sent:* Tuesday, September 19, 2017 8:51:35 PM
> *To:* <nfd-dev at lists.cs.ucla.edu>
> *Subject:* [Nfd-dev] Getting onContentStoreMiss even if the data is in
> ContentStore
>
> Hello all,
>
> I am observing some strange forwarding behaviour of NFD. I am working on a
> star topology of 4 nodes (1 middle and three leaf nodes) where each node is
> running NFD and the routing is setup in a way that the leaf nodes talk to
> each other via middle node.
> In this particular scenario two nodes (attached to face 333 and 273)
> requesting the same data from the third node.
> Here is what I am observing at the middle node.
>
> At 1 the middle node got the interest from node 1 and as there was no
> matching Content in CS, it was forwarded to the Producer.
> At 4 the middle node got the data back, which is forwarded towards the
> consumer in step 6.
> At 8, the middle node got the same interest from node 2. However, instead
> of serving it from the CS; the interest was forwarded to the Producer
> again.
> Shouldn't it be served from the CS as we have already got the data in step
> 4. Any idea what's going wrong here?
>
>
>    1. 1505869006.866421 DEBUG: [Forwarder] onIncomingInterest face=333
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    2. 1505869006.866489 DEBUG: [Forwarder] onContentStoreMiss
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    3. 1505869006.866537 DEBUG: [Forwarder] onOutgoingInterest face=303
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    4. 1505869007.849591 DEBUG: [Forwarder] onIncomingData face=303
>    data=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    5. 1505869007.849650 DEBUG: [Forwarder] onIncomingData
>    matching=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    6. 1505869007.849687 DEBUG: [Forwarder] onOutgoingData face=333
>    data=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    7. 1505869007.949745 DEBUG: [Forwarder] onInterestFinalize
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    satisfied
>    8. 1505869008.050235 DEBUG: [Forwarder] onIncomingInterest face=273
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    9. 1505869008.050316 DEBUG: [Forwarder] onContentStoreMiss
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    10. 1505869008.050363 DEBUG: [Forwarder] onOutgoingInterest face=303
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    11. 1505869008.062779 DEBUG: [Forwarder] onIncomingData face=303
>    data=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    12. 1505869008.062935 DEBUG: [Forwarder] onIncomingData
>    matching=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    13. 1505869008.062964 DEBUG: [Forwarder] onOutgoingData face=273
>    data=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    14. 1505869008.163024 DEBUG: [Forwarder] onInterestFinalize
>    interest=/vfsr/c31/chatapp/chat/chatroom1/u31/contentVideo/476/0/30042
>    satisfied
>
>
> Thanks,
> Obaid
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170920/b0557d16/attachment-0001.html>