Pavel Vinokurov created IGNITE-8912:
---
Summary: PartitionLossPolicy.READ_ONLY_SAFE does not detect
partition loss
Key: IGNITE-8912
URL: https://issues.apache.org/jira/browse/IGNITE-8912
Project: Ign
I checked the code again, seems there is no such event.
Thanks,
Ken Cheng
On Tue, Jul 3, 2018 at 7:41 AM Dmitriy Setrakyan
wrote:
> Do we really not have events in Ignite for cluster activation?
>
> Alexey Goncharuk, can you please comment?
>
> D.
>
> On Mon, Jul 2, 2018 at 1:34 AM, kcheng.mv
Regarding 1. I'm referring to the documentation here,
https://apacheignite.readme.io/docs/topology-validation, which states
"*Topology
validator is used to verify that cluster topology is valid for further
cache operations*." and "*If topology validator is not configured, then the
cluster topology
Do we really not have events in Ignite for cluster activation?
Alexey Goncharuk, can you please comment?
D.
On Mon, Jul 2, 2018 at 1:34 AM, kcheng.mvp wrote:
> Dear igniters,I am going to pick up
> https://issues.apache.org/jira/browse/IGNITE-8376, and did some research
> based on the comments
On Mon, Jul 2, 2018 at 4:03 PM, John Wilson wrote:
> Hi,
>
>
>1. What exactly is a cluster topology? What makes a cluster topology
>invalid for further cache operations?
>
Cluster topology is a set of Ignite nodes in the cluster. I do not think a
cluster topology could be invalid on its
Hi,
1. What exactly is a cluster topology? What makes a cluster topology
invalid for further cache operations?
2. Why do we have the concept of partitions in Ignite? Why don't we
have a key-to-node mapping rather than a key-to-partition and a
partition-to-node mapping?
Thanks,
Jo
Alexey,
Thanks for the instructions. Please put them on Ignite wiki as a sub-page
of Development Process:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
Tell me your Wiki ID and I'll grant required permissions.
--
Denis
On Mon, Jul 2, 2018 at 1:35 AM Igor Sapego wrote:
To be honest, I am not sure if we need to kick off another file system
storage discussion in Ignite. It sounds like a huge effort and likely will
not be productive.
However, I think an ability to store large objects will make sense. For
example, how do I store a 10GB blob in Ignite cache? Most lik
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4292
Ignite 2.4.7.b1 no 8900
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.7.b1-no-8900
Alternatively you ca
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4291
Ignite-8911
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8911
Alternatively you can review and apply these
Eduard Shangareev created IGNITE-8911:
-
Summary: While cache is restarting it's possible to start new
cache with this name
Key: IGNITE-8911
URL: https://issues.apache.org/jira/browse/IGNITE-8911
P
Pavel,
We already can monitor the state of individual nodes and show it through
metrics. Now I'd like to see how to go further and automate a decision on
if a node should be kicked off from the cluster or not.
--
Denis
On Mon, Jul 2, 2018 at 12:28 PM Pavel Kovalenko wrote:
> Denis,
>
> I think
Denis,
I think, JVM can't easily help to itself if it's in SW pause. Most
solutions what I saw about handling such situations are checking heartbeats
on other nodes or run in parallel supervisor process which can detect that
JVM with Ignite in SW.
2018-07-02 20:54 GMT+03:00 Denis Magda :
> Ignit
Hi Igor,
I totally agree with the point that auto-generated things does not
belong to the source tree.
I already made short instructions on how to generate HTML documents with
Sphinx in README file. The instructions assume that the user is able to
use the common tools (Python, pip, virtualen
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4290
Ignite 8900 repro
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-8900-repro
Alternatively you can review and apply th
Igniters,
Pulling this discussion up. Any thoughts?
--
Denis
On Thu, Jun 21, 2018 at 3:52 PM Denis Magda wrote:
> Igniters,
>
> It's a pleasure to see how our project is evolving in a directing of being
> a self-healing solution:
>
>- Ignite can already handle critical failures such as OOM
Ivan Rakov created IGNITE-8910:
--
Summary: PagesList.takeEmptyPage may fail with AssertionError:
type = 1
Key: IGNITE-8910
URL: https://issues.apache.org/jira/browse/IGNITE-8910
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4242
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4218
---
Dmitriy,
A few questions regarding the user cases for the utility:
1) Would I be able to read the extracted data from the dumped file without
Ignite node binary/marshaller metadata? In other words, will I be able to
move only the dumped file to another grid or will I need to move the
metadata as w
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4289
Ignite 2.4.7.b1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.7.b1
Alternatively you can review and app
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4211
---
Pavel,
Thank you. I'll wait for feature comparison and concrete use cases, because
for me this feature still sounds too abstract to judge whether product
would benefit from it.
On Mon, Jul 2, 2018 at 3:15 PM Pavel Kovalenko wrote:
> Dmitriy,
>
> I think we have a little miscommunication here. O
Denis Mekhanikov created IGNITE-8909:
Summary: Visor shows unimplemented off-heap memory cache metric
Key: IGNITE-8909
URL: https://issues.apache.org/jira/browse/IGNITE-8909
Project: Ignite
Dmitriy,
I think we have a little miscommunication here. Of course, I meant
supporting large entries / chunks of binary data. Internally it will be
BLOB storage, which can be accessed through various interfaces.
"File" is just an abstraction for an end user for convenience, a wrapper
layer to have
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4272
---
By the way, guys,
I can see generated docs under source control. We do not store them
this way in Ignite. Instead, we have separate step during release, where
we generate them and include in binary distribution.
So you should remove documents from Git and provide us with instructions
on how to ge
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4288
IGNITE-8905 incorrect assertion was replaced with if-check
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Mikhail Cherkasov created IGNITE-8908:
-
Summary: NPE in BinaryMetadataTransport
Key: IGNITE-8908
URL: https://issues.apache.org/jira/browse/IGNITE-8908
Project: Ignite
Issue Type: Bug
Yury Babak created IGNITE-8907:
--
Summary: [ML] Using vectors in featureExtractor
Key: IGNITE-8907
URL: https://issues.apache.org/jira/browse/IGNITE-8907
Project: Ignite
Issue Type: Improvement
Roman Kondakov created IGNITE-8906:
--
Summary: SQL TX: Immediate rollback for Near transactions during
topology changing.
Key: IGNITE-8906
URL: https://issues.apache.org/jira/browse/IGNITE-8906
Projec
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4287
IGNITE-8684 fix partition state exchange during rebalance
Partition state exchange during rebalance continues to keep sending state
messages (single, full) in the loop even if no changes
Sergey Chugunov created IGNITE-8905:
---
Summary: Incorrect assertion in GridDhtPartitionsExchangeFuture
Key: IGNITE-8905
URL: https://issues.apache.org/jira/browse/IGNITE-8905
Project: Ignite
Hi dkarachentsev,
oh, my fault. I did not notice this part when I look through the document.
I am supposed to post such question to user mail list.
Thank you very much.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi,
Please clarify what's wrong in your opinion?
If you mean that you do not see hits or misses - metrics are disabled by
default [1].
[1] https://apacheignite.readme.io/v2.0/docs/memory-and-cache-metrics
Thanks!
-Dmitry
30.06.2018 05:12, kcheng.mvp пишет:
here is the environment : 1 serve
Pavel Kovalenko created IGNITE-8904:
---
Summary: Add rebalanceThreadPoolSize to nodes configuration
consistency check
Key: IGNITE-8904
URL: https://issues.apache.org/jira/browse/IGNITE-8904
Project: I
I believe, we need to put this instruction on wiki page.
Best Regards,
Igor
On Sun, Jul 1, 2018 at 3:58 PM Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
> Denis,
>
> below is instruction how to publish/update npm module with Ignite NodeJS
> client on npmjs.
> Use it when you decide
Dear igniters,I am going to pick up
https://issues.apache.org/jira/browse/IGNITE-8376, and did some research
based on the comments.based on my understanding, if we want to know this
action is triggered by which way(rest, mbean, auto or visocmd) then we need
to change the core method's signature.I
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/4286
IGNITE-8898
rename command argument '--force' to '--yes' for control.sh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignit
Github user vldpyatkov closed the pull request at:
https://github.com/apache/ignite/pull/4283
---
40 matches
Mail list logo
