Re: config guide
Hello! Are you talking about TRANSACTIONAL caches and their cache store committing a transaction? I'm actually not sure what is the best practice here. I think that if you are confident that noone else besides Ignite is writing in that DB, you can skip DB-level locking. Regards, -- Ilya Kasnacheev сб, 13 апр. 2019 г. в 05:13, Coleman, JohnSteven (Agoda) < johnsteven.cole...@agoda.com>: > For CacheStore.write is there any need to lock in the database to prevent > simultaneous row updates? Presumably it’s quicker to lock the key at the > cache level and allow DB lock free and non-transactional updates? > > > > John > > > > *From:* Ilya Kasnacheev > *Sent:* Thursday, April 11, 2019 4:31 PM > *To:* user@ignite.apache.org > *Subject:* Re: config guide > > > > Email received from outside the company. If in doubt don't click links nor > open attachments! > -- > > Hello! > > > > Most of those topics are solidly covered in our docs: > https://apacheignite.readme.io/docs > > > > More precisely, > > https://apacheignite.readme.io/docs/cache-configuration > > > https://apacheignite.readme.io/docs/3rd-party-store#section-custom-cachestore > > > > Please feel free to ask if any questions remain. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > чт, 11 апр. 2019 г. в 04:42, Coleman, JohnSteven (Agoda) < > johnsteven.cole...@agoda.com>: > > What is the best guide to Ignite configuration? For example how to have a > distributed cache that is both partitioned to spread the values as well as > resilient so nothing is lost with node failures? > > > > Also examples how to efficiently reload whole table to a cache after a > DC/full cluster failure and how to load highly used data in local memory vs > distributed cache vs persistent storage. > > > > John > > > -- > This message is confidential and is for the sole use of the intended > recipient(s). It may also be privileged or otherwise protected by copyright > or other legal rules. If you have received it by mistake please let us know > by reply email and delete it from your system. It is prohibited to copy > this message or disclose its content to anyone. Any confidentiality or > privilege is not waived or lost by any mistaken delivery or unauthorized > disclosure of the message. All messages sent to and from Agoda may be > monitored to ensure compliance with company policies, to protect the > company's interests and to remove potential malware. Electronic messages > may be intercepted, amended, lost or deleted, or contain viruses. > >
RE: config guide
For CacheStore.write is there any need to lock in the database to prevent simultaneous row updates? Presumably it’s quicker to lock the key at the cache level and allow DB lock free and non-transactional updates? John From: Ilya Kasnacheev Sent: Thursday, April 11, 2019 4:31 PM To: user@ignite.apache.org Subject: Re: config guide Email received from outside the company. If in doubt don't click links nor open attachments! Hello! Most of those topics are solidly covered in our docs: https://apacheignite.readme.io/docs More precisely, https://apacheignite.readme.io/docs/cache-configuration https://apacheignite.readme.io/docs/3rd-party-store#section-custom-cachestore Please feel free to ask if any questions remain. Regards, -- Ilya Kasnacheev чт, 11 апр. 2019 г. в 04:42, Coleman, JohnSteven (Agoda) mailto:johnsteven.cole...@agoda.com>>: What is the best guide to Ignite configuration? For example how to have a distributed cache that is both partitioned to spread the values as well as resilient so nothing is lost with node failures? Also examples how to efficiently reload whole table to a cache after a DC/full cluster failure and how to load highly used data in local memory vs distributed cache vs persistent storage. John This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.
Re: config guide
Hello! Most of those topics are solidly covered in our docs: https://apacheignite.readme.io/docs More precisely, https://apacheignite.readme.io/docs/cache-configuration https://apacheignite.readme.io/docs/3rd-party-store#section-custom-cachestore Please feel free to ask if any questions remain. Regards, -- Ilya Kasnacheev чт, 11 апр. 2019 г. в 04:42, Coleman, JohnSteven (Agoda) < johnsteven.cole...@agoda.com>: > What is the best guide to Ignite configuration? For example how to have a > distributed cache that is both partitioned to spread the values as well as > resilient so nothing is lost with node failures? > > > > Also examples how to efficiently reload whole table to a cache after a > DC/full cluster failure and how to load highly used data in local memory vs > distributed cache vs persistent storage. > > > > John > > -- > This message is confidential and is for the sole use of the intended > recipient(s). It may also be privileged or otherwise protected by copyright > or other legal rules. If you have received it by mistake please let us know > by reply email and delete it from your system. It is prohibited to copy > this message or disclose its content to anyone. Any confidentiality or > privilege is not waived or lost by any mistaken delivery or unauthorized > disclosure of the message. All messages sent to and from Agoda may be > monitored to ensure compliance with company policies, to protect the > company's interests and to remove potential malware. Electronic messages > may be intercepted, amended, lost or deleted, or contain viruses. >
config guide
What is the best guide to Ignite configuration? For example how to have a distributed cache that is both partitioned to spread the values as well as resilient so nothing is lost with node failures? Also examples how to efficiently reload whole table to a cache after a DC/full cluster failure and how to load highly used data in local memory vs distributed cache vs persistent storage. John This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.
