bq. out of which 1.2.4 is released Actually 1.2.4 has already been released. 1.1.8 RC is being voted upon.
FYI On Tue, Dec 13, 2016 at 5:48 PM, Sangjin Lee <sjl...@gmail.com> wrote: > According to HBASE-16749, the fix went into HBase 1.2.4 and 1.1.8 (out of > which 1.2.4 is released). To resolve this issue, we'd need to upgrade to > 1.2.4 or later. > > > Sangjin > > On Tue, Dec 13, 2016 at 3:41 PM, Vrushali Channapattan < > vchannapat...@twitter.com> wrote: > > > Yes, I think bumping up the hbase version to 1.2 should help with this > > build time taken issue. I will start looking into this upgrade right > > away. > > > > Thanks > > Vrushali > > > > > On Dec 13, 2016, at 3:02 PM, Li Lu <llu.u...@gmail.com> wrote: > > > > > > I could not reproduce this issue locally but this may be related to > some > > local maven repos. This may be related to the private repo issues of > HBase? > > If this is the case, bumping up hbase dependency version of YARN timeline > > module might be helpful? > > > > > > +Sangjin, Vrushali, and Joep: In YARN-5976 we’re proposing to bump up > > HBase dependency version into 1.2. Shall we prioritize that JIRA? Thanks! > > > > > > Li Lu > > > > > >> On Dec 13, 2016, at 14:43, Wangda Tan <wheele...@gmail.com> wrote: > > >> > > >> Hi folks, > > >> > > >> It looks like HBASE-16749 is fixed, and Phoenix version is updated > (per > > >> Li). But I'm still experiencing slow build of ATSv2 component: > > >> > > >> [INFO] Apache Hadoop YARN ................................. SUCCESS [ > > >> 1.378 s] > > >> [INFO] Apache Hadoop YARN API ............................. SUCCESS [ > > >> 10.559 s] > > >> [INFO] Apache Hadoop YARN Common .......................... SUCCESS [ > > >> 6.993 s] > > >> [INFO] Apache Hadoop YARN Server .......................... SUCCESS [ > > >> 0.057 s] > > >> [INFO] Apache Hadoop YARN Server Common ................... SUCCESS [ > > >> 2.266 s] > > >> [INFO] Apache Hadoop YARN NodeManager ..................... SUCCESS [ > > >> 4.075 s] > > >> [INFO] Apache Hadoop YARN Web Proxy ....................... SUCCESS [ > > >> 0.924 s] > > >> [INFO] Apache Hadoop YARN ApplicationHistoryService ....... SUCCESS [ > > >> 1.549 s] > > >> [INFO] Apache Hadoop YARN Timeline Service ................ SUCCESS > > [05:14 > > >> min] > > >> [INFO] Apache Hadoop YARN ResourceManager ................. SUCCESS [ > > >> 8.554 s] > > >> [INFO] Apache Hadoop YARN Server Tests .................... SUCCESS [ > > >> 1.561 s] > > >> [INFO] Apache Hadoop YARN Client .......................... SUCCESS [ > > >> 1.321 s] > > >> [INFO] Apache Hadoop YARN SharedCacheManager .............. SUCCESS [ > > >> 0.843 s] > > >> [INFO] Apache Hadoop YARN Timeline Plugin Storage ......... SUCCESS [ > > >> 0.949 s] > > >> [INFO] Apache Hadoop YARN Timeline Service HBase tests .... SUCCESS [ > > >> 3.137 s] > > >> [INFO] Apache Hadoop YARN Applications .................... SUCCESS [ > > >> 0.055 s] > > >> [INFO] Apache Hadoop YARN DistributedShell ................ SUCCESS [ > > >> 0.807 s] > > >> [INFO] Apache Hadoop YARN Unmanaged Am Launcher ........... SUCCESS [ > > >> 0.602 s] > > >> [INFO] Apache Hadoop YARN Site ............................ SUCCESS [ > > >> 0.060 s] > > >> [INFO] Apache Hadoop YARN Registry ........................ SUCCESS [ > > >> 0.910 s] > > >> [INFO] Apache Hadoop YARN UI .............................. SUCCESS [ > > >> 0.072 s] > > >> [INFO] Apache Hadoop YARN Project ......................... SUCCESS [ > > >> 0.749 s] > > >> [INFO] > > >> ------------------------------------------------------------ > > ------------ > > >> [INFO] BUILD SUCCESS > > >> [INFO] > > >> ------------------------------------------------------------ > > ------------ > > >> [INFO] Total time: 06:02 min > > >> > > >> This doesn't happen every time when I run build on latest Hadoop > trunk, > > but > > >> I can often see this happens. > > >> > > >> Thoughts about how to solve it? > > >> > > >> Thanks, > > >> Wangda > > >> > > >> > > >> > > >>> On Tue, Oct 4, 2016 at 6:50 PM, Sangjin Lee <sjl...@gmail.com> > wrote: > > >>> > > >>> Thanks Wangda. > > >>> > > >>> To answer Steve's question, I don't think maven downloads anything > from > > >>> that location (it's a very old content). It just does a wasted effort > > by > > >>> hitting this repo. > > >>> > > >>>> On Mon, Oct 3, 2016 at 10:25 AM, Wangda Tan <wheele...@gmail.com> > > wrote: > > >>>> > > >>>> Filed: https://issues.apache.org/jira/browse/HBASE-16749 > > >>>> > > >>>>> On Mon, Oct 3, 2016 at 10:18 AM, Wangda Tan <wheele...@gmail.com> > > wrote: > > >>>>> > > >>>>> Thanks Sangjin/Ted/Steve for your comments/suggestions, I will > file a > > >>>>> HBase JIRA later. > > >>>>> > > >>>>> Regards, > > >>>>> Wangda > > >>>>> > > >>>>> On Mon, Oct 3, 2016 at 4:43 AM, Steve Loughran < > > ste...@hortonworks.com> > > >>>>> wrote: > > >>>>> > > >>>>>> HBase really ought to have a profile for D/Ling from somewhere > like > > >>>> this, > > >>>>>> and, perhaps, list the ASF snapsphot repo first > > >>>>>> > > >>>>>>> On 1 Oct 2016, at 17:37, Wangda Tan <wheele...@gmail.com> wrote: > > >>>>>>> > > >>>>>>> Hi YARN-dev, > > >>>>>>> > > >>>>>>> (cc common-dev), > > >>>>>>> > > >>>>>>> YARN timeline service currently sometimes downloads > > >>>> maven-metadata.xml > > >>>>>> from > > >>>>>>> a personal apache site, log looks like: > > >>>>>>> > > >>>>>>> [INFO] ------------------------------ > > ------------------------------ > > >>>>>>> ------------ > > >>>>>>> [INFO] Building Apache Hadoop YARN Timeline Service > > >>>>>> 3.0.0-alpha2-SNAPSHOT > > >>>>>>> [INFO] ------------------------------ > > ------------------------------ > > >>>>>>> ------------ > > >>>>>>> Downloading: http://conjars.org/repo/org/ap > > >>>> ache/hadoop/hadoop-client/3. > > >>>>>>> 0.0-alpha2-SNAPSHOT/maven-metadata.xml > > >>>>>>> ... > > >>>>>>> Downloading: http://people.apache.org/~ > > garyh/mvn/org/apache/hadoop/ > > >>>>>>> hadoop-client/3.0.0-alpha2-SNAPSHOT/maven-metadata.xml > > >>>>>>> ... > > >>>>>>> Downloading: http://people.apache.org/~ > > garyh/mvn/org/apache/hadoop/ > > >>>>>>> hadoop-client/3.0.0-alpha2-SNAPSHOT/maven-metadata.xml > > >>>>>>> > > >>>>>>> I noticed this happens for a while, I'm not sure if it causes by > my > > >>>>>> local > > >>>>>> > > >>>>>> is it actually D/Lin'g the files? Or is it looking for them and > then > > >>>>>> going on to try the next repo? > > >>>>>> > > >>>>> > > >>>>> > > >>>> > > >>> > > >>> > > > > > >
