date:20160915

RE: SQL Reference Manuals updates

2016-09-15 Thread Dave Birdsall

Hi,

I'll direct everyone on this discussion thread to this pull request:
https://github.com/apache/incubator-trafodion/pull/707. Perhaps we can
continue our discussion there.

You can see what I propose to do and comment on it. Note that the
revisions.txt file (which contains the Release History) is shared among all
documents. Each document has a separate "New and Changed" information; I've
only modified the one for the SQL Reference Manual. Before releasing, the
same section will need changing in other manuals as appropriate.

Dave

-Original Message-
From: Carol Pearson [mailto:carol.pearson...@gmail.com]
Sent: Thursday, September 15, 2016 11:45 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: SQL Reference Manuals updates

Hi,

Release date is good enough, in my opinion. If someone is interested
particulars, then we have that history in git, though that's developer-level
function, not user-level.

-Carol P.


---
Email:carol.pearson...@gmail.com
Twitter:  @CarolP222
---

On Thu, Sep 15, 2016 at 11:17 AM, Steve Varnau 
wrote:

> I would have thought that the version of the documents (2.1) is good
> to have, and the release info (release dates) should be on the web
> site, rather than in the content of each document.
>
> The doc page
> (http://trafodion.incubator.apache.org/documentation.html)
> indicates that 2.0 is released, and the latest (in development)
> section points to the 2.1 docs.
>
> The release manager task list
> (https://cwiki.apache.org/confluence/display/TRAFODION/
> Create+Release#CreateRelease-UpdateProjectWebSite)
> includes updating release info web page:
> http://trafodion.incubator.apache.org/download.html
>
> But not content of the docs.
>
> --Steve
>
> > -Original Message-
> > From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> > Sent: Thursday, September 15, 2016 11:00 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: SQL Reference Manuals updates
> >
> > Hi Carol,
> >
> > I'm wondering if the revision date should be the date of the
> > release? If so, the release manager should be the one to update it.
> >
> > For the moment, I've written "TBD" here.
> >
> > Dave
> >
> > -Original Message-
> > From: Carol Pearson [mailto:carol.pearson...@gmail.com]
> > Sent: Thursday, September 15, 2016 10:58 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: SQL Reference Manuals updates
> >
> > Hi Dave
> >
> > It seems like the "update the revision history" step should be part
> > of
> the
> > release manager checklist that Roberta and Steve put together?
> > Nobody knows if s/he is the last person to update it
> >
> > The alternative is every update is presumed to be the last, so each
> person
> > updates it as part of the change..
> >
> > -Carol P.
> >
> > ---
> > Email:carol.pearson...@gmail.com
> > Twitter:  @CarolP222
> > ---
> >
> > On Thu, Sep 15, 2016 at 9:13 AM, Dave Birdsall
> > 
> > wrote:
> >
> > > Hi,
> > >
> > >
> > >
> > > I’m about to add documentation to the SQL Reference Manual for the
> > > incremental UPDATE STATISTICS (IUS) feature for Trafodion 2.1.
> > >
> > >
> > >
> > > I’m guessing I’m the first person to do so for this release.
> > >
> > >
> > >
> > > One thing I notice is that the Revision History doesn’t have an
> > > entry for 2.1. I propose to add one, with a notation that this is
> > > a work in progress.
> > > The last person to update before the release should remove that
> > > note and set the date of the release.
> > >
> > >
> > >
> > > Section 1.2 New and Changed Information appears to have stuff for
> > > the previous release (2.0, 2.0.1). I propose to remove all of
> > > this. But will add an entry for incremental update statistics.
> > >
> > >
> > >
> > > Does this sound right to you?
> > >
> > >
> > >
> > > Are there other general sections of this kind that need updating
> > > for the next release?
> > >
> > >
> > >
> > > Thanks,
> > >
> > >
> > >
> > > Dave
> > >
>

RE: SQL Reference Manuals updates

2016-09-15 Thread Dave Birdsall

Hi Carol,

I'm wondering if the revision date should be the date of the release? If so,
the release manager should be the one to update it.

For the moment, I've written "TBD" here.

Dave

-Original Message-
From: Carol Pearson [mailto:carol.pearson...@gmail.com]
Sent: Thursday, September 15, 2016 10:58 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: SQL Reference Manuals updates

Hi Dave

It seems like the "update the revision history" step should be part of the
release manager checklist that Roberta and Steve put together?  Nobody knows
if s/he is the last person to update it

The alternative is every update is presumed to be the last, so each person
updates it as part of the change..

-Carol P.

---
Email:carol.pearson...@gmail.com
Twitter:  @CarolP222
---

On Thu, Sep 15, 2016 at 9:13 AM, Dave Birdsall 
wrote:

> Hi,
>
>
>
> I’m about to add documentation to the SQL Reference Manual for the
> incremental UPDATE STATISTICS (IUS) feature for Trafodion 2.1.
>
>
>
> I’m guessing I’m the first person to do so for this release.
>
>
>
> One thing I notice is that the Revision History doesn’t have an entry
> for 2.1. I propose to add one, with a notation that this is a work in
> progress.
> The last person to update before the release should remove that note
> and set the date of the release.
>
>
>
> Section 1.2 New and Changed Information appears to have stuff for the
> previous release (2.0, 2.0.1). I propose to remove all of this. But
> will add an entry for incremental update statistics.
>
>
>
> Does this sound right to you?
>
>
>
> Are there other general sections of this kind that need updating for
> the next release?
>
>
>
> Thanks,
>
>
>
> Dave
>

Re: SQL Reference Manuals updates

2016-09-15 Thread Carol Pearson

Hi Dave

It seems like the "update the revision history" step should be part of the
release manager checklist that Roberta and Steve put together?  Nobody
knows if s/he is the last person to update it

The alternative is every update is presumed to be the last, so each person
updates it as part of the change..

-Carol P.

---
Email:carol.pearson...@gmail.com
Twitter:  @CarolP222
---

On Thu, Sep 15, 2016 at 9:13 AM, Dave Birdsall 
wrote:

> Hi,
>
>
>
> I’m about to add documentation to the SQL Reference Manual for the
> incremental UPDATE STATISTICS (IUS) feature for Trafodion 2.1.
>
>
>
> I’m guessing I’m the first person to do so for this release.
>
>
>
> One thing I notice is that the Revision History doesn’t have an entry for
> 2.1. I propose to add one, with a notation that this is a work in progress.
> The last person to update before the release should remove that note and
> set the date of the release.
>
>
>
> Section 1.2 New and Changed Information appears to have stuff for the
> previous release (2.0, 2.0.1). I propose to remove all of this. But will
> add an entry for incremental update statistics.
>
>
>
> Does this sound right to you?
>
>
>
> Are there other general sections of this kind that need updating for the
> next release?
>
>
>
> Thanks,
>
>
>
> Dave
>

RE: Trafodion master Daily Test Result - 332 - Still Failing

2016-09-15 Thread Sean Broeder

RE: Trafodion master Daily Test Result - 332 - Still Failing

In this case we are trying to drop a table and we want to disable all the
regions.  Before doing so, each region makes sure it allows any pending
transactions to complete before closing.  One region finds an active
transactional scanner and continues to wait for the scanner to clear.



2016-09-15 10:26:55,574 INFO
[PriorityRpcServer.handler=11,queue=1,port=16020]
transactional.SplitBalanceHelper: scannersListClear Active Scanner found,
ScannerId: 0 Txid: 1054 Region:
TRAFODION.SCH.T106A,\x00\x00\x00\x02\x00\x00\x00\x00,1473934644524.39d9ea92d6f2109a682f66f38a795b79.

2016-09-15 10:26:55,726 INFO
[PriorityRpcServer.handler=8,queue=0,port=16020]
transactional.SplitBalanceHelper: scannersListClear Active Scanner found,
ScannerId: 0 Txid: 1054 Region:
TRAFODION.SCH.T106A,\x00\x00\x00\x02\x00\x00\x00\x00,1473934644524.39d9ea92d6f2109a682f66f38a795b79.

2016-09-15 10:26:56,075 INFO
[PriorityRpcServer.handler=11,queue=1,port=16020]
transactional.SplitBalanceHelper: scannersListClear Active Scanner found,
ScannerId: 0 Txid: 1054 Region:
TRAFODION.SCH.T106A,\x00\x00\x00\x02\x00\x00\x00\x00,1473934644524.39d9ea92d6f2109a682f66f38a795b79.

2016-09-15 10:26:56,226 INFO
[PriorityRpcServer.handler=8,queue=0,port=16020]
transactional.SplitBalanceHelper: scannersListClear Active Scanner found,
ScannerId: 0 Txid: 1054 Region:
TRAFODION.SCH.T106A,\x00\x00\x00\x02\x00\x00\x00\x00,1473934644524.39d9ea92d6f2109a682f66f38a795b79.



Since it doesn’t clear it essentially locks up the drop forever.  I know
there was a bug for a while where a transaction’s own scanner would block a
drop, but a change was made to allow the close to go through if the scanner
was for our own transaction.  The logging doesn’t show the transaction of
the drop (that I see).



I think Prashanth should have a look at this.



Regards,

Sean



*From:* Sean Broeder [mailto:sean.broe...@esgyn.com]
*Sent:* Thursday, September 15, 2016 9:47 AM
*To:* 'Narain Arvind' ; '
dev@trafodion.incubator.apache.org' 
*Subject:* RE: Trafodion master Daily Test Result - 332 - Still Failing



Sure.  I’ll have a look



*From:* Narain Arvind [mailto:narain.arv...@gmail.com
]
*Sent:* Thursday, September 15, 2016 9:22 AM
*To:* dev@trafodion.incubator.apache.org
*Cc:* Sean Broeder 
*Subject:* RE: Trafodion master Daily Test Result - 332 - Still Failing



Timeout in core-regress-executor-hdp is during drop of table T106A.

https://jenkins.esgyn.com/job/core-regress-executor-hdp/369/console

Messages related to transactional.SplitBalancerHelper repeated in Region
Server logs.

Sean could you please take a look ? Thanks.

http://traf-testlogs.esgyn.com/Daily-master/332/regress-executor-hdp/hbase-logs/hbase-hbase-regionserver-slave-ahw23.log

2016-09-15 10:25:01,806 INFO  [RS_CLOSE_REGION-slave-ahw23:16020-2]
regionserver.HRegion: Closed
TRAFODION.SCH.T106A,\x00\x00\x00\x01\x00\x00\x00\x00,1473934644524.f32b6c8d8f3932729b9824f51a95a63e.

2016-09-15 10:25:02,059 INFO
[PriorityRpcServer.handler=8,queue=0,port=16020]
transactional.SplitBalanceHelper: scannersListClear Active Scanner found,
ScannerId: 0 Txid: 1054 Region:
TRAFODION.SCH.T106A,\x00\x00\x00\x02\x00\x00\x00\x00,1473934644524.39d9ea92d6f2109a682f66f38a795b79.

…

2016-09-15 10:31:37,204 INFO  [regionserver/
slave-ahw23.trafodion.org/172.31.3.234:16020.leaseChecker]
regionserver.RSRpcServices: Scanner 12971 lease expired on region
TRAFODION.SCH.T106A,\x00\x00\x00\x01\x00\x00\x00\x00,1473934644524.f32b6c8d8f3932729b9824f51a95a63e.

2016-09-15 10:31:37,205 ERROR [regionserver/
slave-ahw23.trafodion.org/172.31.3.234:16020.leaseChecker]
regionserver.RSRpcServices: Closing scanner for
TRAFODION.SCH.T106A,\x00\x00\x00\x01\x00\x00\x00\x00,1473934644524.f32b6c8d8f3932729b9824f51a95a63e.

org.apache.hadoop.hbase.NotServingRegionException: Region
TRAFODION.SCH.T106A,\x00\x00\x00\x01\x00\x00\x00\x00,1473934644524.f32b6c8d8f3932729b9824f51a95a63e.
is not online on slave-ahw23.trafodion.org,16020,1473931541282

at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2898)

at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2875)

