> On Dec. 13, 2018, 4:54 a.m., Rajitha R wrote: > > lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java > > Lines 617 (patched) > > <https://reviews.apache.org/r/69554/diff/1/?file=2113075#file2113075line617> > > > > can this be moved to the if condition? this would ensure there is > > atleast one row
we should rely on this to throw exception. If resultset has no rows or for any other type of error or exception we are relying on finsihed_query table to fetch query details. > On Dec. 13, 2018, 4:54 a.m., Rajitha R wrote: > > lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java > > Lines 623 (patched) > > <https://reviews.apache.org/r/69554/diff/1/?file=2113075#file2113075line623> > > > > Can this be shifted to final block? Also DBUtils.close(stmt) and > > DBUtils.close(rs) makes more sense. This applies here and everywhere else DBUtils.close(stmt) and DBUtils.close(rs) throws SQLException, not a good idea to have it in final block. > On Dec. 13, 2018, 4:54 a.m., Rajitha R wrote: > > lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java > > Line 390 (original), 827 (patched) > > <https://reviews.apache.org/r/69554/diff/1/?file=2113075#file2113075line827> > > > > while all of existing code in lensserverdao is using commons db utils, > > any particular reason we are using vanilla java code in the new code? to > > maintain consistency in the code, it seems better to use the db utils > > library to define the new apis as well, IMO db utils api sunc as DBRunner that we are using currently perofrms one to one serialisaition between java class and mysql table. In case of query context class and LensSession.PersistInfo it will add unnecessary complexity of modifying these table definition as and when we introduce new filed in these classes. > On Dec. 13, 2018, 4:54 a.m., Rajitha R wrote: > > lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java > > Lines 3680 (patched) > > <https://reviews.apache.org/r/69554/diff/1/?file=2113076#file2113076line3680> > > > > Why can't we put this code in existing validatesession in > > Baselensservice than defining a new api altogether? > > Ankit Kailaswar wrote: > moved. SessionValidator interface is better place for this api, moved it there. > On Dec. 13, 2018, 4:54 a.m., Rajitha R wrote: > > lens-server/src/main/java/org/apache/lens/server/session/HiveSessionService.java > > Line 579 (original), 616 (patched) > > <https://reviews.apache.org/r/69554/diff/1/?file=2113078#file2113078line616> > > > > While all the write operations on sessions are handled in this code, I > > am not able to see any changes in list and get kind of apis in this class > > For instance, what happens if getAllSessionParameters api gets called > > with a session id from other lens instance, in which case I assume , > > restoresessionfrom db needs to be called in the getSession api of > > BaseLensService, which doesn't seem to be handled here > > restoresessionfromdb might have to be called in other apis involving > > write operations as well, which I am unable to see we are calling it for 1. requests in query resource 2. get/set params , list/add resources in session. 3. all requests for scheduler service 4. all requests for metastore service. - Ankit ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69554/#review211269 ----------------------------------------------------------- On Dec. 18, 2018, 12:20 p.m., Ankit Kailaswar wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69554/ > ----------------------------------------------------------- > > (Updated Dec. 18, 2018, 12:20 p.m.) > > > Review request for lens, Amareshwari Sriramadasu and Rajitha R. > > > Bugs: LENS-1538 > https://issues.apache.org/jira/browse/LENS-1538 > > > Repository: lens > > > Description > ------- > > Implementation > > Session > > We need to persist all client session in database. > This involve persisting client session’s id and configuration in mysql > server. persisting entire session object is not required. We need to do this > as first thing while creating user session. > For each request from client lens server should not validate session id > from its in memory map. It should rather validate it from persisted session > in mysql server. > > if > > session is present in mysql and not present in lens server’s in memory > map(session manager) then it should create a lens session with same session > id and add it to in memory map > > else If > > session is not present in mysql and present in server’s in memory map then it > signifies that user have initiated close session from other host and we will > need to remove this session from current host’s in memory map as well > > else if > > session is not present in mysql and in server’s in memory map then return > “invalid session”. > > Whenever session expired/closed then we need to remove this session from > lens server’s in memory map and mysql. > > > > Query > > For sync queries lens server will close connection as soon as it is > stopped or failed with appropriate failure message. Client will be retrying > the query. > For async-light queries and async-heavy queries lens server takes care of > rescheduling all queries which were in running or queued state at the time of > restart. we can use this to make query ids available with both servers. > For async queries we need to persist all non finished async user queries > in mysql server in new table current_query. > If user executes query on host1 and it goes down and nginx points to > host2 then user should be able to poll on query status. Lens server will > first check query id in its inmemory maps if it is not present then it will > check in “finished_query” table in mysql else in “current_query” table in > mysql. In this case we will continue showing old status of query since it is > scheduled by host1. As soon as host1 comes up it will reschedule these > queries and will change the status. Optionally we can have host2 to move > these queries in “allqueries” map of its query service which will take care > of recovering, in this case we don't need to wait for host1 to come up and > reschedule. > While moving query from ”finished_quey” map to “finished_query” table in > mysql we will need to remove it from “current_query” tables as well. > This flow will remain same for request ids/query ids generated for query > plan/estimate. > > > > Issue addressed > > Lens downtime will be zero in case of deployment and if primary fail. > User will not have to create a new session whenever switch happens > User will be able to get status of all async queries seamlessly. > > > Diffs > ----- > > > lens-server-api/src/main/java/org/apache/lens/server/api/SessionValidator.java > 65403191 > > lens-server-api/src/main/java/org/apache/lens/server/api/events/AsyncEventListener.java > 94734658 > lens-server/src/main/java/org/apache/lens/server/BaseLensService.java > 9364872d > > lens-server/src/main/java/org/apache/lens/server/error/LensServerErrorCode.java > ef43371a > > lens-server/src/main/java/org/apache/lens/server/metastore/MetastoreResource.java > cb29c9ea > lens-server/src/main/java/org/apache/lens/server/query/LensServerDAO.java > cc6ca7d4 > > lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java > 07a2107a > > lens-server/src/main/java/org/apache/lens/server/query/QueryServiceResource.java > 47b40a8f > > lens-server/src/main/java/org/apache/lens/server/scheduler/ScheduleResource.java > 1d5959b2 > > lens-server/src/main/java/org/apache/lens/server/session/HiveSessionService.java > f6d43d70 > > > Diff: https://reviews.apache.org/r/69554/diff/5/ > > > Testing > ------- > > Unit testing > > > Thanks, > > Ankit Kailaswar > >
