It sounds like your persistence volumes are reset upon restarts. Please
double check that persistence is mapped to a permanent location:
https://apacheignite.readme.io/docs/stateful-deployment#section-separate-disk-for-wal
-
Denis
On Wed, Dec 11, 2019 at 10:33 AM naidusm wrote:
> We have a
We have a three-node ignite cluster running inside Kubernetes with native
persistence enabled.
We have an application which uses ignite cache in client mode. And the
application as well running in Kubernetes scaled to 3 pods.
Recently we have started to observe that when we scale down the
Hi Ivan,
Thank you for sharing your feedback. I will try to install all modules in
local agent's repository and run the build.
I will share updates.
Regards,
Saikat
On Tue, Dec 10, 2019 at 9:56 AM Ivan Pavlukhin wrote:
> Saikat,
>
> Let me share my understanding how do we run the majority of
Mikhail Cherkasov created IGNITE-12431:
--
Summary: Allow to set inline size for implicit indexes per table
Key: IGNITE-12431
URL: https://issues.apache.org/jira/browse/IGNITE-12431
Project: Ignite
Hello!
I think we should check that setField happily accepts both BinaryObject and
BinaryObjectBuilder, and then deprecate this method.
Regards,
--
Ilya Kasnacheev
пт, 6 дек. 2019 г. в 16:02, Alexei Scherbakov :
> Looks like it's already possible to pass binary object as value using
>
Alexey,
from my point of view Drill's approach looks like somewhat a hack:
sortedness and index lookups added to a removed from the query plan by
the special rules (which look very messy and complicated). Compare it to
the Phoneix approach where index is added to optimizer as a sorted view
of a
Hi Vladimir,
from what I understand, Drill does not exploit collation of indexes. To
be precise it does not exploit index collation in "natural" way where,
say, we a have sorted TableScan and hence we do not create a new Sort.
Instead of it Drill always create a Sort operator, but if TableScan
Hello!
I don't think Apache Ignite supports it. We even clear caches explicitly if
a node was reset when WAL was disabled, and your scenario is just like this
one but worse.
Regards,
--
Ilya Kasnacheev
ср, 4 дек. 2019 г. в 20:43, Gangaiah Gundeboina :
> Thanks Denis.
>
> It's ok to loose
Hello!
Let's fix MOVING partitions first, think about thin client support later.
If nobody wants to fix that, then I'm pretty sure nobody wants thin client
support also.
Regards,
--
Ilya Kasnacheev
ср, 4 дек. 2019 г. в 11:35, Ivan Pavlukhin :
> Pavel mentioned a thread [1] discussion
Zhenya,
there is nothing in common in implementation of Ignite indexes and
Phoenix indexes. I just borrowed the idea how Phoenix supplies the index
metadata (index name, columns, sorting, etc.) to Calcite optimizer. It's
not about index implementation, it's about metadata handling.
--
Kind
Hello!
Yes, I guess you are right :(
I can surely fix the range issue, It's just that it was so broken that I
could not figure the correct behavior for this case.
Regards,
--
Ilya Kasnacheev
пн, 2 дек. 2019 г. в 15:01, Ivan Pavlukhin :
> Ilya,
>
> I checked your test on a revision before
Saikat,
Let me share my understanding how do we run the majority of our jobs
executing test suites. Hope it will help.
1. ~Build Apache Ignite~ in a separate run and publish everything as a
single artifact ignite.zip (it contains ignite working directory with
compiled modules, e.g.
I'd like Drill approach, worked and debugged with something similar, it's
more easy to support
Buuut, you have an implemented prototype (it votes for Phoenix in my mind)
вт, 10 дек. 2019 г. в 17:19, Vladimir Ozerov :
> Hi Roman,
>
> Why do you think that Drill-style will not let you exploit
Hi Roman,
Why do you think that Drill-style will not let you exploit collation?
Collation should be propagated from the index scan in the same way as in
other sorted operators, such as merge join or streaming aggregate. Provided
that you use converter-hack (or any alternative solution to trigger
Roman just as fast remark, Phoenix builds their approach on already existing
monolith HBase architecture, most cases it`s just a stub for someone who wants
use secondary indexes with a base with no native support of it. Don`t think
it`s good idea here.
>
>
>--- Forwarded message
Hi all!
As you may know there is an activity on integration of Apache Calcite
query optimizer into Ignite codebase is being carried out [1],[2].
One of a bunch of problems in this integration is the absence of
out-of-the-box support for secondary indexes in Apache Calcite. After
some research I
Hi,
We found 3 vulnerabilities while scanning Grid Gain Web console application.
We are using HTTP and not HTTPS due to some issues on our side. Although
vulnerabilities are of lower severity, but thought of reporting it here.
1) HTTP TRACE / TRACK Methods Enabled. (CVE-2004-2320
It's free software without limitations. Just download and use it.
-
Denis
On Tue, Dec 10, 2019 at 1:21 PM Prasad Bhalerao <
prasadbhalerao1...@gmail.com> wrote:
> Hi,
>
> Can apache ignite users use it for free in their production environments?
> What license does it fall under?
>
> Thanks,
>
Hi,
Can apache ignite users use it for free in their production environments?
What license does it fall under?
Thanks,
Prasad
On Fri, Oct 4, 2019 at 5:33 AM Denis Magda wrote:
> Igniters,
>
> There is good news. GridGain made its distribution of Web Console
> completely free. It goes with
Alexey Goncharuk created IGNITE-12430:
-
Summary: Move PagePool to a separate class
Key: IGNITE-12430
URL: https://issues.apache.org/jira/browse/IGNITE-12430
Project: Ignite
Issue Type:
20 matches
Mail list logo
