Re: Stupide question about Queue ?

[Valentin Kulichenko]

Agree with Denis. Sounds like this can be easily achieved by enabling swap
layer for queue cache. So we just need to put this on configuration.

-Val

On Thu, Jan 14, 2016 at 5:44 AM, Denis Magda  wrote:

> Hi,
>
> This seems to be an interesting functionality. As I understand you're
> referring to [1].
>
> Personally I think that it makes sense to support the same in Ignite.
> However I would just extend CollectionConfiguration adding ability to set
> an eviction policy and enable swap on demand. When eviction policy faces
> with a limit entries will be evicted to swap space.
> Don't think that we need to support other kind of storages here.
>
> Igniters, do you have other thoughts on this?
>
> [1] http://docs.hazelcast.org/docs/3.5/manual/html/queue-persistence.html
>
> --
> Denis
>
>
> On 1/14/2016 1:41 PM, Yann BLAZART wrote:
>
> Hello,
>
>
>
> In hazelcast we can persist Queues in Database, this  help me for example
> when consumer are down to no have OOM exception.
>
>
>
> But I don’t see this possibility in Ignite docs ?
>
>
>
> This message and any attachments (the "message") is
> intended solely for the intended addressees and is confidential.
> If you receive this message in error,or are not the intended recipient(s),
> please delete it and any copies from your systems and immediately notify
> the sender. Any unauthorized view, use that does not comply with its
> purpose,
> dissemination or disclosure, either whole or partial, is prohibited. Since
> the internet
> cannot guarantee the integrity of this message which may not be reliable,
> BNP PARIBAS
> (and its subsidiaries) shall not be liable for the message if modified,
> changed or falsified.
> Do not print this message unless it is necessary,consider the environment.
>
>
> --
>
> Ce message et toutes les pieces jointes (ci-apres le "message")
> sont etablis a l'intention exclusive de ses destinataires et sont
> confidentiels.
> Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
> merci de le detruire ainsi que toute copie de votre systeme et d'en avertir
> immediatement l'expediteur. Toute lecture non autorisee, toute utilisation
> de
> ce message qui n'est pas conforme a sa destination, toute diffusion ou
> toute
> publication, totale ou partielle, est interdite. L'Internet ne permettant
> pas d'assurer
> l'integrite de ce message electronique susceptible d'alteration, BNP
> Paribas
> (et ses filiales) decline(nt) toute responsabilite au titre de ce message
> dans l'hypothese
> ou il aurait ete modifie, deforme ou falsifie.
> N'imprimez ce message que si necessaire, pensez a l'environnement.
>
>
>

Re: Stupide question about Queue ?

[Murthy Kakarlamudi]

What are the possibilities for swap spaces? Can we persist the cache/queue
content to file system based on the eviction policy?

Thanks,
Murthy.

On Thu, Jan 14, 2016 at 5:23 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Agree with Denis. Sounds like this can be easily achieved by enabling swap
> layer for queue cache. So we just need to put this on configuration.
>
> -Val
>
> On Thu, Jan 14, 2016 at 5:44 AM, Denis Magda  wrote:
>
>> Hi,
>>
>> This seems to be an interesting functionality. As I understand you're
>> referring to [1].
>>
>> Personally I think that it makes sense to support the same in Ignite.
>> However I would just extend CollectionConfiguration adding ability to set
>> an eviction policy and enable swap on demand. When eviction policy faces
>> with a limit entries will be evicted to swap space.
>> Don't think that we need to support other kind of storages here.
>>
>> Igniters, do you have other thoughts on this?
>>
>> [1] http://docs.hazelcast.org/docs/3.5/manual/html/queue-persistence.html
>>
>> --
>> Denis
>>
>>
>> On 1/14/2016 1:41 PM, Yann BLAZART wrote:
>>
>> Hello,
>>
>>
>>
>> In hazelcast we can persist Queues in Database, this  help me for example
>> when consumer are down to no have OOM exception.
>>
>>
>>
>> But I don’t see this possibility in Ignite docs ?
>>
>>
>>
>> This message and any attachments (the "message") is
>> intended solely for the intended addressees and is confidential.
>> If you receive this message in error,or are not the intended
>> recipient(s),
>> please delete it and any copies from your systems and immediately notify
>> the sender. Any unauthorized view, use that does not comply with its
>> purpose,
>> dissemination or disclosure, either whole or partial, is prohibited.
>> Since the internet
>> cannot guarantee the integrity of this message which may not be reliable,
>> BNP PARIBAS
>> (and its subsidiaries) shall not be liable for the message if modified,
>> changed or falsified.
>> Do not print this message unless it is necessary,consider the environment.
>>
>>
>> --
>>
>> Ce message et toutes les pieces jointes (ci-apres le "message")
>> sont etablis a l'intention exclusive de ses destinataires et sont
>> confidentiels.
>> Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
>> merci de le detruire ainsi que toute copie de votre systeme et d'en
>> avertir
>> immediatement l'expediteur. Toute lecture non autorisee, toute
>> utilisation de
>> ce message qui n'est pas conforme a sa destination, toute diffusion ou
>> toute
>> publication, totale ou partielle, est interdite. L'Internet ne permettant
>> pas d'assurer
>> l'integrite de ce message electronique susceptible d'alteration, BNP
>> Paribas
>> (et ses filiales) decline(nt) toute responsabilite au titre de ce message
>> dans l'hypothese
>> ou il aurait ete modifie, deforme ou falsifie.
>> N'imprimez ce message que si necessaire, pensez a l'environnement.
>>
>>
>>
>