at
org.apache.hadoop.hbase.regionserver.RSRpcServices$ScannerListener.leaseExpired(RSRpcServices.java:285)

at org.apache.hadoop.hbase.regionserver.Leases.run(Leases.java:121)

at java.lang.Thread.run(Thread.java:745)

…

2016-09-15 11:29:49,857 INFO
[PriorityRpcServer.handler=1,queue=1,port=16020]
transactional.SplitBalanceHelper: scannersListClear Active Scanner found,
ScannerId: 0 Txid: 1054 Region:
TRAFODION.SCH.T106A,\x00\x00\x00\x02\x00\x00\x00\x00,1473934644524.39d9ea92d6f2109a682f66f38a795b79.

2016-09-15 11:29:49,864 INFO
[PriorityRpcServer.handler=19,queue=1,port=16020]
transactional.SplitBalanceHelper:

SQL Reference Manuals updates

2016-09-15 Thread Dave Birdsall

Hi,



I’m about to add documentation to the SQL Reference Manual for the
incremental UPDATE STATISTICS (IUS) feature for Trafodion 2.1.



I’m guessing I’m the first person to do so for this release.



One thing I notice is that the Revision History doesn’t have an entry for
2.1. I propose to add one, with a notation that this is a work in progress.
The last person to update before the release should remove that note and
set the date of the release.



