Yes, it's about Page Memory defragmentation.
Pages in partitions files are stored sequentially, possible, it makes
sense to defragment pages first to avoid interpages gaps since we use
pages offset to manage them.
I filled an issue [1], I hope we will be able to find resources to
solve the issue
Vyacheslav Daradur created IGNITE-10862:
---
Summary: Introduce tool to free up space on a disc of unused
memory pages
Key: IGNITE-10862
URL: https://issues.apache.org/jira/browse/IGNITE-10862
Hi Saikat,
Fix itself is ok. But from the top of my head, I don't know how can we
auto-test this scenario in the future. Do you have an idea?
Sincerely,
Dmitriy Pavlov
ср, 9 янв. 2019 г. в 07:08, Saikat Maitra :
> Hi,
>
> I have raised a PR for the below issue.
>
> IGNITE-10856 cassandra-store
Hi,
In continuation of discussion summarized in [1] I would like to
highlight some points related to avoidance of non-deadlocked
transactions rollback. In [1] maintaining a lock counter for
transaction is suggested in order to avoid rolling back a transaction
which have made progress since a
jeado ko created IGNITE-10861:
-
Summary: Using multiple Ignite Sink got Ignite instance has
already been started Error
Key: IGNITE-10861
URL: https://issues.apache.org/jira/browse/IGNITE-10861
Project:
Hi, which Ignite's version do you use?
*Local* queries are prohibited on client nodes since they do not store data.
The check was added within task [1] and included in Ignite 2.7 release.
[1] https://issues.apache.org/jira/browse/IGNITE-8915
On Tue, Jan 8, 2019 at 10:17 PM prashant wrote:
>
>
Hi,
I have raised a PR for the below issue.
IGNITE-10856 cassandra-store seems to be broken by incorrect guava version
PR - https://github.com/apache/ignite/pull/5780/
Please take a look and share feedback.
Regards,
Saikat
Yury,
I will need to make an update to Genetic Algorithms section of Ignite ReadMe
documentation in support of this ticket.
Please advise on when https://apacheignite.readme.io/v2.8/docs will be
available so I may update accordingly.
Best,
Turik
--
Sent from:
Hi Guys,
I am also running into same issue where I am doing local query
SqlFieldsQuery query = new SqlFieldsQuery(sql);
query.setLocal(true);
FieldsQueryCursor> fq = cache.query(query);
This leads to same exception stack trace.
Is there any workaround
Anton Kurbanov created IGNITE-10860:
---
Summary: Exception on GridJobProcessor.stop()
Key: IGNITE-10860
URL: https://issues.apache.org/jira/browse/IGNITE-10860
Project: Ignite
Issue Type:
10 matches
Mail list logo