Re: Stupide question about Queue ?

[Valentin Kulichenko]

Created ticket for queue swapping feature:
https://issues.apache.org/jira/browse/IGNITE-2389

Feel free to provide feedback.

-Val

On Thu, Jan 14, 2016 at 3:24 PM, Murthy Kakarlamudi 
wrote:

> What are the possibilities for swap spaces? Can we persist the cache/queue
> content to file system based on the eviction policy?
>
> Thanks,
> Murthy.
>
> On Thu, Jan 14, 2016 at 5:23 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Agree with Denis. Sounds like this can be easily achieved by enabling
>> swap layer for queue cache. So we just need to put this on configuration.
>>
>> -Val
>>
>> On Thu, Jan 14, 2016 at 5:44 AM, Denis Magda  wrote:
>>
>>> Hi,
>>>
>>> This seems to be an interesting functionality. As I understand you're
>>> referring to [1].
>>>
>>> Personally I think that it makes sense to support the same in Ignite.
>>> However I would just extend CollectionConfiguration adding ability to
>>> set an eviction policy and enable swap on demand. When eviction policy
>>> faces with a limit entries will be evicted to swap space.
>>> Don't think that we need to support other kind of storages here.
>>>
>>> Igniters, do you have other thoughts on this?
>>>
>>> [1]
>>> http://docs.hazelcast.org/docs/3.5/manual/html/queue-persistence.html
>>>
>>> --
>>> Denis
>>>
>>>
>>> On 1/14/2016 1:41 PM, Yann BLAZART wrote:
>>>
>>> Hello,
>>>
>>>
>>>
>>> In hazelcast we can persist Queues in Database, this  help me for
>>> example when consumer are down to no have OOM exception.
>>>
>>>
>>>
>>> But I don’t see this possibility in Ignite docs ?
>>>
>>>
>>>
>>> This message and any attachments (the "message") is
>>> intended solely for the intended addressees and is confidential.
>>> If you receive this message in error,or are not the intended
>>> recipient(s),
>>> please delete it and any copies from your systems and immediately notify
>>> the sender. Any unauthorized view, use that does not comply with its
>>> purpose,
>>> dissemination or disclosure, either whole or partial, is prohibited.
>>> Since the internet
>>> cannot guarantee the integrity of this message which may not be
>>> reliable, BNP PARIBAS
>>> (and its subsidiaries) shall not be liable for the message if modified,
>>> changed or falsified.
>>> Do not print this message unless it is necessary,consider the
>>> environment.
>>>
>>>
>>> --
>>>
>>> Ce message et toutes les pieces jointes (ci-apres le "message")
>>> sont etablis a l'intention exclusive de ses destinataires et sont
>>> confidentiels.
>>> Si vous recevez ce message par erreur ou s'il ne vous est pas destine,
>>> merci de le detruire ainsi que toute copie de votre systeme et d'en
>>> avertir
>>> immediatement l'expediteur. Toute lecture non autorisee, toute
>>> utilisation de
>>> ce message qui n'est pas conforme a sa destination, toute diffusion ou
>>> toute
>>> publication, totale ou partielle, est interdite. L'Internet ne
>>> permettant pas d'assurer
>>> l'integrite de ce message electronique susceptible d'alteration, BNP
>>> Paribas
>>> (et ses filiales) decline(nt) toute responsabilite au titre de ce
>>> message dans l'hypothese
>>> ou il aurait ete modifie, deforme ou falsifie.
>>> N'imprimez ce message que si necessaire, pensez a l'environnement.
>>>
>>>
>>>
>>
>