Section 1.2 New and Changed Information appears to have stuff for the
previous release (2.0, 2.0.1). I propose to remove all of this. But will
add an entry for incremental update statistics.



Does this sound right to you?



Are there other general sections of this kind that need updating for the
next release?



Thanks,



Dave

Trafodion master Daily Test Result - 332 - Still Failing

2016-09-15 Thread steve . varnau

Daily Automated Testing master

Jenkins Job:   https://jenkins.esgyn.com/job/Check-Daily-master/332/
Archived Logs: http://traf-testlogs.esgyn.com/Daily-master/332
Bld Downloads: http://traf-builds.esgyn.com

Changes since previous daily build:
[dbirdsall] [TRAFODION-2187] Fix DROP SCHEMA CASCADE when sample tables are 
present

[anoop.sharma] jira TRAFODION-2184 groupby/orderby construct extensions and 
enablement

[hzeller] [TRAFODION-] Trafodion on HDP 2.3 needs yarn client in class path

[anoop.sharma] jira TRAFODION-2184 additional changes



Test Job Results:

FAILURE core-regress-executor-hdp (2 hr 20 min)
SUCCESS build-rh6-master-debug (30 min)
SUCCESS build-rh6-master-release (35 min)
SUCCESS core-regress-charsets-cdh (44 min)
SUCCESS core-regress-charsets-hdp (43 min)
SUCCESS core-regress-compGeneral-cdh (41 min)
SUCCESS core-regress-compGeneral-hdp (1 hr 1 min)
SUCCESS core-regress-core-cdh (1 hr 1 min)
SUCCESS core-regress-core-hdp (1 hr 25 min)
SUCCESS core-regress-executor-cdh (1 hr 14 min)
SUCCESS core-regress-fullstack2-cdh (10 min)
SUCCESS core-regress-fullstack2-hdp (21 min)
SUCCESS core-regress-hive-cdh (49 min)
SUCCESS core-regress-hive-hdp (48 min)
SUCCESS core-regress-privs1-cdh (50 min)
SUCCESS core-regress-privs1-hdp (53 min)
SUCCESS core-regress-privs2-cdh (51 min)
SUCCESS core-regress-privs2-hdp (1 hr 20 min)
SUCCESS core-regress-qat-cdh (29 min)
SUCCESS core-regress-qat-hdp (38 min)
SUCCESS core-regress-seabase-cdh (1 hr 27 min)
SUCCESS core-regress-seabase-hdp (1 hr 54 min)
SUCCESS core-regress-udr-cdh (25 min)
SUCCESS core-regress-udr-hdp (40 min)
SUCCESS jdbc_test-cdh (30 min)
SUCCESS jdbc_test-hdp (48 min)
SUCCESS phoenix_part1_T2-cdh (1 hr 7 min)
SUCCESS phoenix_part1_T2-hdp (1 hr 19 min)
SUCCESS phoenix_part1_T4-cdh (1 hr 2 min)
SUCCESS phoenix_part1_T4-hdp (1 hr 23 min)
SUCCESS phoenix_part2_T2-cdh (1 hr 2 min)
SUCCESS phoenix_part2_T2-hdp (1 hr 19 min)
SUCCESS phoenix_part2_T4-cdh (1 hr 0 min)
SUCCESS phoenix_part2_T4-hdp (1 hr 19 min)
SUCCESS pyodbc_test-cdh (11 min)
SUCCESS pyodbc_test-hdp (27 min)

RE: SQL Reference Manuals updates

RE: SQL Reference Manuals updates

Re: SQL Reference Manuals updates

RE: Trafodion master Daily Test Result - 332 - Still Failing

SQL Reference Manuals updates

Trafodion master Daily Test Result - 332 - Still Failing

6 matches

Site Navigation

Mail list logo

Footer information