Igniters,
I've put together a page with the most prominent capabilities that have to
be on our radar and must be documented *prior* to the release. Expand it if
anything is missing:
https://cwiki.apache.org/confluence/display/IGNITE/Required+Docs
A full list of doc tickets can be retrieved with
A full list of doc tickets can be retrieved with the following filter in
JIRA:
project = Ignite AND component = documentation AND fixVersion = 2.7 AND
status not in (Resolved, Closed)
--
Denis
On Thu, Sep 6, 2018 at 11:27 PM Denis Magda wrote:
> Igniters,
>
> I've put together a page with the
Hello Maxim,
I miss this conversation and ticket when implementing PageMemory tracker
plugin. By default, it's disabled (every method do nothing), but plugin
instance created anyway.
If we want to get clear Ignite instances in the testing framework in the
core module, PageMemory tracker plugin
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4654
---
Yakov,
Thanks for reply. Indeed, initial design assumed node termination when
hanging critical thread has been detected. But sometimes it looks
inappropriate. Let, for example fsync in WAL writer thread takes too long,
and we terminate the node. Upon rebalancing, this may lead to long fsyncs
on
Dmitry,
Recently, I've faced the same issue. I've tried configs from `example`
Ignite directory and they worked for me.
Try: ./ignite.sh -v example/config/example-ignite.xml
Note. You should have the correct IGNITE_HOME environment variable pointing
at yours Ignite dir.
Is this is what you
Alexey,
Yes, I believe I am using the default config. I do not modify any file
of those came with Ignite nightly build, and I do not supply my own .xml
to `bin/ignite.sh` script, so I think I'm clean.
Could you please clarify, which exactly file to edit and how to set
Aleksey Plekhanov created IGNITE-9500:
-
Summary: SQL system view for list of caches
Key: IGNITE-9500
URL: https://issues.apache.org/jira/browse/IGNITE-9500
Project: Ignite
Issue Type:
Yes, and you should suggest solution, e.g. throttle rebalancing threads
more to produce less load.
What you suggesting kills the idea of this enhancement.
--Yakov
2018-09-07 19:03 GMT+03:00 Andrey Kuznetsov :
> Yakov,
>
> Thanks for reply. Indeed, initial design assumed node termination when
>
Andrey,
I don't understand your point. My opinion, the idea of these changes is to
make cluster more stable and responsive by eliminating hanged nodes. I
would not make too much difference between threads trapped in deadlock and
threads hanging on fsync calls for too long. Both situations lead to
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4705
Configuration compatibility fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gg-14183
Alternatively you can
Pavel Kovalenko created IGNITE-9501:
---
Summary: Exclude newly joining nodes from exchange latch
Key: IGNITE-9501
URL: https://issues.apache.org/jira/browse/IGNITE-9501
Project: Ignite
Pavel Kovalenko created IGNITE-9496:
---
Summary: Add listenAsync method to GridFutureAdapter
Key: IGNITE-9496
URL: https://issues.apache.org/jira/browse/IGNITE-9496
Project: Ignite
Issue
The prototype of the API will look like that
PipelineMdl mdl = new Pipeline ()
.addFeatureExtractor(featureExtractor)
.addLabelExtractor(lbExtractor)
.addStage(new EncoderTrainer()
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4655
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4686
---
Aleksey Zinoviev created IGNITE-9497:
Summary: [ML] Add Pipeline support to Cross-Validation process
Key: IGNITE-9497
URL: https://issues.apache.org/jira/browse/IGNITE-9497
Project: Ignite
Pavel Kovalenko created IGNITE-9494:
---
Summary: Communication error resolver may be invoked when topology
is under construction
Key: IGNITE-9494
URL: https://issues.apache.org/jira/browse/IGNITE-9494
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4704
ZookeeperDiscovery testClientReconnect is flaky in master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Pavel Kovalenko created IGNITE-9493:
---
Summary: Communication error resolver shouldn't be invoked if
connection with client breaks unexpectedly
Key: IGNITE-9493
URL:
Pavel Kovalenko created IGNITE-9492:
---
Summary: Limit number of threads which process SingleMessage with
exchangeId==null
Key: IGNITE-9492
URL: https://issues.apache.org/jira/browse/IGNITE-9492
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4688
---
Chaouki Dhib created IGNITE-9499:
Summary: Node IDs are not guaranteed to be unique after reboot
Key: IGNITE-9499
URL: https://issues.apache.org/jira/browse/IGNITE-9499
Project: Ignite
Issue
Alexander Gerus created IGNITE-9495:
---
Summary: Update version for org.apache.lucene lucene-queryparser :
5.5.2
Key: IGNITE-9495
URL: https://issues.apache.org/jira/browse/IGNITE-9495
Project:
Alexey Goncharuk created IGNITE-9498:
Summary: SchemaExchangeSelfTest should use test IP finder for all
discovery SPIs
Key: IGNITE-9498
URL: https://issues.apache.org/jira/browse/IGNITE-9498
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4694
---
Hello Dmitriy,
Did you use the default config shipped with Ignite? Can you try modifying
the config to use TcpDiscoveryVmIpFinder providing only 127.0.0.1:47500 in
the list of IP addresses?
чт, 6 сент. 2018 г. в 22:16, Dmitry Melnichuk <
dmitry.melnic...@nobitlost.com>:
> Hello igniters!
>
> I
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4696
---
Hello!
Can you please frame it as Github pull request as per our process? Do you
have ticket for that?
Regards,
--
Ilya Kasnacheev
пт, 7 сент. 2018 г. в 5:08, Tâm Nguyễn Mạnh :
>
> modules\indexing\src\main\java\org\apache\ignite\internal\processors\query\h2\opt\GridLuceneIndex.java
>
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/4702
IGNITE-8545 Different queryParallelism validation for cache configuration
You can merge this pull request into a Git repository by running:
$ git pull
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4679
---
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/4698
---
Yury Gerzhedovich created IGNITE-9490:
-
Summary: Connection.getMetaData.getIndexInfo method doesn't return
PK indexes
Key: IGNITE-9490
URL: https://issues.apache.org/jira/browse/IGNITE-9490
Hi Ravil,
We appreciate your contribution. I looking forward to see your PR.
Please don't hesitate to contact us if will have any questions about ML
module.
Regards,
Yury
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4703
IGNITE-9015 Failover test fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9015
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4699
---
Alex,
Thank you.
I've added an additional comment in IGNITE-7679 about PageMemory tracker
plugin, so we can move
all plugins within a single ticket and do not miss anything.
[1] https://issues.apache.org/jira/browse/IGNITE-7679
On Fri, 7 Sep 2018 at 09:39 Alex Plehanov wrote:
> Hello Maxim,
Ravil, Alexey,
I for this task will run CI builds and review this task. After this I will
merge this task.
Ravil,
You can create a your own account on our TeamCity server
https://ci.ignite.apache.org/
Thanks,
Yury
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Github user DaveWHarvey closed the pull request at:
https://github.com/apache/ignite/pull/4706
---
Maxim,
Thank you very much, your command did it. I did not had to set the
`IGNITE_HOME` var though.
Now I must analyze the difference it made to put in into my client's
documentation.
On 9/8/18 2:27 AM, Maxim Muzafarov wrote:
Dmitry,
Recently, I've faced the same issue. I've tried
GitHub user DaveWHarvey opened a pull request:
https://github.com/apache/ignite/pull/4706
Ignite 2.5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/percipiomedia/ignite ignite-2.5
Alternatively you can review and apply these
There are at least two production cases that need to be distinguished:
The first is where a single node restart will repair the problem( and you
get the right node. )
The other cases are those where stopping the node will invalidate it's
backups, leaving only one copy of the data, and the problem
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4615
---
Pavel Kovalenko created IGNITE-9491:
---
Summary: Exchange latch coordinator shouldn't be oldest node in a
cluster
Key: IGNITE-9491
URL: https://issues.apache.org/jira/browse/IGNITE-9491
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4476
---
45 matches
Mail list logo
