[VOTE] Release Apache SensSoft (Incubating) UserALE.js 1.0.0 RC#1

2018-02-26 Thread lewis john mcgibbney 
Hi Folks,
This thread is an official general@ VOTE to release the Apache SensSoft
(Incubating) UserALE.js 1.0.0 RC#1. The previous SensSoft (Incubating)
community VOTE [0] passed with RESULTS at [1].
This VOTE will be open for at least 72 hours and will pass if at least 3
IPMC members VOTE +1.
Apache SensSoft (Incubating) UserALE.js is released in a number of forms

1) source and binary artifacts which can be found at [2] alongside
accompanying .asc, .md5 and .sha512 accompanying signatures.

2) The tagged source [3] commitId b29542e6cc1e74c4caccdeb9ed4191013498e9ee

All artifacts were signed by 48BAEBF6 2013-10-28 Lewis John McGibbney (CODE
SIGNING KEY)  included within the SensSoft KEYS file
[4].

Further to the VOTE passing, artifacts will also be published via the NPM
channel for wider distribution.

Lewis

[ ] +1, let's get it released!!!
[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

P.S. Here is my IPMC-binding +1

[0] https://s.apache.org/ysWS
[1] https://s.apache.org/FHKx
[2] https://dist.apache.org/repos/dist/dev/incubator/senssoft/
apache-senssoft-useralejs-1.0.0/
[3] https://s.apache.org/fzXf
[4] https://dist.apache.org/repos/dist/dev/incubator/senssoft/KEYS

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [VOTE] Release Apache Hivemall (Incubating) v0.5.0 Release Candidate 3

2018-02-26 Thread Makoto Yui 
Hi,

I created a docker image [1,2] to verify release artifacts.

Just run the following command to verify a release artifact.

# 1). run a docker image
$ docker run -it hivemall/verify:v0.5.0-rc3

# 2). download Hivemall release artifacts, build, and run unit tests.
$ ./build_from_src.sh

We need votes from IPMC members.

Thanks,
Makoto

[1] https://hub.docker.com/r/hivemall/verify/
[2] https://github.com/myui/hivemall-dockerfiles

2018-02-20 14:19 GMT+09:00 Makoto Yui :
> Hi all,
>
> The Apache Hivemall community has approved a proposal to release
> Apache Hivemall v0.5.0
> by v0.5.0 Release Candidate 3.
>
> We now kindly request that the Incubator PMC members review and vote
> on this incubator release candidate.
>
> The PPMC vote thread is located here:
> 
> https://www.mail-archive.com/dev@hivemall.incubator.apache.org/msg00462.html
> (vote)
> 
> https://www.mail-archive.com/dev@hivemall.incubator.apache.org/msg00468.html
> (vote result)
>
> Links to various release artifacts are given below.
>
> - The source tarball, including signatures, digests, ChangeLog, etc.:
>   
> https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/
> - Sources for the release:
>   
> https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/hivemall-0.5.0-incubating-source-release.zip
> - Git tag for the release:
>   
> https://git-wip-us.apache.org/repos/asf?p=incubator-hivemall.git;a=shortlog;h=refs/tags/v0.5.0-rc3
> - The Nexus Staging URL:
>   
> https://repository.apache.org/content/repositories/orgapachehivemall-1003/
> - KEYS file for verification:
>   https://dist.apache.org/repos/dist/dev/incubator/hivemall/KEYS
> - For information about the contents of this release, see:
>   
> https://dist.apache.org/repos/dist/dev/incubator/hivemall/0.5.0-incubating-rc3/ChangeLog.html
>
> Artifacts verification how-to can be found in
> http://hivemall.incubator.apache.org/verify_artifacts.html
>
> Please vote accordingly:
>
> [ ] +1  approve (Release this package as Apache Hivemall 0.5.0-incubating)
> [ ] -1  disapprove (and reason why)
>
> The vote will be open for at least 72 hours.
>
> Regards,
> Makoto
> on behalf of Apache Hivemall PPMC
>
> --
> Makoto YUI 
> Research Engineer, Treasure Data, Inc.
> http://myui.github.io/



-- 
Makoto YUI 
Research Engineer, Treasure Data, Inc.
http://myui.github.io/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Rya incubating v 3.2.12 RC2

2018-02-26 Thread Billie Rinaldi 
+1 (binding)

* checksums and signatures are good
* license and notice are good
* source zip matches the tag
* DISCLAIMER exists and file name contains incubating
* builds from source
Note that eventually Rya will need to review the license and notice files
it is providing for its binary artifacts that are published to the maven
repository. We can discuss this further on the Rya list. See also [1].

[1]: http://www.apache.org/dev/licensing-howto.html#binary

On 2/24/18 10:18 PM, Adina Crainiceanu wrote:

> The Apache Rya community has voted and approved the proposed release of
> Apache Rya 3.2.12 (Incubating) RC2.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
> supports SPARQL queries. Rya is a scalable RDF data management system
> built
> on top of Apache Accumulo®. Rya uses novel storage methods, indexing
> schemes, and query processing techniques that scale to billions of triples
> across multiple nodes. Rya provides fast and easy access to the data
> through SPARQL, a conventional query mechanism for RDF data. More
> information can be found at http://rya.incubator.apache.org/
>
> [VOTE] Thread:
> https://lists.apache.org/thread.html/75ba0d23c08263f8117baf8
> 05c3960bfcf8f069efb2a494349e9ee7e@%3Cdev.rya.apache.org%3E
>
> [VOTE RESULT] Thread:
> https://lists.apache.org/thread.html/8e178647abb346094977817
> 874748d78f86b2c61bbec8000b5fdc24c@%3Cdev.rya.apache.org%3E
>
> The source zip, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> incubating-3.2.12-rc2/
>
> Ancillary artifacts such as poms, jars, wars, etc. can be found here:
> https://repository.apache.org/content/repositories/
> orgapacherya-1010/org/apache/rya/
>
> The Git tag is rya-incubating-3.2.12-rc2
> The Git commit ID is edb9aa6f9d3479f22a8d17dae928d2ca19e5de37
> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> edb9aa6f9d3479f22a8d17dae928d2ca19e5de37
>
>
> Checksums of rya-project-3.2.12-source-release.zip:
> SHA512:a0e87e1b3813e1425bf58e5e66e8cf8f948a1157f6905a55c913d
> 4169dfb8cfa05fa7c77514c2f75e414654198f9674533227a15ceee2fb68
> 35e15777a0c48d8
> SHA1: 58128bf6cc5c8d92e429bd3a26aa1c104c757097
> MD5: 6e70b0d5aa54a4f018d5c12464e774e3
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/adina.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj
> ectId=12319020&version=12341570
>  ectId=12319020&version=12341570>*
>
> Issues closed/resolved between RC1 and RC2
> https://issues.apache.org/jira/browse/RYA-468
>
>
> The vote will be open for at least 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source (mvn clean
> install), and test.  Then please vote:
>
> [ ] +1 Release this package as rya-project-3.2.12
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>
> Thank you,
> Adina
>
>

Re: [VOTE] Accept Druid into the Apache Incubator

2018-02-26 Thread Ashutosh Chauhan 
+1

On Sun, Feb 25, 2018 at 11:51 PM, Hao Chen  wrote:

> +1 (non-binding)
>
> Hao Chen
>
> *PMC & Committer, Apache Eagle*
>
> On Mon, Feb 26, 2018 at 3:02 PM, ShaoFeng Shi 
> wrote:
>
> > +1 (non-binding)
> >
> > 2018-02-26 14:16 GMT+08:00 Zhanhui Li :
> >
> > > +1 (non-binding)
> > >
> > > Glad to see Druid in Apache community.
> > >
> > > > 在 2018年2月26日，下午1:45，Bhupesh Chawda  写道：
> > > >
> > > > +1 (non-binding)
> > > >
> > > > ~ Bhupesh
> > > >
> > > >
> > > > ___
> > > >
> > > > Bhupesh Chawda
> > > >
> > > > E: bhup...@datatorrent.com  |
> Twitter:
> > > @bhupeshsc
> > > >
> > > > www.datatorrent.com   |
> apex.apache.org
> > <
> > > http://apex.apache.org/>
> > > >
> > > >
> > > >
> > > > On Mon, Feb 26, 2018 at 11:12 AM, Chinmay Kolhatkar <
> > chin...@apache.org
> > > >
> > > > wrote:
> > > >
> > > >> +1
> > > >>
> > > >> On 2018/02/24 09:02:41, Ted Dunning  wrote:
> > > >>> +1
> > > >>>
> > > >>>
> > > >>>
> > > >>> On Thu, Feb 22, 2018 at 11:03 AM, Julian Hyde 
> > > wrote:
> > > >>>
> > >  Hi all,
> > > 
> > >  After some discussion on the Druid proposal[1], I'd like to
> > >  start a vote on accepting Druid into the Apache Incubator,
> > >  per the ASF policy[2] and voting rules[3].
> > > 
> > >  A vote for accepting a new Apache Incubator podling is a
> > >  majority vote for which only Incubator PMC member votes are
> > >  binding. Votes from other people are also welcome as an
> > >  indication of people's enthusiasm (or lack thereof).
> > > 
> > >  Please do not use this VOTE thread for discussions.  If
> > >  needed, start a new thread instead.
> > > 
> > >  This vote will run for at least 72 hours. Please VOTE as
> > >  follows:
> > >  [ ] +1 Accept Druid into the Apache Incubator
> > >  [ ] +0 Abstain
> > >  [ ] -1 Do not accept Druid into the Apache Incubator
> > > because ...
> > > 
> > >  The proposal is listed below, but you can also access it on
> > >  the wiki[4].
> > > 
> > >  Julian
> > > 
> > >  [1] https://lists.apache.org/thread.html/
> > > >> b95f90a30b6e8587e9b108f368b07c
> > >  1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
> > > 
> > >  [2] https://incubator.apache.org/policy/incubation.html#
> > >  approval_of_proposal_by_sponsor
> > > 
> > >  [3] http://www.apache.org/foundation/voting.html
> > > 
> > >  [4] https://wiki.apache.org/incubator/DruidProposal
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  = Druid Proposal =
> > > 
> > >  == Abstract ==
> > > 
> > >  Druid is a high-performance, column-oriented, distributed
> > >  data store.
> > > 
> > >  == Proposal ==
> > > 
> > >  Druid is an open source data store designed for real-time
> > >  exploratory analytics on large data sets. Druid's key
> > >  features are a column-oriented storage layout, a distributed
> > >  shared-nothing architecture, and ability to generate and
> > >  leverage indexing and caching structures. Druid is typically
> > >  deployed in clusters of tens to hundreds of nodes, and has
> > >  the ability to load data from Apache Kafka and Apache
> > >  Hadoop, among other data sources. Druid offers two query
> > >  languages: a SQL dialect (powered by Apache Calcite) and a
> > >  JSON-over-HTTP API.
> > > 
> > >  Druid was originally developed to power a slice-and-dice
> > >  analytical UI built on top of large event streams. The
> > >  original use case for Druid targeted ingest rates of
> > >  millions of records/sec, retention of over a year of data,
> > >  and query latencies of sub-second to a few seconds. Many
> > >  people can benefit from such capability, and many already
> > >  have (see http://druid.io/druid-powered.html). In addition,
> > >  new use cases have emerged since Druid's original
> > >  development, such as OLAP acceleration of data warehouse
> > >  tables and more highly concurrent applications operating
> > >  with relatively narrower queries.
> > > 
> > >  == Background ==
> > > 
> > >  Druid is a data store designed for fast analytics. It would
> > >  typically be used in lieu of more general purpose query
> > >  systems like Hadoop MapReduce or Spark when query latency is
> > >  of the utmost importance. Druid is often used as a data
> > >  store for powering GUI analytical applications.
> > > 
> > >  The buzzwordy description of Druid is a high-performance,
> > >  column-oriented, distributed data store. What we mean by
> > >  this is:
> > > 
> > >  * "high performance": Druid aims to provide low query
> > >   latency and high ingest rates possible.
> > >  * "column-oriente

Re: [VOTE] Accept Druid into the Apache Incubator

2018-02-26 Thread Bolke de Bruin 
+1 (non-binding)

> On 26 Feb 2018, at 20:53, Ashutosh Chauhan  wrote:
> 
> +1
> 
> On Sun, Feb 25, 2018 at 11:51 PM, Hao Chen  wrote:
> 
>> +1 (non-binding)
>> 
>> Hao Chen
>> 
>> *PMC & Committer, Apache Eagle*
>> 
>> On Mon, Feb 26, 2018 at 3:02 PM, ShaoFeng Shi 
>> wrote:
>> 
>>> +1 (non-binding)
>>> 
>>> 2018-02-26 14:16 GMT+08:00 Zhanhui Li :
>>> 
 +1 (non-binding)
 
 Glad to see Druid in Apache community.
 
> 在 2018年2月26日，下午1:45，Bhupesh Chawda  写道：
> 
> +1 (non-binding)
> 
> ~ Bhupesh
> 
> 
> ___
> 
> Bhupesh Chawda
> 
> E: bhup...@datatorrent.com  |
>> Twitter:
 @bhupeshsc
> 
> www.datatorrent.com   |
>> apex.apache.org
>>> <
 http://apex.apache.org/>
> 
> 
> 
> On Mon, Feb 26, 2018 at 11:12 AM, Chinmay Kolhatkar <
>>> chin...@apache.org
 >
> wrote:
> 
>> +1
>> 
>> On 2018/02/24 09:02:41, Ted Dunning  wrote:
>>> +1
>>> 
>>> 
>>> 
>>> On Thu, Feb 22, 2018 at 11:03 AM, Julian Hyde 
 wrote:
>>> 
 Hi all,
 
 After some discussion on the Druid proposal[1], I'd like to
 start a vote on accepting Druid into the Apache Incubator,
 per the ASF policy[2] and voting rules[3].
 
 A vote for accepting a new Apache Incubator podling is a
 majority vote for which only Incubator PMC member votes are
 binding. Votes from other people are also welcome as an
 indication of people's enthusiasm (or lack thereof).
 
 Please do not use this VOTE thread for discussions.  If
 needed, start a new thread instead.
 
 This vote will run for at least 72 hours. Please VOTE as
 follows:
 [ ] +1 Accept Druid into the Apache Incubator
 [ ] +0 Abstain
 [ ] -1 Do not accept Druid into the Apache Incubator
   because ...
 
 The proposal is listed below, but you can also access it on
 the wiki[4].
 
 Julian
 
 [1] https://lists.apache.org/thread.html/
>> b95f90a30b6e8587e9b108f368b07c
 1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
 
 [2] https://incubator.apache.org/policy/incubation.html#
 approval_of_proposal_by_sponsor
 
 [3] http://www.apache.org/foundation/voting.html
 
 [4] https://wiki.apache.org/incubator/DruidProposal
 
 
 
 
 
 = Druid Proposal =
 
 == Abstract ==
 
 Druid is a high-performance, column-oriented, distributed
 data store.
 
 == Proposal ==
 
 Druid is an open source data store designed for real-time
 exploratory analytics on large data sets. Druid's key
 features are a column-oriented storage layout, a distributed
 shared-nothing architecture, and ability to generate and
 leverage indexing and caching structures. Druid is typically
 deployed in clusters of tens to hundreds of nodes, and has
 the ability to load data from Apache Kafka and Apache
 Hadoop, among other data sources. Druid offers two query
 languages: a SQL dialect (powered by Apache Calcite) and a
 JSON-over-HTTP API.
 
 Druid was originally developed to power a slice-and-dice
 analytical UI built on top of large event streams. The
 original use case for Druid targeted ingest rates of
 millions of records/sec, retention of over a year of data,
 and query latencies of sub-second to a few seconds. Many
 people can benefit from such capability, and many already
 have (see http://druid.io/druid-powered.html). In addition,
 new use cases have emerged since Druid's original
 development, such as OLAP acceleration of data warehouse
 tables and more highly concurrent applications operating
 with relatively narrower queries.
 
 == Background ==
 
 Druid is a data store designed for fast analytics. It would
 typically be used in lieu of more general purpose query
 systems like Hadoop MapReduce or Spark when query latency is
 of the utmost importance. Druid is often used as a data
 store for powering GUI analytical applications.
 
 The buzzwordy description of Druid is a high-performance,
 column-oriented, distributed data store. What we mean by
 this is:
 
 * "high performance": Druid aims to provide low query
 latency and high ingest rates possible.
 * "column-oriented": Druid stores data in a column-oriented
 format, like most other systems designed for analyt

Re: [VOTE] Accept Druid into the Apache Incubator

2018-02-26 Thread Suneel Marthi 
+1 - its great to see Druid coming to Apache

On Mon, Feb 26, 2018 at 9:23 PM, Bolke de Bruin  wrote:

> +1 (non-binding)
>
> > On 26 Feb 2018, at 20:53, Ashutosh Chauhan  wrote:
> >
> > +1
> >
> > On Sun, Feb 25, 2018 at 11:51 PM, Hao Chen  wrote:
> >
> >> +1 (non-binding)
> >>
> >> Hao Chen
> >>
> >> *PMC & Committer, Apache Eagle*
> >>
> >> On Mon, Feb 26, 2018 at 3:02 PM, ShaoFeng Shi 
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> 2018-02-26 14:16 GMT+08:00 Zhanhui Li :
> >>>
>  +1 (non-binding)
> 
>  Glad to see Druid in Apache community.
> 
> > 在 2018年2月26日，下午1:45，Bhupesh Chawda  写道：
> >
> > +1 (non-binding)
> >
> > ~ Bhupesh
> >
> >
> > ___
> >
> > Bhupesh Chawda
> >
> > E: bhup...@datatorrent.com  |
> >> Twitter:
>  @bhupeshsc
> >
> > www.datatorrent.com   |
> >> apex.apache.org
> >>> <
>  http://apex.apache.org/>
> >
> >
> >
> > On Mon, Feb 26, 2018 at 11:12 AM, Chinmay Kolhatkar <
> >>> chin...@apache.org
>  >
> > wrote:
> >
> >> +1
> >>
> >> On 2018/02/24 09:02:41, Ted Dunning  wrote:
> >>> +1
> >>>
> >>>
> >>>
> >>> On Thu, Feb 22, 2018 at 11:03 AM, Julian Hyde 
>  wrote:
> >>>
>  Hi all,
> 
>  After some discussion on the Druid proposal[1], I'd like to
>  start a vote on accepting Druid into the Apache Incubator,
>  per the ASF policy[2] and voting rules[3].
> 
>  A vote for accepting a new Apache Incubator podling is a
>  majority vote for which only Incubator PMC member votes are
>  binding. Votes from other people are also welcome as an
>  indication of people's enthusiasm (or lack thereof).
> 
>  Please do not use this VOTE thread for discussions.  If
>  needed, start a new thread instead.
> 
>  This vote will run for at least 72 hours. Please VOTE as
>  follows:
>  [ ] +1 Accept Druid into the Apache Incubator
>  [ ] +0 Abstain
>  [ ] -1 Do not accept Druid into the Apache Incubator
>    because ...
> 
>  The proposal is listed below, but you can also access it on
>  the wiki[4].
> 
>  Julian
> 
>  [1] https://lists.apache.org/thread.html/
> >> b95f90a30b6e8587e9b108f368b07c
>  1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
> 
>  [2] https://incubator.apache.org/policy/incubation.html#
>  approval_of_proposal_by_sponsor
> 
>  [3] http://www.apache.org/foundation/voting.html
> 
>  [4] https://wiki.apache.org/incubator/DruidProposal
> 
> 
> 
> 
> 
>  = Druid Proposal =
> 
>  == Abstract ==
> 
>  Druid is a high-performance, column-oriented, distributed
>  data store.
> 
>  == Proposal ==
> 
>  Druid is an open source data store designed for real-time
>  exploratory analytics on large data sets. Druid's key
>  features are a column-oriented storage layout, a distributed
>  shared-nothing architecture, and ability to generate and
>  leverage indexing and caching structures. Druid is typically
>  deployed in clusters of tens to hundreds of nodes, and has
>  the ability to load data from Apache Kafka and Apache
>  Hadoop, among other data sources. Druid offers two query
>  languages: a SQL dialect (powered by Apache Calcite) and a
>  JSON-over-HTTP API.
> 
>  Druid was originally developed to power a slice-and-dice
>  analytical UI built on top of large event streams. The
>  original use case for Druid targeted ingest rates of
>  millions of records/sec, retention of over a year of data,
>  and query latencies of sub-second to a few seconds. Many
>  people can benefit from such capability, and many already
>  have (see http://druid.io/druid-powered.html). In addition,
>  new use cases have emerged since Druid's original
>  development, such as OLAP acceleration of data warehouse
>  tables and more highly concurrent applications operating
>  with relatively narrower queries.
> 
>  == Background ==
> 
>  Druid is a data store designed for fast analytics. It would
>  typically be used in lieu of more general purpose query
>  systems like Hadoop MapReduce or Spark when query latency is
>  of the utmost importance. Druid is often used as a data
>  store for powering GUI analytical applications.
> 
>  The buzzwordy description of Druid is a high-performa

Re: [IP CLEARANCE] Apache Ignite - Genetic Algorithms Grid

2018-02-26 Thread Denis Magda 
With no -1 votes being cast, this IP Clearance vote passes by lazy
consensus. Further information on merging and code status will be posted on
the d...@ignite.apache.org list.

--
Denis

On Thu, Feb 22, 2018 at 3:02 PM, Denis Magda  wrote:

> Apache Ignite is receiving a donation developed outside of the community.
>
> Please refer to the IP-clearance form for details:
> http://incubator.apache.org/ip-clearance/ga-grid-ignite.html
>
> Please vote to approve the donation.
>
> It's a lazy consensus majority vote, open for at least 72 hours.
>
> Regards,
> Denis
>
>

[RESULT][IP CLEARANCE] Apache Ignite - Genetic Algorithms Grid

2018-02-26 Thread Denis Magda 
This message officially closes the IP Clearance vote took place on
general@incubator:
http://apache-incubator-general.996316.n3.nabble.com/IP-CLEARANCE-Apache-Ignite-Genetic-Algorithms-Grid-td57791.html


The IP Clearance vote passed by lazy consensus.

[jira] [Created] (INCUBATOR-210) Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义

2018-02-26 Thread renyingxin (JIRA) 
renyingxin created INCUBATOR-210:


 Summary: Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义
 Key: INCUBATOR-210
 URL: https://issues.apache.org/jira/browse/INCUBATOR-210
 Project: Incubator
  Issue Type: Task
Reporter: renyingxin


Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义,也就是类似[0,200),[200,400）这种时延分布的统计，平均时延可能会掩盖系统的部分问题，比如部分高延时，但是被正常平均值掩盖了



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-210) Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义

2018-02-26 Thread Michael Vorburger (JIRA) 

[ 
https://issues.apache.org/jira/browse/INCUBATOR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378105#comment-16378105
 ] 

Michael Vorburger commented on INCUBATOR-210:
-

Could someone with more JIRA privileges than I seem to have here close this 
issue and block [~renyingxin]'s account? (Or elevate my JIRA permission so that 
I can do either or both.)

> Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义
> ---
>
> Key: INCUBATOR-210
> URL: https://issues.apache.org/jira/browse/INCUBATOR-210
> Project: Incubator
>  Issue Type: Task
>Reporter: renyingxin
>Priority: Major
>
> Servicecomb当前性能统计不支持时延分布的统计，这个对于业务有重要意义,也就是类似[0,200),[200,400）这种时延分布的统计，平均时延可能会掩盖系统的部分问题，比如部分高延时，但是被正常平均值掩盖了



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org